Since upgrading to 3.2.0 I've got lots of small bugs to iron out many I'm sure I haven't found yet as I just come across them as and when.
This latest one has BBCode turning off part way in a post. Okay, it's not a conventional post as it has 8878 links in it.
But they used to display fine when I was running 3.1.9
I have checked the ACP for the setting for the number of links allowed in a post.
It was set at 0, but I've now changed it to 9999
This has made no difference. I measured how many links it does allow to display correctly before stopping and it's 4973
One thing I did need to change in order to be able to upgrade to 3.2.0 was my php version on the server. Could it be anything to do with that?
The BBcode works fine 4973 times in this particular post, so if it's a problem with the bbcode it either wouldn't work at all or it should work all the time.
The size of the post is 495,167 bytes if that helps
I've copied the latter half of the post to another post so the contents are spread across two posts instead of one. Works perfectly in two separate posts, but not one.
That's because it counts both the [url] BBCodes and the URLs found in the text (e.g. the URL used in a BBCode) so you get 10000 ÷ 2 = 5000 of them. Maybe it should only count valid tags, I'd have to think about it. Originally, those limits were meant as a safeguard against the unexpected or accidental DoS.
I wrote the library that handles markup in phpBB 3.2+.
I posted about the exact same problem on my forum way back in March viewtopic.php?f=556&t=2415021 but got no replies.
At the time i thought it was a bug because the post was ok before i updated to 3.2.0 but if what you guys are saying is correct it's not a bug but a limitation in phpBB.
7 years ago I ran into a similar problem: huge posts with many BBCodes would only partly parse. Back then a limitation was the same culprit, but reporting the encounter of such a situation was not available to every supported PHP version.
Now the software can detect the limit, but again the user remains uninformed. If there's an anomaly it should be reported, not muted.
"The problem is probably not my English but you do not want to understand correctly. ... We will not come anybody anyway, nevertheless, it's best to shit this." Affin, 2018-11-20 ↑
"But this shit is not here for you. You can follow with your. Maybe the question, instead, was for you, who know, so you shoved us how you are." axe70, 2020-10-10 ↑
"My reaction is not to everyone, especially to you." Raptiye, 2021-02-28 ↑
AmigoJack wrote: ↑Thu Jul 20, 2017 8:20 am
Now the software can detect the limit, but again the user remains uninformed. If there's an anomaly it should be reported, not muted.
Have you considered making a Pull Request for it?
I wrote the library that handles markup in phpBB 3.2+.
JoshyPHP, the job you're doing is really good so please don't get disappointed by the claiming here.
The extension is actually simple and clear and sets limitations to maximum possible values provided by PHP platform (which is equal to removing any limitations).