Session expired or cookies are not enabled in your browser

Hi,

I have already spent two hours trying to debug the following error message :

Session expired or cookies are not enabled in your browser. Please press "reload page" in your browser, and enable cookies in your browser. Please refresh/reload page before filling-in.

The message occurs when clicking on the Pagination buttons at the bottom a CB page.

There is no Cache or any sort enabled (nor Joomla nor hosting).

I have no clue. Maybe the problem has been there for a long time but I have only been reported recently.
Latest version of everything.

I can of course give you the credentials to the website : www.ajpds.be/fr/members/list

Does all paging do this? Registration form do this? or is this entirely isolated to userlist paging?

Also ensure you've the latest CB build installed and retry. There isn't a way for that issue to happen anymore unless there's something wrong with your Joomla sessions as we no longer use cookies for spoof checks and are all contained in the Joomla session now.

Txs,

I do trust you !
But still : I have the latest version and I face this issue

I send you the credentials so that you can see for yoursel. Probably it will be obvious to you. It must be the first issue I report for 6 years or so

Txs,

Marc

Please do not send login credentials we did not request. Your issue is due to the below bug.

forge.joomlapolis.com/issues/7613

I've disabled hotlink protection in your userlist, which is a functionality we will likely just be removing as isn't really necessary especially for your install given your userlist isn't public access to begin with. Your paging links work fine now. I've also updated your install to the latest CB build as your install was out of date.

Txs a lot for the quick reaction !

It now works indeed.

I am surprised you say you had to update : CB was saying I had version 2.4.2 and that the last version was 2.4.2 as well

You had the latest stable release installed. We've had multiple build releases since then. Stable and build releases go through the same testing processes now so there's no reason not to use latest build release these days. However, our update checker won't suggest a build release if a stable release is installed (we'll be changing this behavior in a future release).