Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
Verto Posted October 28 Posted October 28 Hello. Today I was updating the installation to version 4.7.18, but when I finished the update, when accessing the site I get the error : “An error has occurred (Error 500). We are sorry, but a temporary technical error has occurred which means that we are unable to display this site at this time. You can try again by clicking the button below, or try again later.” I modified constants.php and enabled recovery mode. I was able to access the site, but when I deactivated recovery mode, the error reappeared. I checked the php error log, and I see this error: thrown in /home/talentaaurea/public_html/system/Db/Db/Db.php on line 638 #5 {main} #4 [internal function]: session_write_close() #3 [internal function]: IPS_Session_Front->write() #2 /home/talentaaurea/public_html/system/Session/Front.php(375): IPSession->updateSession->updateSession(). #1 /home/talentaaurea/public_html/system/Session/Store/Database.php(77): IPSDB->insert(). #0 /home/talentaaurea/public_html/system/Db/Db/Database.php(941): IPS\_Db->preparedQuery(). Stack trace: [25-Oct-2024 12:04:08 UTC] PHP Fatal error: Uncaught IPSDBException: Table 'talenta_db1.core_sessions' doesn't exist in /home/talentaaurea/public_html/system/Db/Db/Db.php:638 Can you help me? Thank you and best regards
teraßyte Posted October 28 Posted October 28 Based on the error you posted, your core_sessions table is missing from the database. You should check with your hosting about how/why this happened. The table doesn't hold any significant data, so it's possible to re-create it with a simple query. But I would check if anything else is missing first. If more than that table was lost, you may need to restore a backup. Jim M and Verto 2
Verto Posted October 28 Author Posted October 28 Thank you for your help. Actually, the indicated table was indeed present in the database, but for some reason it was generating the mentioned error. I had to restore a backup and update again, to solve the problem. From what I have been investigating, the problem had to be caused by a third party plugin, which I have had to deactivate, pending an update from its developer. Thanks in any case for your interest and help. Best regards
Recommended Posts