Lazarus forum incompatible with Firefox now, but works for me, with Chrome only.

[wpostma]

Attempting to use this forum [https://forum.lazarus.freepascal.org/]  fails with a cookie error, and redirects to this page:

https://forum.lazarus.freepascal.org/cookies.html

There is no further error, and I have not disabled cookies, and I have not got adblock or any security software or security or privacy features enabled on Firefox.  It's a strictly vanilla firefox install, which used to work fine.

Anyone else?  Firefox 150.0 64 bit, windows 11.

Warren

[Handoko]

I solved it by doing these:

Move your mouse to the link you want to click. Right click, copy the link and paste it to a text editor. The link will look like this:
https://forum.lazarus.freepascal.org/index.php/topic,73678.msg581265/topicseen.html?PHPSESSID=aa35pqmo16d08j4kfmi4oe47b7#new

Remove the part started from ?PHPSESSID to the end. So it should like this:
https://forum.lazarus.freepascal.org/index.php/topic,73678.msg581265/topicseen.html

Now copy paste the new link and use it on your browser. The page should be able to show up.

But if you 'really' want remove the problem, make a login to the forum.

It works for me.

[Thaddy]

Seems to me that a browser is unable to keep up with standards?
Although I would be disappointed if that turns out to be Firefox.
Now installing...

[Handoko]

It just happened on my Firefox, Palemoon and Brave browsers after recent 504 Gateway Timeout issue. And also the forum down issue about a year ago. But it can be fixed easily following what I said above.

But if anyone want to see the error, on my test, you just need to start a private tab and browse the forum on the private tab.

[Thausand]

make click reload before new tab open or reload before login forum with firefox (login no mandator but else not possible for login). As write handoku this is happen when protect for bot activate.

[Datalore]

Well,

Same problem here, i'm copying links and removing PHPSESSID and everything after it for about everything now.
It was already annoying when cookies were enforced but this is becoming onworkable, cookies are not disabled here either.

Let's be fair..... It's a bit easy to say: "use another browser", "do this", "do that", "don't use the forums then"

I also think the logic "Bots don't use cookies so this'll be another hurdle" falls flat on it's face considering the above removal of PHPSESSIONID part of links will get you to the content, just a line of extra code.

There's a problem created server-side, it's ditched to the user now.

[PeterEvans]

I have been having trouble logging in for days now.
I see the same page that #Handoko sees.

(1) in Firefox in Settings I enabled cookies for this forum. This did not work.

(2) in Firefox when I see the page. Move mouse to address line. Back space the characters for the cookie page. Hit enter. This sometimes works.

[dsiders]

It was already annoying when cookies were enforced but this is becoming onworkable, cookies are not disabled here either.

It is Firefox that is totally disabling ALL cookies. You can circumvent that in their cookie settings by creating an exception for the forum website. It has some bullshit marketing name... but I can't recall what it is at the moment.

[Thaddy]

It is Firefox that is totally disabling ALL cookies.

That is actually a laudable feature. It encourages to maintain state serverside instead of laying the burden on the client.
We actually implemented that years ago at our bank.
Why? "legitimate interest", amongst others, also read available cookies and that potentially leaks information. Even the presence of a cookie is an information leak.

I can imagine there are people that can not imagine a life without cookies, though.
But they are technically not strictly necessary, they are a convenience for developers/serverside users.

[swissbob]

It is Firefox that is totally disabling ALL cookies. You can circumvent that in their cookie settings by creating an exception for the forum website. It has some bullshit marketing name... but I can't recall what it is at the moment.

Nope.  I have the same problem on both Chrome, Safari and ViValdi as well.  Sometimes you get the cookies error dispite having them turne on.  Go back a couple of minutes later and it works. 

[Datalore]

DSiders,

Thank you for proving my point. "Just do this.....", problem ditched.

I hope you realise there are a fair amount of users who resort to handoko's method of cutting the PHPSESSID part of links which, if you ask me, is not a really normal use of links?

The whole argument has bit of a "You're holding it wrong" feel to it. As i stated earlier, cookies aren't even disabled here. It's checked, checked, double cheched. and when i was absolutely sure.... I checked it again. Blame firefox all you want, if chrome and vivaldi users have the same problems..... perhaps it may not be firefox but a well-intended but not so great executed change server-side.

There's also the "Bot's don't use cookies" logic fallacy which is easlily bypassed with a oneliner. Again, cut the PHPSESSID part from the link and a bot has access to the content, yet users are dancing naked in the moonlight shaking their tambourines.

I get that this policy was enforced with all well-meaning in mind, i just doubt this was the intended effect.
Or are we so seriously indoctrinated that cookies are so convenient that no matter at what cost, the end justifies the means?

[dsiders]

Or are we so seriously indoctrinated that cookies are so convenient that no matter at what cost, the end justifies the means?

You're free to use whatever thing you choose... even if it is enshitified. I don't care one way or the other.

[Marc]

There's a problem created server-side, it's ditched to the user now.

Nope, there is no server problem, there is an internet problem and the only way for the forum to survive that is to require cookies (for now).

[lar]

What works for me on Firefox is to right-click on the Forum's bookmark (assuming you have one) and select "Open in new private window".

[Arend041]

I only have no problems with the forum in Firefox when I'm logged in.