trying to upgrade from 7.4 I get a page that says 'Show error 7' / table opensis.app doesn't exist at 220/2 or no loads even when meeting requirements on centos 9 stream

[fcortesjp]

Hi
I'm upgrading from 7.4 straight up to 9.1 and after indicating the database I'm upgrading from, the page goes to section where it shows the process of upgrading but after a few seconds I get this page

[fcortesjp]

just tried with the root user and I get this message now

[fcortesjp]

try upgrading from 7.4 to 9
from 7.4 to 8.0
from 7.4 to 7.6
and still error Table 'opensisic.app' doesn't exist error at 2

[fcortesjp]

same issue upgrading from 7.4 to 7.5.
what's going on?

[fcortesjp]

I did managed to upgrade to from 7.4 to 7.5 after restoring db used with 7.4.

somewhere in the upgrade code, drops most tables including the opensis.app table and it's not restoring them (assuming that it does that)

not sure what 8-9.1 upgrades do but at some point I ended up with a whole bunch of tables dropped

why?

[fcortesjp]

managed to upgrade from 7.5 to 7.6 ok
but upgrading from 7.6 to 8.0 damages db again and is causing the error : opensis.app doesn't exist at 220(/2)
Something is still not right on whatever is causing the drop of bunch of tables as part of the upgrade.

#174

[fcortesjp]

I upgraded php from 7.4 to 8.3 (I'm on centos 9 stream on a dev server), and because of that upgrade my 7.6 install doesn't load anymore, so I tried to run the upgrade option from my opensis 7.6 version to opensis 8.0 on that server but after the upgrade process I get a sort of blank page

the only php version so far that seems to play well with opensis is 7.4
yet, in your documentation it says it needs 8.x

why??

[fcortesjp]

also.. somehow enabling display error in php.ini doesn't seem to show any errors.. I wonder why that is
should I consider migrating to ubuntu or something?. what is everyone using?

[fcortesjp]

my server enviroment is centos 9 stream

[fcortesjp]

I managed finally to complete the updates until the last version (9.1 at the moment). !!!!!!

here are my 2 cents if someone finds themselves in the same situation:

I was on 7.4 looking to update up to 9.1
I managed to update ok to 7.5 and 7.6 using the zip downloads from https://github.com/OS4ED/openSIS-Classic/releases, but moving fro 7.6 upwards was causing issues ( error 7, app table not found ... blank pages.. etc)
what I did was

• I managed to update from 7.6 to 8 by using the 8.0 version updated (not the one seen on the release page but this one: https://github.com/OS4ED/openSIS-Classic/tree/Version_8.0, this one includes fixes, in particular fix Upgrading to 8.0 from 7.6 fails - Table 'opensis.app' doesn't exist error at 2 #174 in the install folder which includes updates in the Upgrade.php file and other files
• after I updated to opensis 8.0 version fixed I also had to update my php version (i was on 5.4 and I had to move up to 7.4), something that tells you that you need this php update is when you start seeing blank pages after or during the update.
• after getting the 8.0 fixed updated version. and having php updated i was able to complete 9.1 update.

No access/login issues found when moving from 7.6 to 8 and then 9.1:

after I updated to 8.0 I noticed I was not able to login with my admin password, I managed to update my password by using the 7.6 install (still on the prod server) so I could use that logged in session to login to opensis 8, then from 8.0 I wen to the staff module and i managed to I reset my own password which then allowed me to login fine on 8.0 and 9.1 later installed.. so make sure not to remove your 7.6 installation so you can use that to login if you lose your admin access after 8.0 install, I figure the php update might have broken something on how login works normally, I figure my users might need to have their password reset but at least the admin (myself) have the chance to complete that task now.

good luck and make sure to backup your database prior doing anything!!!!!, I had to restore the db at least twice while trying to update my installs because while trying to update, the upgrade script was wiping database tables if something was not right which led to the app table error reported here and on other issues. hopefully that can be checked on future update procedures.

this issue can can be closed if needed.