Mybb Diagnostics Troubleshooting Tool

[frostschutz]

This user has been denied support.

The question I have is how we can correct them? I've tried to open for example "printthread.lang.php" which says "does not start with <?php" and I've found it starts with "<?php".

The UTF-8 Byte Order Mark is an invisible character. You want to use an editor that does not add it (or removes it if it's already there). Any programming editor will do, for example Notepad++. If your editor has a charset option, make sure it's set to UTF-8 _without_ Byte Order Mark.

[Conor C.]

That is a very cool plugin! it should be installed by EVERY mybber.

[Lo.]

I wonder, if this plugin will be included with 1.6? It would be amazing for support.

[faviouz]

Will this work with 1.6? I assume we only have to change the compatibility line.

[JonathanP]

It's not even a plugin, all you have to do is upload it to your root.

[faviouz]

Right, good point! Didn't check that. Thanks.

[n00bie]

Not sure if this is the right place to go, but anyway... in the last couple of days I came across several people who had issues with MyBB because in some file, there was either whitespace or tabs or (very evil) an UTF-8 byte order mark outside of <?php ?>. Due to the nature of PHP (supposed to be embedded into HTML), anything that is not within <?php ?> will automatically end up in the output (unless it's just a simple newline after ?> or something).

Anyhow, I wrote a small plugin that walks through all the PHP files and checks wether it correctly begins with <?php and ends with ?>. It does this when you click 'activate'. It's not very end user friendly (you still have to check the files it lists as fail manually), and the output is very ugly, but if there is to be a general diagnostics tool, maybe this is a functionality that should go in there as well, since it's very hard to debug where unwanted stuff in the output came from...

Thank you, I changed the ver to 1.6 and works like a charm

[Phantomawe]

your own plugin doesn't even end correctly...

FAIL ('/*inc/plugins/dirwalk.php' does not end with '?>')

[dragonexpert]

your own plugin doesn't even end correctly...

FAIL ('/*inc/plugins/dirwalk.php' does not end with '?>')

PHP files do not need to end with ?> to be valid. Secondly, this threads last reply was almost 8 years ago.

[s3_gunzel]

your own plugin doesn't even end correctly...

FAIL ('/*inc/plugins/dirwalk.php' does not end with '?>')

PHP files do not need to end with ?> to be valid.  Secondly, this threads last reply was almost 8 years ago.

In fact, common practice is to not end them with ?> nowadays.