Dear Seblod community,
I have been using Seblod for 2 months now, it is great as it allowed me to build a project with a real comfort on Joomla.
Currently facing a problem that a few users also met, a bit different however, I am writing to you because everything was working perfectly, until I add users to my project, and nothing of what I found on the internet worked.
Each submission of my search form (8 fields) now leads to a white page, and that famous "invalid security token" (translated from french, I guess that's it). It happened after adding a seblod user form (working fine), and so other users, one new group and one new access level. I noticed that my URL's query works like a charm when I remove the task at the end of it, which is "save2view". It gives me my results page like before, with the good results. None of the other tasks work...
What is annoying is that everything worked super fine before that, and now neither my super admin account nor my normal user account work anymore...
Could anybody have an idea about it ?
Config : Joomla 2.5.28 / Seblod 3.7.2 / PHP 5.4.45 / mysql 5.5.46.
(Caching is disabled everywhere, input max var increased too...)
Thanks for your time,
It is impossible to know what is going on without having access to your site, adding usergroup should not have any relation to security tokens, this are two completely separate things.
On thing that does come to my mind is that you should check permisisons and viewlevels set on your content type, perhaps user must be logged now after you changed that or something similar - but still should not have anything to do with tokens..
Thanks a million times for your answer, I was not expecting anybody to consider my issue before a long time...
I found out the origin of the problem ! My user registration form and my product search form had the same task on submit. Nothing was wrong with this done like this, right ? Saving then viewing your profile, allowing you to check your registration.
I changed the user registration to save & close, and then, everything came back to normal state.
Anyway, I guess search form was calling user registration task, and that must have been the source of the token not recognized... My brain is stewed fruits, I do not want to cogitate anymore on this problem, but I want to thank you for your answer, more encouraging than you thought.
Have a good day,
Cheers