Joomdle 1.0 Installation

Error 500

More
10 years 4 months ago #1 by inesh
Error 500 was created by inesh
Joomla 3.45, Moodle 3.0, Joomdle 1.0.3
System Check: Joomla to Moodle & Moodle to Joomla HTTP connectivity are not okay but Joomdle Web Services is okay.
Using cURL but file_get_contents has the same behaviour.
Not using redirectless SSO.
Yes, using redirectless logout.
===============================================

Logging into Joomla gives an Error 500. (Reguested URL: "/moodle/auth/joomdle/land.php?username=somename&token=4c00becae190d8047db24e6750c9053b&use_wrapper=0&create_user=0&wantsurl=http%3A%2F%2Facureflex.ca%2Fa%2Fen%2F") Given that the Moodle authentication failed, the user is logged into Joomla but not Moodle.

Logging into an embedded instance of Moodle is okay (and actually logs the user into Joomla as well although you can't see this until the screen is refreshed).

Logging out of the embedded instance of Moodle is okay (meaning it logs user out of both Moodle and Joomla).

Now that I use redirectless logout, logging out of Joomla no longer gives an Error 500 but the user is still logged into Moodle. (Former Error 500... Requested URL: /moodle/auth/joomdle/land_logout.php)

And, the other weird thing... when a user creates a Joomla account, everything is apparently okay but it isn't. Joomla, Joomdle and Moodle user accounts are created. The appropriate user group is assigned. The user's name, username and email address is saved and passed along. But the password the user signed up with isn't anywhere to be found. So even though the system says "You can now login.", the user actually can't. Account creation and logging in (to Joomla) was okay before Joomdle 1.0.3.

So... I don't know what to try next. Any help would be appreciated.

Please Log in or Create an account to join the conversation.

More
10 years 4 months ago #2 by Chris
Replied by Chris on topic Error 500
A few things you may wish to try while Antonio is sleeping :)
- Enter deubbing mode to see if you get any further information
- I infer from your comments that you upgraded from a previous version of Joomdle. Therefore, did you upgrade Joomdle in Moodle too? You can check in the Joomlde for Moodle configuration to check the version of Joomdle. (You would have had to remove the Joomdle folders in Moodle and then add the new ones).
- Ensure all the Joomdle functions are added to the Moodle user. When upgrading if new functions are required they must be added as Moodle will not auto add these. www.joomdle.com/wiki/Installing_Joomdle_...functions_to_service

With regards to the password not being found, I assume you mean in the Moodle tables? The passwords will be stored encrypted in joomla's user table.

Please Log in or Create an account to join the conversation.

More
10 years 4 months ago #3 by inesh
Replied by inesh on topic Error 500
Thanks for having taken the time to respond!

It was actually a fresh Moodle installation so it was a fresh Joomdle installation in there. I actually think that the problem is on the Joomla side of things as Moodle connects to Joomla just fine but Joomla is having a tough time connecting to Moodle.

For the user accounts... it's Joomla that seems to be the problem. The account is created on Joomla, the message comes back "Thanks for registering. You can login now." but the login information isn't recognized. Manually opening the user account in Joomla to put in the password that was given when the account was created does the trick.

All of that makes me think that I missed something on the Joomdle upgrade to 1.0.3. Well... I write "upgrade" even though I did eventually uninstall Joomdle from Joomla and then reinstalled it.

Please Log in or Create an account to join the conversation.

More
10 years 4 months ago #4 by Chris
Replied by Chris on topic Error 500
Like most Joomla extensions, uninstalling will leave the Joomdle tables intake, so a fresh Joomdle install will have the old tables there - so a complete fresh Joomdle installation should include (after removing Joomdle using Joomla's installer) removing the tables before a new install.

What you are describing re user creation is odd. Joomdle does not get involved with the creation of user ids and passwords, this is Joomla's job. I am not suggesting it is impossible for a conflict to exist but the process is typically create user in Joomla. Joomla triggers plugins which act upon user creation which Joomdle will be one of them.
- Are all your joomdle plugins enabled? What happens if you disable them? Is the password stored correctly?
- What login module / extension are you using to register users in Joomal? We do not test all and there are known capabilities issues with some 3rd party extensions that may not have been tested.

Also did you enter debug mode to more details on the error 500? 500 is a system message so you should see more info and also there should be a line written to your error log in Joomla (normally stored in Joomla's root)

Please Log in or Create an account to join the conversation.

More
10 years 4 months ago #5 by inesh
Replied by inesh on topic Error 500
Disabling all of Joomdle's plugins makes the user creation/login problem go away. I turned them back on one at a time. The problem shows up when I enable "User hooks - Joomdle".

I use standard Joomla to create and login-out users.

The 500 Error leaves no trace in the error log. The only information I can see are the referring URL and the requested URL. The latter is always a version of this..." /moodle/auth/joomdle/land.php?username=astudent&token=e4bfcca183dfcd1eea2a45323a937d39&use_wrapper=0&create_user=0&wantsurl=http%3A%2F%2Facureflex.ca%2Fa%2Fen%2Fclasses" The "wantsurl" is the referring URL.

I did turn debugging on. I'm not exactly sure what I'm supposed to see there. Nothing unusual showed up. A couple of duplicate calls to the database that come from the template code.


I think that tomorrow I will uninstall Joomdle from Joomla again and/but will, this time, remove the tables. Thanks for the heads up on that. And, again, thanks for having taken the time to respond.

Please Log in or Create an account to join the conversation.

More
10 years 4 months ago - 10 years 4 months ago #6 by Chris
Replied by Chris on topic Error 500
Did you check that you added all Joomdle funtions in Moodle to the service and that the joomdle authentication in moodle is installed.
Last edit: 10 years 4 months ago by Chris.

Please Log in or Create an account to join the conversation.

More
10 years 4 months ago #7 by Antonio Durán
Replied by Antonio Durán on topic Error 500
Error 500: Check permissions in joomdle folder in Moodle. In some hostings, setting permissions to 777 or similar will cause an error 500.

Password problem: this may be related to a bug I found yesterday, introduced in Joomdle 1.0.3. We will release 1.0.4 with a fix as soon as we can.

Please Log in or Create an account to join the conversation.

More
10 years 4 months ago - 10 years 4 months ago #8 by inesh
Replied by inesh on topic Error 500
Chris -- Yes I checked that all Joomdle functions were added to the Moodle service.

Antonio -- Glad to hear that there's a fix coming for the password glitch. For the joomdle folder in moodle... yikes! Permissions are 777. I have changed permissions on folders and files in the joomdle folder on moodle and all is well! Thank you!
Last edit: 10 years 4 months ago by inesh.

Please Log in or Create an account to join the conversation.

More
10 years 4 months ago #9 by Antonio Durán
Replied by Antonio Durán on topic Error 500
I thought about permissions because this happened to a client last week.

How did you install the 1.0.3 package? Maybe in the process you chaned its permissions... I have checked released package, and it unzips with correct permissions.

Please Log in or Create an account to join the conversation.

More
10 years 4 months ago - 10 years 4 months ago #10 by inesh
Replied by inesh on topic Error 500
I installed joomdle through moodle's "install plugins".

And... I was too quick with my "all's well". Logging out of joomla doesn't log people out of moodle with "redirectless logout" ON. But... I switched "redirectless logout" to OFF and now it's okay.

Thank you!
Last edit: 10 years 4 months ago by inesh.

Please Log in or Create an account to join the conversation.