Is this possible? I need to have separate product catalogs for different domains (looks like this can be done with core Domain Access) and also use different payment gateways or just different Paypal accounts for them. I've looked into Ubercart Marketplace but it doesn't seem to do this either.
Comments
Comment #1
longwaveI have added preliminary support for per-domain payment methods and gateways, though I have only briefly tested with PayPal so far.
These settings are not enabled by default as some users will want the same settings across all domains. To enable them for your site, visit /admin/build/domain and select the required options under Ubercart settings. The individual domain settings pages will then allow you to change all the same options as the standard payment settings pages.
This is available now from CVS HEAD or as 6.x-1.x-dev in a few hours - any feedback will be useful, more testing is always good!
Comment #2
julia_g commentedWow, that was fast, thanks! I may not have time to test it right now but I'll let you know after I do.
Comment #3
longwaveComment #5
OzSchmoz commentedI'm trying to use this feature, but it doesn't appear to be saving my settings. I have a two domains. The first domain uses paypal express checkout and I need the second to use payment method "Other".
When I set the options on the /admin/build/domain settings page for the secondary domain, it says "The changes have been saved" but does not actually save them.
Any suggestions?
Thanks
Comment #6
plasticlax commentedsame here. this is only happening to the payment method section, store, product and order save the settings (haven't tried gateways)
this would be awesome if it worked.
should there be a place to set the site's default currency?
Comment #7
plasticlax commentedmaybe this is an option: http://drupal.org/project/uc_conditional_payment
Comment #8
jm.federico commentedmarking #544842: Separate payment and currency systems? as duplicate of this
Comment #9
longwaveI don't currently use this feature and don't have time to debug it at present, I'm not sure why it isn't working as expected. It might be better to use the Domain Settings submodule included in Domain Access itself to provide per-domain payment method and gateway settings, rather than duplicate the functionality here.
If someone has success with this, please report back and I'll remove this functionality from the module, or alternatively if anyone can provide a patch that makes this functionality work as expected, I will commit it.
Comment #10
m.stentaI need the ability to change the available payment methods on a per-domain basis as well (gateway settings are less of a priority to me at this point). I looked into the code of this module, and discovered that
it doesn't actually have any code to do this. (see my update at the end of this comment)UC Domain currently provides extra fieldsets in each domain's settings (at /admin/build/domain/conf/%),
but it doesn't provide any code to make them work. It merely displays the forms. Submitting the form does save the settings to the database in the {domain_conf} table,but it saves them in a disorganized fashion, and it doesn't load them in as default values when you view the form again, so it looks like they haven't saved.UC Domain does NOT do anything else with those settings after they've been saved. It does not change the methods that are available in checkout, nor does it apply the domain-specific payment settings during processing. So that all needs to be done.I'm going to be working on this over the next few days. It seems that the main tasks at hand are:
1. Save the domain-specific payment method settings properly to the database, and load them up again as default values when the form is reloaded.
2. Add code to make it all work. Change which payment methods are available in checkout based on the settings, and change the settings for the payment method during processing.Step 1 is pretty straightforward.
Step 2 is the much larger, and more uncertain, task. It will involve hooking into Ubercart's processing, to ensure that the checkout form is modified properly, and all the payment method settings are used as expected. I need to dig in to find out exactly what all this entails.We will also need to do the same thing for the per-domain payment gateway settings, but for now I'm focusing on the payment methods, because that's what I need.
Update: I may have jumped the gun on this issue a little. It appears that it does actually work... I think. It's just the form defaults that don't work (#1 above). I will dig into this more to confirm...
Comment #11
m.stentaOk, so I was wrong... the settings do stick when you save them (sort of... I might have found a separate issue, but I'll open a new ticket for that if so). I missed the fact that the Domain Conf module overrides variables system wide, and this module just taps into that.
So it seems that the main issue here is that the forms don't display the values that you selected. They only display the sitewide values.
I've created a new issue to address that specifically: #1854472: Per-domain payment settings forms don't load saved values
Closing this one for good now.