phpBB 3.2.0-a1 released

[CHItA]

OK, the random characters are base64 encoded. If I run the characters through a decoder I can see the source code:

Code: Select all

<?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 doesn't have any files starting like that...

[Frank Rizzo]

Yep it's defintely the phpBB files.

I just tried viewing files in the root of the forum and I think I found the problem. Some of the files such as:

faq.php
index.php
mcp.php

are all base64 encoded.

I don't know if my sftp client converted it, or the update process did. Will start again and try and find out why this has happened.

[CHItA]

Which update method have you used?

[Frank Rizzo]

Ok, confirmed this base64 problem is due to the download of modified files.

I used the From 3.1.5 - > Automatic Update Package from 3.1.5 - zip

from here: https://area51.phpbb.com/downloads/

Running the update process states that faq.php, index.php ... are modified and do not represent the original files from the old version. As to why that is I may have modified them myself at some stage. Anyway these files:

are then downloaded as a .tar file. If I then view the downloaded file it has been base64 encoded.

Of course, when I then upload the file to the server the forum is just going to display the contents (the base64 encoded characters).

As a work around for now I can

a) base64_decode the files manually
b) upload the current 3.2 files from the 3.2 source

[Frank Rizzo]

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.

----

A separate issue if someone else gets this is that I was receiving this error:

allowed memory size XXXXXXX bytes exhausted in vendor/patchwork/utf8/class/Patchwork/PHP/Shim/Mbstring.php

This happened because PHP was not compiled with mbstring. I had to recompile with the config option

--enable-mbstring

If you installed via yum you need to do this:

yum install php-mbstring

---

Anyway. Great work team.

I really needed 3.2 to happen so that I can use PHP7. If anyone wants a 15-20-25%+ performance boost for zero cost then install PHP7.

[CHItA]

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 should be fixed. Nice find, and thank you for the details, and the investigation.

[RMcGirr83]

Someone want to explain to me how to get the update package to install? downloaded the automatic update package for 3.1.6, extracted the directories to the root of the forum visited the ACP page and all I get is that the install directory is present. I don't see a way for me to be able to run the updater.

[david63]

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

That seems to start it off - but mine gave up when it said it could not delete files (not had time to look into it further)

[RMcGirr83]

Time for another ticket I suppose. Clicking on the download link to look for conflicts I get this

Call to a member function format_date() on a non-object in F:\xampp\htdocs\qi\boards\315\install\update\new\includes\functions.php on line 4168

and then the missing lang var CANNOT_DELETE_FILES

Sort of begs the question as to how this site was able to be updated.

Thus endth that.

[david63]

Sort of begs the question as to how this site was able to be updated.

And the other question - where is the changed files/database_update option?