Just so everyone can be on the same page - which instructions?ingeva wrote:When did your problem begin? After upgrading, following instructions to the point
Good question.kinerity wrote:Just so everyone can be on the same page - which instructions?
Yes I have. I have also tried replacing the database with a backup from another forum, and I get the same error. The backup update seems to be OK, and the forum itself is OK too, but this error message is unfortunate. I haven't tried it on the web yet; I always try out things locally first.kinerity wrote:Those are the correct instructions. Have you tried uploading fresh copies of the files again just to be sure?
The previous version is not stored anywhere - when you do the upgrade it overwrites the old version. It is your responsibility to ensure that you have a backup of both the files and database.ingeva wrote:does anyone know where the previous version is stored?
The version number can be found in several files, I just don't know which one is used. It is reported on one of the very first lines of the output from the upgrade routine.david63 wrote:The previous version is not stored anywhere - when you do the upgrade it overwrites the old version. It is your responsibility to ensure that you have a backup of both the files and database.ingeva wrote:does anyone know where the previous version is stored?
It looks like your server is redirecting the request due to an HTTP 403 "Access Forbidden" errorphpbb_debug.txt wrote: [REDIRECT_STATUS] => 403
[REDIRECT_URL] => /.err403.php
Yes, I found it. I just wonder why it isn't used by the upgrade procedure.david63 wrote:That version number is stored in the config table of the database
I wonder why on earth it would do that. After all, it looks for the root directory where there are no restrictions. Maybe I should try using the old .htaccess file ...T0ny wrote:It looks like your server is redirecting the request due to an HTTP 403 "Access Forbidden" errorphpbb_debug.txt wrote: [REDIRECT_STATUS] => 403
[REDIRECT_URL] => /.err403.php
Well, it seems like that did the trick. The .htaccess file that came with version 3.1.2 could not be used. Replacing it with my old .htaccess file and adding my special error processing file .err403.php etc. made the error disappear. The the 3.1.2 file does not contain any reference to .err403.php, which is my own special file (Gives a more elaborate error message and logs the error).ingeva wrote:I wonder why on earth it would do that. After all, it looks for the root directory where there are no restrictions. Maybe I should try using the old .htaccess file ...
I found the culprit. This was caused by a protection scheme that I have been using on higher directory levels.ingeva wrote:Well, it seems like that did the trick. The .htaccess file that came with version 3.1.2 could not be used. Replacing it with my old .htaccess file and adding my special error processing file .err403.php etc. made the error disappear.ingeva wrote:Maybe I should try using the old .htaccess file ...
LordGlissando wrote:please state where you added; 'DirectoryIndex index.php' (No quotes)
I assume that means the line was added to the start of theingeva wrote:I added
'DirectoryIndex index.php' (No quotes)
before the rest of the .htaccess file.
.htaccess
file in the root of the board installation.