XF 2.1 Fatal Error out of the blue

Luchian

Member
Hi guys,

I finally took the chance for a long overdue update during this winter break.
I was running XF 1.5.2 without any issues since its release.
Decided to first update to XF 2.1.2 (since I was still having the license), and next month to finally migrate towards latest version.

Update went smooth (previously did a test locally), as you can see below
pre-update.webp
succes.webp

I have then installed Resource Manager and Featured Threads addons.
Everything running smooth: I have uploaded resources, I have posted, I have edited messages, all, for almost the entire day.

Then, simply being in Admin panel, I was trying to create a second NOTICE (Communications > Notice), and out-of-the-blue, I got this error:
Code:
Fatal error: Uncaught XF\Db\Exception: MySQL statement prepare error [1146]: Table 'my_community.xf_data_registry' doesn't
exist in /var/www/html/src/XF/Db/AbstractStatement.php:217 Stack trace: #0 /var/www/html/src/XF/Db/Mysqli/Statement.php(196):
XF\Db\AbstractStatement->getException('MySQL statement...', 1146, '42S02') #1 /var/www/html/src/XF/Db/Mysqli/Statement.php(39):
XF\Db\Mysqli\Statement->getException('MySQL statement...', 1146, '42S02') #2 /var/www/html/src/XF/Db/Mysqli/Statement.php(54):
XF\Db\Mysqli\Statement->prepare() #3 /var/www/html/src/XF/Db/AbstractAdapter.php(94): XF\Db\Mysqli\Statement->execute() #4
/var/www/html/src/XF/Db/AbstractAdapter.php(175): XF\Db\AbstractAdapter->query('\n\t\t\tSELECT data...', Array) #5
/var/www/html/src/XF/DataRegistry.php(138): XF\Db\AbstractAdapter->fetchPairs('\n\t\t\tSELECT data...') #6
/var/www/html/src/XF/DataRegistry.php(83): XF\DataRegistry->readFromDb(Array, Array) #7 /var/www/html/src/XF/DataRegistry.php(226):
XF\DataRegistry->get(Array) #8 /var/www/html/src/X in /var/www/html/src/XF/Db/AbstractStatement.php on line 217
:confused:

What are my options/chances now?
Thank you for any opinions that could help solve this.

Notes:
the updated site is on a new VPS, the DNS migration might not have been final yet? - still, should not lead to this?
if it came to worst case scenario, I have a db backup, but it's from before the update.
 
Back
Top Bottom