Error during database update going from v3.3.13 to 3.3.14

[Bob Jacobs]

Hi,

I've made 2 attempts to update v3.3.13 to v3.3.14 without success. Previous updates for all prior 3.3.x versions have been successful without any problems, and I have previously used the Changed Files update package (as far as I recall). This time I chose to use the Full Package update, attempted yesterday, and when I attempted to update the database I had the following error:

Screenshot 2024-11-23 151038.png

I couldn't get past this so restored the backup files and database. This morning I tried again, but this time using the Changed Files update package. When I attempted to update the database I had the following error:

Screenshot 2024-11-24 105534.png

Once again, I've restored the backup files and database. Can anyone throw any light on the reported error, please? Thanks in advance for any support.

[warmweer]

user_interests AFAIR isn't a default profile field.
Was this manually added or part of an extension?

[Bob Jacobs]

That's a good question (thanks). I did look for that when I first saw the error,

I haven't added any extensions. I also haven't added any custom profile fields for some years. In the list of custom profile fields there is a phpbb_interests field, type textarea, that appears 3 times.

I couldn't find any mention of user_interests in the database backup file.

[warmweer]

That's a good question (thanks). I did look for that when I first saw the error,

I haven't added any extensions. I also haven't added any custom profile fields for some years. In the list of custom profile fields there is a phpbb_interests field, type textarea, that appears 3 times.

I couldn't find any mention of user_interests in the database backup file.

Check the database to see if there's any data in that field. (you could also have a look at the extension table to see id there's any mention of an added extension.
If there no data, just remove the field and retry the update.

[ssl]

I couldn't find any mention of user_interests in the database backup file.

If the field is not present in the db, you must delete it in the ACP and resume the update

[Bob Jacobs]

Thanks both, I'll take a look. Cheers.

[Bob Jacobs]

I think it's in the database as pf_phpbb_interests, corresponding with the Field Identification phpbb_interests in the ACP.

I'm not sure why user_interests would be in the error message.

[Bob Jacobs]

Does anyone have any suggestions for the second error? That seems to be the one that's stopping me from updating right now. Cheers.

[thecoalman]

Just a guess but it would seem those errors would occur if it were trying to update older board The main page of ACP says v3.3.13?

This is the "Reboot windows" advice but upload the install folder, manually delete everything in the cache folder except .htaccess and index.htm and then point your browser at the install folder.

[Bob Jacobs]

Yes, the ACP confirms v3.3.13.

The "reboot windows" advice is appreciated, but was unsuccessful. Currently seeing the following error message:

Screenshot 2024-11-24 143218.png

[invenio]

Did you delete the:

store/install_config.php
store/io_lock.lock

files after the initial update failure and subsequent retry?

[Bob Jacobs]

No, I haven't deleted them. Would you recommend me deleting them and trying again?

[invenio]

No, I haven't deleted them. Would you recommend me deleting them and trying again?

My understanding is that if you don't the installer tries to pick up where it left off instead of starting new. So if you went back to a backup, it should be a clean install and those files should be removed (as the update instructions tell you to do).

[warmweer]

No, I haven't deleted them. Would you recommend me deleting them and trying again?

Absolutely. Those files reference an already started update and since that has issues, it' better to start a new clean instance.

Delete those 2 files and while you're at it also empty board and browser cache before restarting the update.

[Bob Jacobs]

Thanks both. I deleted them prior to the initial Full Package update, but not for the Changed Files attempt. I'll go back and try again with a clean slate. Thanks again.