 |
Ubercart |
|
|
|
||
|
Mon, 11/24/2008 - 13:11
  Yikes! In my multisite environment, changing a payment setting on one site changes the same setting on all sites. I don't think it's supposed to work that way. Site-specific payment settings are mission-critical. Is there a trick? Someplace I should look for a problem? Thanks.
Re: Multisite Payment Settings
It seems like this could only be happening if you're sharing the variables table... are you?
Hard-code it?
I suppose I could hard-code the settings in each site's settings.php file, but that seems clunky. Is there a better way?
Re: Hard-code it?
My question was more related to how you've configured your multi-site setup. Payment settings are stored in a site's variables table, which (afaik) is supposed to be unique for each site.
Variable table
My multisite setup didn't result in separate variable tables. Don't know why or whether, it just didn't. I've been wondering about that. What I've done with other elements (store name, store address) is just hard-code them into the settings file like this: $conf = array( and I could add: 'uc_credit_payment_method' => '0', but I thought multisite was supposed to let me do it through the administration interface. If now, I guess I'll survive. By the way, your responsiveness is fantastic and greatly appreciated. I think I'll donate.
Install?
Hmmm, wonder if it's because I didn't run install.php in each new subsite directory.....?
Nope.
Nope, that's not it. You gotta hard-code the settings file. Or you could do shared/separate tables as mentioned somewhere on the Drupal site, but that creates new tables in the db and means that nothing from the variable file will be shared. I want most variables shared, but a few not.
Re: Install?
Yeah, it sounds to me like maybe multisite wasn't configured properly. The gist of it, if we're thinking of the same thing when we say "multisite", is you should...
This will let you configure each site independent of the settings, modules, themes, etc. installed on the other sites. The advantage of a setup like this is then you only have to maintain a single code base... so you'd only have to update Drupal or Ubercart in a single location to affect all the sites. You'd still have to go through and run update.php individually at each site, though. Also, thanks for your kind words. Any donation would be gladly accepted.
Errata
correction for those who are trying this out: the field to enable/disable credit cards at checkout is uc_payment_method_credit_checkout, not uc_credit_payment_method.
Sounds awesome. Thanks for
Sounds awesome.
Re: Sounds awesome. Thanks for
Some simple notes (and a question) about using domain access with Ubercart can be found here:
OK and How-To
Everything is lovely now. I will explain the circumstance and the correct config so that others might find it. This is mainly a how-to for others. My setup is "multisite" in that visitors will access a single Drupal install from a number of separate domains. We do that by redirecting their domain to the correct Drupal subsite. Our Drupal install is in the base url of othersite.com. Our server does not like subsite folders in the base url (url would read subsite.othersite.com) and insists that the subsites be only in the sites directory (url reads othersite.com/subsite, but the actual subsite folder is sites/othersite.com.subsite). That's fine, because we want to share a single database. Only subsites that do not share a common database need to be in the base url. My site has a great deal of shared content, thus the single database. If I have subsites bonkers, wonkers, and wankers, a member of any of them can see the shared content. I also have content that is specific to a single subsite. A member of bonkers can see the site-specific content of bonkers, but cannot see the site-specific content of wonkers and wankers. I handle this through taxonomy, using the Taxonomy Access Lite module. The same taxonomy allows UberCart products to vary between bonkers, wonkers, and wankers. A member of bonkers can see common products and can see bonkers site-specific products, but cannot see site-specific wonkers or wankers products. One key product type is memberships. I create a membership product for each site, and use Workflow-ng to grant the membership role corresponding to the site on which the membership was purchased. Thus I have separate membership types, and separate membership roles, and separate membership product workflows, for each site. It's easier than it sounds. Three quick settings. If you buy a membership on bonkers, you are granted a bonkers membership role and can see (and create) the content that bonkers members can see. In the same way, a bonkers administrator can change selected settings for bonkers, but not for wonkers and wankers. I use basic Drupal access to determine which settings they can change, and TAC Lite to determine which site they can administer. Unlike with memberships, I set up a single administrator role, rather than separate site-specific administrator. I (manually) upgrade a site member to administrator on their profile page, where I also use the ability of TAC Lite to create taxonomy access rights (to bonkers, wonkers, or wankers) applicable to that one administrator. I could do this with members, too, but doing manual settings for zillions of members would make me crazy, thus I create separate site-specific roles for members. All members have access to the store, where they buy memberships and other things. As mentioned above, TAC Lite determines which products they can see. But in my situation, each site is in fact a separate organization. Different people own and run the individual organizations that share the Drupal site. Bonkers, wonkers, and wankers share the Drupal install, and share some content, but they are different people who do not share bank accounts. They are separate entities. I do not care to channel all of their transactions through my credit card accounts, because I would have to do a lot of bookkeeping. So I need to have separate payment setups for each subsite. Hmmm. I do that by hard-coding each subsite's setup.php file, in their subsite folder. I separately specify whether each site takes checks. If they do, I separately specify the address to which the checks should be sent. I can separately specify whether each site takes credit cards, what cards they take, and what their account numbers, etc. are. It is just a matter of identifying the correct field in the database's "variable" table, and specifying a custom value in the settings.php file. The code to do so is already at the bottom of settings.php. All you do is add some fields. The process is detailed in an earlier post of mine, above. Now I have multisites with a common database. They share a lot of content, and don't share other content. The settings.php file allows them distinct names, addresses, and so forth. They share a store in which their members can buy common products and site-specific products. The settings.php file allows each site to independently decide whether to take checks or credit cards, and to specify their own addresses and credit card account details. (Of course, I control access to the settings.php file, so I make those settings for them when they set up their subsite.) And, of course, I have a variety of themes from which each subsite can choose. A different look, different logo, different graphics, different block layout for each subsite. (Drupal tracks block layouts and some other stuff nicely for multisites that share a single database, even though it won't separately track content without taxonomy. Strange but true.) It works for me.
Brilliant! But I need your help PLEASE!
Hello Your solution may have saved my life. What I need is what you have suggested, which is that all products are the same (and look and feel is the same) except only CURRENCY and PAYMENT are different (as in a multi-country solution for a company) PLEASE can you help me, by publishing a complete list (if the one you demonstrated above isn't complete) of all of the variables I need to manually set? I need some countries to pay by credit card through one 3rd party provider, and other countries to pay by credit card through other 3rd party providers. How did you go about finding out what these settings should be? In setting up your multi-site, did you install ubercart in the default directory, then change settings.php in all sub sites, or did you install separate instances of ubercart in all subsites? Are there any other tables within ubercart that i need to share, or make sub-site specific, in order to get this solution to work? This would save my life. Thanks!!!! |
|
Thanks for taking the time on the write-up. I'm not sure if you're familiar with it or not (or if it even applies) but there's been work done around a module called