Development Discussion Board

Now, what's the best course of action? Edit the old posts and re-save them so they get reparsed. You may need to add a non-space character to the post to force the update. There isn't an easy way to force a single post to get reparsed currently. If you have many of those you may try the command lin...

Thank you for the extra feedback, will add it to the comment!

Thanx DavidIQ, will start with that.

Any thoughts on the quotes within the BBCodes itself?

Hi all, https://tracker.phpbb.com/browse/PHPBB3-14740 Marc wrote a fix for this and i am very grateful but testing now and rewriting some extensions and i am noticing that, again, new messages aren't parsed correctly when using quotes in BBCodes while the OLD bbcodes were parsed correctly. Now, what...

I was still @3Di's initial question as for the future of the rewriting of the ACP part of phpbb. The thing my clients like about other packages (e.g. wordpress or joomla) is the "interactiveness" of their admin panel. The client gets the idea that the ACP sends messages of new updates and ...

Marc wrote: ↑Mon Sep 19, 2016 8:57 am Somewhere between now and probably 2020, at the latest 2038 as we'll have to fix the unix time stamps until then though.

Do you know this is actually one of that rare times you even mention a date?

Upgrade went well! No problems with migratuion times (@marc) but then again, there were no post migrations whatsoever so i guess that wouldn't be a problem now. I had a few little minor "glitches" i had to fix manually.... includes/acp_users.php includes/functions_download.php includes/mcp...

Thank you David, if i find anything, i will, as always, give feedback.

Thanks!

DavidIQ wrote: ↑Fri Oct 21, 2016 5:28 pm There's issues with some extensions and the migrations that some of them have but,

David, last question, has this prob been narrowed down. I have searched but didn't find a topic with any list that had an extensive list of extensions (or did i miss something in my search?)

(Ps, maybe the ticket status should be changed manually for now then, if it is indeed fixed and already merged then the "open status" is only a faulty flag... ;-) JIRA apparently doesn't let you change the status back to "Unverified fix". I can instead close it and mark it as fi...