Hello all. I've come across a rather interesting glitch with aMember's login module for Mambo. Some of Mambo's components do not recognize a member as logged in. However, when I logged in that user via Mambo's native login module, the problem disappeared. That means there is *something* not quite right about the Mambo module provided for aMember. Has anyone else had this problem? If so, how did you resolve it? Thanks! Regards, Brat.
Fixed!!! Okay, I made some fairly major changes to the existing aMember Mambo login module. My prior logout problems disappeared. This also resolved the issue of certain components not recognizing members logged in via the original aMember module (though, if logged in through the standard Mambo login box, the same members were perfectly fine). Regards, Brat.
Would you be willing to share those mods with Alex so they can be rolled into the plugin? I'm working with several cms and the mambo login has been a drawback. Tom
Sure. I'll finish cleaning it up tonight and I can package the module for Mambo installation (i.e., the php and XML files zipped). Let me know the best way to send it. Thanks. Regards, Brat.
When I login using the Mambo plug-in, in Mambo, I find that it's actually sending me to the aMember profile, rather than simply logging me into the Mambo site. Is this the way it's supposed to work? I'm setting up an online magazine, and I simply want people to be able to login, and then have access to the parts of the Web site i have given them access to. They really don't need to login to the aMember system (front-end) ever. Thanks, Ryan
Was this ever finished? I'm having trouble with akocomment and amember not recognizing each other... was this fixed?
Akocomment is an addon component for Mambo that uses the Mambo core user db. Even though my concern is not with regard to core mambo or akocomment integration, I will document some of the buggy experience I had with the amember integration plugin as it relates to mambo core user integration: If you use a Mambo login module it will log you into both (aMember & Mambo), however, the mambo logout module will only log you out of Mambo (not amember) when you click the log out button. If you change your password through Mambo's registration update interface it does not update the aMember user account. However, if you change your password through aMember, it does change the mambo's core user password. Whatever the case, I personally am not using the Mambo integration plugin since I'm waiting on the aMember plugin integration for Mambo's Community Builder (CB). One thing to note Alex (while developing the CB integration), is that amember password, name, & e-mail verification, login/logout functions, & cookie session fields should be able to be updated in aMember whenever the user changes those instances from the CB interface. I wish you luck in the integration. Supposedly the integration should be much more straightforward to accomplish in the upcoming CB release. I hope you were able to get on the 3rd party integrater list.
I have not received any response to my messages from the developers of CB. Lets wait for official release.
Alex, I was able to get on their 3rd party developer (3PD) team the other day. I did it under the auspice of aMember Pro. They haven't yet released build 9 to the test/3PD team. Build 9 is the last build before they fix up the final bugs and release the final software as RC2. Build 9 is the release that contains the special plugin API (which makes it supposedly simple for 3PD to integrate). Who did you e-mail to get on the 3PD team? Could you try the request again? I was planning to attempt some of my own aMember integration hacks to build 9 and then funnel my changes to you for potential roll up into your final code. But then again, I'm not exactly a coding genius. I think it will be great if the next CB release is integration capable with aMember (inherent in RC2 s/w without the need for a plugin). It will encourage future users to consider the two pieces of software for less installation hassle. The best way to accomplish this ideal would be to have a plugin created and given to the CB developers prior to final RC2 release. Let know if you're interested in such. Even if you're unable to get on the test team, I can still get you a copy of build 9 when it is due out next week.
Could you email or PM me their email address to alex@cgi-central.net ? I contacted them via PM in their forum.