Hi, I originally worked with Alex to write the first Moodle/aMember plug-in. I left the Moodle platform for a while and was glad to see that chemical2004 was working with aMember to rewrite the plug-in to work with the current Moodle versions. I have integrated Moodle and the new aMember plug-in on a site I am building. I was trying out a new video capturing program tonight and decided to knock out some flash movies to show what the front side and back side of this integration looks like. The plug-in has been tested extensively on Moodle 1.7-1.8. It is still being tested on 1.9 (which is actually a Moodle beta release). The movies that follow are of a Moodle 1.8.2 integration. Within a week, or so, I will make a detailed set of videos showing the Moodle/aMember integration. http://digitalliteracyproject.com/myfiles/Moodle_aMember_Front_End.swf http://digitalliteracyproject.com/myfiles/aMember_Backend_1.swf http://digitalliteracyproject.com/myfiles/aMember_Backend_2.swf http://digitalliteracyproject.com/myfiles/aMember_Backend_3.swf http://digitalliteracyproject.com/myfiles/aMember_Backend_4.swf http://digitalliteracyproject.com/myfiles/aMember_Backend_5.swf
Thanks Grant Swaim. Nice tutorials. the single login integration script is also working fine with moodle v1.9 beta+.
Great tutorials Grant. Quick question - do you have to manually add the Moodle admin to aMember after getting the plug-in set up?
Nope. The Moodle admin and the aMember admin don't have to have the same user name or password. aMember controls enrollment by making direct changes to the Moodle database.
Thanks for the reply. But I already have a Moodle admin, but it's not listed as a user in aMember. I guess what I'm asking is how you got your Moodle admin into aMember after you integrated the two? Doe a new admin user have to be added via aMember, then given admin privileges in Moodle?
nestguy, The Moodle admin and the aMember admin are two different things. You install Moodle and aMember as two separate programs and during the installation process admin accounts are created for both. You then use the plug-in so that aMember can enroll students by directly making the changes in the Moodle DB. You do not need to add the Moodle admin to aMember or the aMember admin to Moodle. Each program can have a different admin username and password. I do see what you are saying in that the admin user is not showing up in aMember, but I don't think it will unless you did an import of the existing Moodle users into the aMember DB. In my case I am starting a fresh installation of Moodle and aMember and I will not be doing an import. This means aMember will not have the Moodle admin user in its DB, but it doesn't need it. Hope this makes sense
Yes. I should have clarified, I have set up using redirect code to have all login functionality handled by aMember. Therefore, I needed a Moodle admin user available from the aMember database, in order to log in as a Moodle admin for admin tasks. The code bypasses Moodle's native login, and relies completely on aMember. You made sense -- hope I'm making more sense now .
What I understand from the present amember integration code is that, it simply passes on the default role (student) to the amember user. (in fact amember does not pass on any role and moodle assumes default role to the amember user). For a moodle admin, you need administrator role to be passed on to the moodle. This is not done. The concept of role does not exist in the present script. Therefore, login redirect does not work for moodle administrator. Since, amember stores passwords in plain text format, I would not recommend moodle administrator to be put in to a risk. If you still want this to do this, you can add an user in the amember and assign the role of moodle administrator from the Site Administration --> Users --> Permissions --> Assign global roles
I approached the integration a little differently. Since about the only time a user needs to interface with aMember is to register with a class, I use the Moodle login and only direct users to aMember to register for a class. The current plug-in supports single login, so when you log into Moodle you are also logged into aMember in the background automatically. When I need to perform administrative duties on the Moodle site, I simple log into Moodle with the admin account that was established when I installed Moodle. Remember you do not manage students and enrollments from Moodle, that is all done from the aMember CP. When I need to manage students or enrollment, I log into aMember with the admin account that was established when I installed aMember. You can see an example of this integration at http://digitalliteracyproject.com You will see that you are initially routed to aMember to register with the site, then you simply log in using Moodle login.
Grant, thanks for the fine videos on intergrating aMember and Moodle. I have a quick question concerning installing the auth-amember.zip plugin. After uploading the files to their proper locations when I view the plugin at Admin--> Users --> Authentication I see the plugin listed as [[auth_amembertitle]] and when I look under it's settings I see [[auth_amembertitle]] and [[auth_amemberdescription]]. We are using Moodle 1.8.2+. Is there a problem with intergration with this version? OH, another thing. Can you please list the suggested configuration for Moodle to interface with aMember correctly. Thanks a head of time! Ji
Check your language file (in the lang/en_utf8_local folder - auth.php). If you add it to your Moodle language directory, that may fix how it is displayed under Admin > Users > Authentication.
Hi all, I've three issues : 1. Did anyone test the integration with moodle 1.8.3? 2. My installation login from moodle doesn't work with account created with aMember even if users are correctly synchronised in the moodle database mdl_users. On the other hand aMember can comunicate with moodle: the "check for uniqueness" function works on the sign-up page. The problem seems to be on the auth mode ("Users/Authentication") of Moodle. Thanks for your help. Marco NB: My config->Moodle: 1.8.3 aMember: 3.0.9PRO
That was more for demonstrating the power of the integration. I need to make a detailed set of videos on how to do all the steps. I will try my best to do that this coming weekend... I got that result when I was doing the installation, but I forgot the exact reason. I know I had placed one of the files in the wrong place. I went pack and read the installation instructions again and got it right. Seems like some of the instructions are a little "fuzzy". I will nail that in the videos, again I will try to do it this coming weekend10/27/2007. It boils down to configuring the course right and then modifying a few language files for the redirects back to aMember.
I have it integrated with a Moodle 1.8.2 site, I would assume if it worked on a 1.8.2 site it would work on a 1.8.3 site. You can see the integration at http://digitalliteracyproject.com I am not sure what is causing this. I do know that on my installation supports single user log-in from both sides. My plan is to do a detailed set of installation videos this coming weekend 10/27/2007.
I fixed the problem. Nothing with aMember or Moodle 1.8.3. But only a problem with mysql database name and reserved character. Everything seems to work great between those two products. Marco Capturator - Languages on-line
Well, not really single sign-in... for Moodle We finally got the Moodle plugin installed however there is a issue where there really isn't "real" single sign-in on the first try. In our situation, when a user logs into aMember and then tries to enter Moodle they are redirected back to the member.php page. We have found that in this situation the user has to logout aMember then log into Moodle. Moodle will then display the Moodle site policy where the user has to agree. After the user logs out and then logs into aMember again the user has "true" single sign-in function. PS: Update: This issue has been traced to a known cookie issue related to Moodle. I maybe missing something in setup Grant. Is there a way around this? Is the policy step blocking single sign-in on the first entry? Note: Here we also have the Wordpress plugin with aMember. If a user "logs out" from Wordpress the user WILL NOT be logged out of Moodle or aMember! I'll try to send a ticket reporting this (if the ticket system allows me this time ) Maybe the exact setup will be explained in Grant's next video. Ji
Yes you are right. It still happens to me occasionally. I will contact help desk tomorrow to find out the real reason
Hi all, I just installed the Moodle plugin. I'm having problems trying to work. In the aMember configuration section for Moodle, when I type in the Moodle Full Path and click on Save, I get an error that says: Moodle plugin error. Not all settings loaded, check config.php My installed Moodle via the Cpanel Fantastico feature in a folder called courses. I'm using Moodle 1.8.2 I have Amember installed with slightly modified files. The modified files are: signup.php & config.inc.php I've opened a support ticket but thought I might try the forums as well. Any help much appreciated. Warm regards, Bina.
Hi Chemistry2004! I just got a note from the Support Desk and it looks like aMember doesn't support logouts across plugins. All logouts should be done from aMember itself for logout from ALL plugin connected platforms. So at this point I guess the best way would to have the logout link in all plugin connected platforms link to aMembers logout.php Does that sounds like it would work? Ji
Can you give a link to your website? I am looking for examples of sites that are successfully using Moodle & aMember.