Development Discussion Board

Nothing I had noticed initially, but looking at the error log of my phpBB 3.3.0-b2 upgrade of a phpBB 3.2.8 site confirms it has actually been showing the same cron.php issues too, for what it's worth. I see Dr. Death has this entered as https://tracker.phpbb.com/browse/PHPBB3-16226 now. And yes ...

https://tracker.phpbb.com/browse/PHPBB3-16207

The change in phpBB 3.2.6 which made "you must have the same session ID between receiving the login form and submitting the login form" a requirement (albeit indirectly via add_form_key() and check_form_key()) seems like it may have given us a preview ...

What is the presumed strategy that someone would be using to create human-readable URLs? Can it be as simple as packing the forum ID and topic ID into the path itself, such as /forum/81-71706/phpBB-3.x-Development/Rewrite-the-URL's-with-extensions-as-before ? Which side-steps the issue of "what if ...

Issues resolved by pulling in the updated s9e/text-formatter might deserve a mention in the Bug Fixes list that goes public.

Certain emoji characters no longer render correctly after phpBB 3.2.6 ( PHPBB3-16074 )

BBCodes using {TEXT} token in HTML tags may not work after phpBB 3.2.6. ( PHPBB3 ...

I don't believe that it is the responsibility of phpBB core to attempt to handle any and every feature that style developers, or for that matter extension developers, include in their respective developments...


That is a completely fair point and perspective for looking at situations such as ...

This discussion on phpbb.com/community connected a couple dots I hadn't put together yet: Technically a phpBB 3.2.5 and earlier style could have offered the ability to login "from any page." i.e. Your template simply needed to decide "do I want to offer a login form here", and it could successfully ...

Right now I'm focusing on situations where "the sid is appended to the URL even though a cookie-based sid is also available." Because I feel like I can duplicate this user's "the anonymous session sid when building the login form on the index page is different than the anonymous session sid phpBB ...

!empty('1'); returns true
!empty('0'); returns false


Thank you; exactly what I was failing to realize; the "or if the value equals FALSE" condition of "empty()".

I will update the user to confirm that this setting should have an effect, by essentially making all logged-out user session ...

While poking at one of the users who still have "invalid form" during login, even with 3.2.7: https://www.phpbb.com/community/viewtopic.php?f=556&t=2510746&p=15248941#p15248941

Edit: Second customer encountered same problem in https://www.phpbb.com/community/viewtopic.php?f=556&t=2511881, and same ...

Thanks for putting in such an efficient implementation of that approach; way less involved than what I had been picturing. Hopefully this does equate to less 3.2.7 upgrade friction, and ultimately fewer impacted users when S_FORUM_TOKEN_LOGIN support finally becomes mandatory again in 3.3.0.