Upgrade issue 3.2 to 3.3

[thndrbck]

Discussed in #640

^{Originally posted by thndrbck January 7, 2025}
I did an in place upgrade of PM version 3.2 to 3.3.
None of the documents I had uploaded, nor the folders I had made in 3.2 were visible in 3.3.
I downgraded back to 3.2 and everything was back to normal.

I'm using Portainer to manage my containers. I followed the procedure for upgrade that I've used in the past to go from 3.0 to 3.1 to 3.2. I have that procedure documented and it's worked in the past.

Any advice on upgrading will be appreciated. Need the field feature.

[ciur]

The problem is that i renamed all underlying database tables in 3.3.

Basically table "core_user" is now "users", "core_basetreenodes", is now "nodes". "core_folders" is now "folders" etc.

So, yes, it won't work just to change the docker image.

[thndrbck]

I see also that 3.2 uses SQLite database and 3.3 doesn't.
So what's the best way to bring my instance up to 3.3?
Will a backup of 3.2 restore to 3.3? If so, Is there anything to be done with the persistent folders?

Thanks.

[ciur]

No.
But I will fix the import into 3.3 part; it is not that complicated.
Currently I am busy with updating landing page and adding an online demo instance. Once I am done with that, I will deal with import from 3.2 into 3.3 issue.

[thndrbck]

Thank you. I'll keep checking back.