Hi! I currently use the latest versions of all 3. Thank you Alex for the Joomla plug-in I am new to aMember, but not new to Joomla or Kayako SupportSuite. Here is my question... 1. When I create a new User in Joomla - it doesn't update aMember. So I'm assuming that the Joomla plug-in is intended to have users sign-up via aMember THEN it >> updates to Joomla, correct? This seems to work fine. So I will have my users sign-up via aMember. I'm just trying to figure out which app to be my 'starting point' for registrations. 2. In Kayako SupportSuite - I use the Joomla LoginShare widget. So this means the login form connects to the Joomla users database. But for some reason, after install I can't seem to login to Kayako. I changed *nothing* on the Kayako or Joomla side - so shouldn't this still work? Only thing I did was install the Joomla plug-in for aMember - then rebuilt DB. Sorry if this has been asked before, I'm new. I tried searching. Thanks!
P.S. I don't mind having my clients logging in twice for Kayako. But aMember and Joomla I'd like them to stay logged in across each other.
Hi! In theory, regardless of any scripts, installation, etc. every amember installation works the best - if and only if - the registration is done through the amember registration and the same for sign-up (with exceptions)! So if you went through the registration system of amember, then it would add the user login data in all the integrated plugins, that are for that purpose activated. Here the user data will be entered in all the integrated databases i.e. tables and you DO NOT need a rebuild. The signup of amember will log a user in each and every integrated database if there are respective subroutines i.e. functions in the plugins. Here joomla has a common login and each and every user will be logged in by the amember - if and only if - the domain is the same. For different domains, there is no script on earth that logs a user for every domain and it is a restriction by the browser itself, i.e. all browsers will log only for a single domain. Hope this helps.
Thanks Draj, very helpful knowledge! Thanks! So I will have my aMember be my registration point. This is great, because it will add users to Joomla database. I don't expect you to be knowledgable with Kayako SupportSuite, but they also have a Joomla "login share" module. It's a login form that uses the Joomla database and works fine until I began to add users from aMember... So my confusion is - since aMember creates new users in Joomla with standard registration in the Users table, and Kayako retrieves Joomla users also ...then, in theory, shouldn't Joomla be my main DB and Kayako login form should work cohesively?
Hi! If you follow above what I mentioned rather very stricktly, and stop thinking of each and every other options, you will land where you would NOT have any confusions! ;-) Lets call Master database for aMember tables and integrated/plugin databases as Slave Database. Without aMember as Master database, how will every other integrated Slave databases will work? Imagine a user being added by any other script in the Slave Database. So how will the User data get into the Master or anyother Slaves? Well, the Master works like a Trunk and Slaves like branches! So the database grows from trunk to branches. Now all the subscription controls are in the aMember tables. So Users needs to be there. When a User is added togather with its subscription details, it will immediately get added into all the Slaves for which the Slaves are connected and subscribed for. It works like a one way road i.e. from Master to Slave. I have placed a request to import User data from ONE Slave into the Master. Thereafter one could rebuild the antire database or part of it. You need to FORGET of getting users in any of the slaves FIRST and then thinking about how and what to do with the users with other slaves, etc. All Users MUST get into the master where the information are stored. So you need a plugin for Joomla and Kayako, configure both of them for interface with aMember i.e. all the login + registration through the amember. Now after doiung this, all the information will get in both the plugin Slaves i.e. Joomla and Kayako automatically, each and every registration, modification of the data, etc. Joomla and Kayako will and must not be allowed to anything with the user data but simply do exactly with each and every kick a user gives with their account within aMember!!! What do you need to remain hanging with othr systems, however well designed they are? You do NOT!!! Just work with amember and thats it... Further, if you deactivated all the other Login/Registration modules, it would be perfect so long as aMember offers acommon login function for that plugin. I beleive that Kayako is one of them in the list for which aMember works for a common login.
Draj, Sorry, I have no idea what you're talking about *confused*. Thanks for the replies though. I have solved the problem. I had to clear my User DB in SupportSuite... So in case anyone else is reading this who has the same setup as me: the SupportSuite Joomla LoginShare works as it should since aMember/Joomla plugin also shares the Joomla database. But there is a glitch in the SupportSuite DB not updating ITS users until you delete them (from SupportSuite) and they log back in again. Then the Joomla users will show up in your Client userlist! I'll move this to the Kayako forums since its not an aMember issue any longer. Thanks!
Hi! If you understand and solve the problem, goodluck. Thats good for you. However, if you do not use the amember database for registrations and logins, your other databases will not function correctly. You need to switch to amember entirely. This is not an issue of any other databases or programs. I say this out of my own experience, integrating other databases.