Hi, I was wondering if anyone knew the answer to this question. I'm running multiple moodle site (approximately 8 sites) all on subdomains: http://sub1.mysite.com/ http://sub2.mysite.com/ ... http://sub8.mysite.com/ Now I know you can run 1 installation of aMember with multiple subdomains, but when it comes to moodle and the moodle integration, how would one have different pricing with each subdomain, all with their own DB's, and using the 1 aMember installation to manage each one. I've tried using sales groups, which does not work unfortunately due to no way to register the user in the moodle DB after installation. So I'm guessing some minor tweaking needing to be done with the plugin, and so far I've tried new directories, renaming the $___plugins name, and altering anything that looks like it could affect the plugin so I can run multiple version of the plugin to different moodle sites all with no luck. Anyone tried this, and if so, what is your solution to this issue? Also started a ticket: HJS-24298-693 - will share anything that comes about.
Ok, I'm able to run 2 instances of the moodle plugin side by side, but the issue now is that when creating a product, theres no way to tell that product what plugin (with proper configs for that product) to use. I find it odd in so many versions of this software no ones run into this, or maybe I'm not thinking of this in the right way. Anyone have any ideas? Odd issue to note: If you do run multiple instances of the moodle plugin side by side, any working sites that would point back to aMember for registration will now produce an error: WARNING: implode() [function.implode]: Invalid arguments passed in line 207 of file moodle.inc.php I'm assuming since there are now multiple DB's and paths to choose based on the different products that the system cannot distinguish what product/path/plugin is valid for the select product from the moodle portal.