Joomdlehooks - causing Invalid Token warnings

Hello
I think theres a bug or something with Joomdlehooks plugin.

Step 1
Brand new joomla - working fine (3.8.3 version)
Moodle - Working fine (3.4 version)

Step 2
Joomdle Installation. 1.1.4
Moodle side, done
Joomla side, done
System Check all green.

Step 3
Login into joomla front end
Warning
The security token did not match. The request was aborted to prevent any security breach. Please try again.

Step 4
Unpublish Joomdlehooks plugin
Warning is not shown ....

Could someone help me????

Hi.

Double-check that you are using the same URL for Joomla and Moodle (https, www or not www).
You can also try using redirect-less SSO, which usually helps with this kind of issue.

using redirect-less SSO was te solution ....

Thanks for your great work. ....

Great, thanks for letting us know.

Hi,

I am also having this problem. I have both Joomla & Moodle running on the same URL and if I try using redirect-less SSO then it only logs me in to Joomla and not Moodle. This is a new installation this week using the latest Joomla, Moodle & Joomdle versions. [link] janebryancollective.janebryanbeautytraining.co.uk/ [/link].
How can I fix this please?

Many thanks
Claire

Hi.

I don't know why you have token problems, as nobody reported similar issues. Double check that you URLs are correct, and not doing any redirection.

As for redirect-less SSO: check that you have curl enabled, Joomla and Moodle are on the same domain (not one in a subdomain) and you correctly set the cookie path in Joomdle config in Joomla.

Ha! Thank you! I hadn't set the cookie path in Joomdle.

For anyone else with this problem this post gave me the final kick in the right dierection:
www.joomdle.com/forum/installation/12147...h-another-user-plugi
at the bottom is:
"For reference, we have this in the docs for the moodle cookie path field:
This option is only needed for redirect-less SSO. You will need to copy here the value that you can find in the Cookie path setting in Moodle->Site Administration->Server->Session Handling. "