Development Discussion Board

It probably happens because the install/update directory is not readable. Please check whether that folder has the appropriate filesystem permissions, and if the problem is not that, please make a bug report in the bug tracker.

Those two versions are independent from one another, therefore there isn't any priority difference between them. The next 3.1 release should come really soonish.

Now it is in alpha, so it is very likely that it will be released in early 2016.

phpBB 3.1.x doesn't support PHP7, and will not support it. You'll have to use 3.2 for PHP7 compatibility when it is released.

Basically all these files could expose the version you are running, but that's it. The core does not store any installation specific information in those files, meaning if you have not modified those files, an attacker would know what is in those files anyway (if they now the version you running, wh...

OK, I uploaded the 3.2 version of the files (not the downloaded merged files) and all is working fine, so the issue is with the download to .tar format storing the files as base64. As to if this is due to my rig or a common problem I do not know. I created a ticket , when the patch gets merged it s...

Which update method have you used?

OK, the random characters are base64 encoded. If I run the characters through a decoder I can see the source code: <?php session_start(); /** * * This file is part ... So the problem is that raw base64 is being generated, which the browser is displaying in that raw format. That is weird as phpBB do...

At the moment, phpBB doesn't provide a REST API. This means that what you try to do is a rather difficult task. You might use a HTML parser, however, more than likely that you won't end up with a generic tool that could be used with any phpBB board. For these reasons there is no simple example that ...

You should be able to run the updater by using /install/app.php.