-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multi-Store Support #6
Comments
Hi @syntaxerror Thank you for your input for the module. I have added your request to our backlog, but I can not say when or if the feature will be implemented. Have a nice day Best regards |
Hi everyone, We have a multistore with 15 domain names. The actual store is the same, it is operated by the same company, and the websites only differ by language and ccTLDs for SEO reasons. We received 15 merchant IDs from Bambora, but this official extension accepts only one, most likely because it was designed with one backend = one store logic in mind. If we implement and contribute the changes required to make the extension work with multiple merchant IDs, will you consider merging them? Provided, they're submitted here using Github via a pull request where you can see which files had been changed and where exactly. Or maybe due to some regulations (who knows) you can only publish the code that originated from within your organisation? The change I can think of would be:
What do you think? |
Hi @mehov! |
@sessan Hi, it's been 5 months, are there any news maybe? Please let me know. Thank you! |
If anything is done with this, the easiest is probably to add the store id's to the returned values in getConfigBaseName(), plus the needed loop in admin for setting up the config for each. T.ex.: |
When it comes to this I hardly see any issue, as long as the quality control is done by Worldline (Bambora), the module already includes t.ex. my code, and also lots of OpenCart code. And actually since it's built on and with OpenCart code, it's still GPL licensed code, no mater what's stated in the file headings, and actually the headers are GPL license violations #3 |
We have brought this request up to Product but it is not prioritised at the moment unfortunately. |
To whoever is stuck with this like we are, here comes: First commit:
Followed by:
I initially wanted to make this into a pull request, but I guess chances are it will be ignored, plus if you said yourself that you don't need it, then why should we even bother, right? And it looks like Opencart is a sinking ship anyway. |
A pull request is probably easier for many to read and use than the old fashion diffs, even if WorldLine (Bambora) ignores it, or have it pending forever. But sure they have some weird priorities at Product... :)
Sure OpenCart and its dev is what it is, and we probably wouldn't build any new stores on it at this point, but still using search stats as a measurement for the use of it probably isn't the best idea - most software have some of the same drop. Better look at something like https://trends.builtwith.com/shop |
Hi! I've brought this up again with the product team and it has finally been prioritised (multi store setups for all the different shopping carts we provide) so we can look into it! So it would be very helpful if you could provide a pull request @mehov |
I'm looking to implement Bambora in a multi-store setup. It's been a few months since this was last discussed. Any updates @sessan ? |
OpenCart, Magento and some other of the supported carts have multi-store support.
This means they can be running several stores, using different domains (or sub-domains), from the same admin (about 50% of our clients use this).
Bambora supports normally only one domain per account (merchant id), as I have understood, but possibly have some workaround to allow several domains per account (still unclear to me).
So as a minimum, the modules should at least support using different payment windows (logo and name) per store/domain. But preferably also different Bambora accounts per domain, unless this domain restriction is going to change soon at Bamboras end.
The text was updated successfully, but these errors were encountered: