Topic: Update problems to 1.2.19 - new users see blank page after login
Hey guys, I hope one of you can help me. I'm kinda embarrassed because I only just found out that all this time, I've been omitting a crucial step when doing all my updates.
But let's start with my problem. I recently updated to 1.2.19 and since then, I got e-mails from two users who had similar problems. One newly registered user reported that she wasn't able to log in to the forum anymore, she only got a blank page. Another user changed her e-mail address and also couldn't log in anymore afterwards. I tried myself and had the same problem when I registered a new test user. All old users from before the update don't have that problem.
Here's where it gets embarrassing. For all the updates I've made to PunBB (I think I started out with version 1.2.13 or 1.2.14), I never ran the 12_to_121x_update.php file. Since I have a lot of mods in the forum, I usually update through the HDIFF file. All I've been doing is edit my files accordingly and upload them to the server. A friend of mine just told me I should have run that update php file every time to make the database conform with the update. When I tried to run it now, of course I get an error message (see below). I have not made manual updates to my database.
An error was encountered
File: /www/htdocs/w0072f62/forum/12_to_1219_update.php
Line: 69PunBB reported: Version mismatch. This script updates version 1.2, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.2.6, 1.2.7, 1.2.8, 1.2.9, 1.2.10, 1.2.11, 1.2.12, 1.2.13, 1.2.14, 1.2.15, 1.2.16, 1.2.17, 1.2.18 to version 1.2.19. The database 'd0031b5f' doesn't seem to be running a supported version.
Is there any way this can be fixed without me purging my database? I'm not very experienced in that area and I'm kinda scared of losing all my posts. Of course I have SQL backups of the database from various stages, but I'd like to avoid messing with that.
Can someone help? Please?? I'd be eternally grateful!
FYI: I've reset my forum to version 1.2.17 now because it doesn't seem to have that problem. But for security reasons, I'd obviously love to go back to version 1.2.19.