Our problem is that we had version 3.9.0 downloaded from Github and it was working fine. We did the update by moving the files via ftp. And now it is impossible to login to Admin account via oc-admin. A regular user can log in to his account
In config.php we added this:
// Enable debugging
// define ('OSC_DEBUG', true);
// define ('OSC_DEBUG_DB', true);
// define ('OSC_DEBUG_LOG', true);
But it doesn't show bugs on the frontend
The server log shows: Got error 'Passing INI directive through FastCGI: unable to set' register_globals ''

@qq
1) you must uncomment those lines
2) you should discuss with hosting how to enable showing error on your server
3) make sure your t_admin table match to definition of oc-includes/osclass/installer/struct.sql file

@qq
1) you must uncomment those lines
2) you should discuss with hosting how to enable showing error on your server
3) make sure your t_admin table match to definition of oc-includes/osclass/installer/struct.sql file

About the massacre. After restoring files to version 3.9.0, you still cannot login to oc-admin. Is anything left in the database?
Now we have found another bug. User cannot create an account because ...... You must accept our "Terms and Conditions" and "Privacy Policy"
There is no such field to check in the template.

There are no such fields even in osclass, I think you little bit panic.
Before any upgrade you should backup files and databse. After upgrade you validate if everything works properly.
In case of some issues, you revert back using backups.
To avoid any problems with production websites, you have copy on some testing subdomain where you can validate upgrade if working properly.

Yrt you have not even shown how problem can be reproduced, what is your url, what message ate you getting, if upgrade finished without any issues...

There are no such fields even in osclass, I think you little bit panic.
Before any upgrade you should backup files and databse. After upgrade you validate if everything works properly.
In case of some issues, you revert back using backups.
To avoid any problems with production websites, you have copy on some testing subdomain where you can validate upgrade if working properly.

Yrt you have not even shown how problem can be reproduced, what is your url, what message ate you getting, if upgrade finished without any issues...

I just installed the clean version as a test and it turns out. I can't login to oc-admin
But shit!


How many times can you write the same thing? I don't waste my time clicking here unnecessarily. I thought the standard from osclass.org has changed, but no. The continuation continues, embarrassment!