CMP, Doodles Tutorial and connector.php producing access denied message.

Mark, THANK YOU SOOO MUCH for your post. Flushing all permissions and clearing the cookies did the trick. It works!!!

Can you elaborate on why changing session_cookie_path to a slash made this Doodles tutorial work?

Thanks again for your tidbit!

Quote from: tahoeg at Jun 19, 2013, 09:19 PM

Mark, THANK YOU SOOO MUCH for your post. Flushing all permissions and clearing the cookies did the trick. It works!!!

Can you elaborate on why changing session_cookie_path to a slash made this Doodles tutorial work?

Thanks again for your tidbit!

Others can correct me if I am wrong but the way I understand it is that by default session cookies are limited to the install path of MODx. So if you have it installed in a subfolder and your Doodles working directory is outside of that subfolder the sessions won't work on it.

By changing the session path to / your are encompassing the entire domain allowing everything access.

Brian, So by doing this that allows everything access, is there a security risk?

Quote from: tahoeg at Jun 20, 2013, 09:18 PM

Brian, So by doing this that allows everything access, is there a security risk?

I'm afraid someone else will have to comment on that. I don't know enough about it to give an accurate answer.

I can confrm that changing session_cookie_path back to "/" solved the 401 error on lang.js.php for me. (MODX created several cookies for every subdirectory, which is wrong behaviour) So I could finally login to my own website again.

I have changed my session_cookie_path to / which enables me to use my connector in the cmp of my extra but now it seems that I can't use the other pages of my modx installation in which I am developing the extra.

By changing it back (and clearing the sessions table and clearing the cache manually) I have the expected behavior that I can use the entire manager except my extra.

I have also seen that if the session_cookie_path is set to / and I open my cmp there is a new session in the modx_session table.

Hope there is a fix for that

I think I got it

seems that you have to edit the session_cookie_domain setting as well.

Good luck everyone!