[Solved] Moodle update to 2.0.6 XML-RPC -Wrong Auth Token

Gentleman,
I updated my Moodle 2.0.4+ site to 2.0.6 on my test server, running Joomla 1.5.23 and Joomdle 0.6

After update, all seems well on Moodle, but the site fails authentication with XML-RPC Error (0): Access control exception.
Joomdle System Check reports Joomdle Web Services fail with Wrong Auth Token.

Reviewed token in Moodle and Joomdle, and both were correct. Deleted and recreated token, same result.
Reviewed Moodle setup, Joomdle Connector user, permissions, all correct.
Moodle Manage Enrol Plugins lists Joomdle, but it is in red and does not allow editing.

Reviewing the 'old' Moodle files there was a Joomdle folder in the /enroll folder, but none in the 'new(updated)' Moodle /enroll folder. I copied the /enrol/Joomdle folder from old to new, without success.

Any advice would be appreciated.

Paul

I don't know what can be happening, as it is clear that the error is related to the token used.... so not sure what else you can try

The enrol plugin is not related to this error.

Left it alone for a couple days. Went back this afternoon, spent about an hour comparing live server settings to test box . . .

You know how at the right end of the breadcrumbs bar it says 'In maintenance mode'? Yeah, probably should have noticed that. :sick: :blush:

Disabled Maintenance Mode, works fine.

Well, spoke too soon.

Authentication is working, but Virtuemart checkout is not recognizing login, and is asking for account creation.

IF not logged in, it will ask for login during checkout, and after login it asks for account creation anyway?

Any advice would be appreciated.

Paul

Hi,

Thanks for the info on maintenance mode, I am sure it will help others in the future.

As for VM: it does not seem relatedto Joomdle...
I would check the URL to be sure that there is no domain changing going on (going from www.site.com to site.com or viceversa)

I think your right. It seems to be a Virtuemart bug.

Appears limited to the same account I keep testing with. New registrations work; other accounts work when logged in.

Some kind of cookie or session handler issue.

Otherwise, seems fine.

Thanks again for the help.

Paul