PDA

View Full Version : Solved Tables doesn't exist



sergarch
19-09-13, 20:42
Hello!

I tried to upgrade vBet and got 2 strange DB errors.

Here the number 1, when I tried to move vBet DB to external DB:

When I clicking "History" under "vBET Manual Translations" in admincp, I am getting this error:


Database error in vBulletin 4.1.12:

Invalid SQL:
SELECT COUNT(*) AS total FROM vbenterprisetranslator_cache_changes WHERE totext LIKE '%' ESCAPE '|';

MySQL Error : Table 'forum.vbenterprisetranslator_cache_changes' doesn't exist
Error Number : 1146
Request Date : Thursday, September 19th 2013 @ 11:28:21 PM
Error Date : Thursday, September 19th 2013 @ 11:28:21 PM
Script : http://www.xpam.org/admincp/vbenterprisetranslator_manualtranslations_history.php?do=history
Referrer : http://www.xpam.org/admincp/index.php?do=nav
IP Address : xxxxxxx
Username : xxxx
Classname : vB_Database
MySQL Version : 5.0.51a-24+lenny4




The 2 on is this:


Database error in vBulletin 4.1.12:

Invalid SQL:

UPDATE setting
SET value = '1'
WHERE varname = 'vbenterprisetranslator_cache_external_use';

MySQL Error : Table 'vbetcache.setting' doesn't exist
Error Number : 1146
Request Date : Thursday, September 19th 2013 @ 11:07:04 PM
Error Date : Thursday, September 19th 2013 @ 11:07:04 PM
Script : http://www.xpam.org/admincp/options.php?do=dooptions
Referrer : http://www.xpam.org/admincp/options.php?do=options&dogroup=vbenterprisetranslator_cache_external
IP Address : xxxxxxxx
Username : xxxxx
Classname : vB_Database
MySQL Version : 5.0.51a-24+lenny4

I tried to update product-vbenterprisetranslator.xml several times, disable all plugins one-by-one, searched your forum here for solution...

Please help!

Marcin Kalak
20-09-13, 12:35
Hello - we need to investigate this. Please note that it can be our bug - I'm not sure that manual translation was tested with external database configuration. We will check it and let you know.

It seems like when you made update of settings then it is used external database (which do not have vB tables just vBET) and when you are trying to get history then it is used normal database, where the table do not exists. We will check it and find solution for you.

Marcin Kalak
08-10-13, 12:09
We have fixed the issue. This fix will be added to the next release. This fix is too big to make quick fix. Please wait for the next version of vBET.

AfrikaansAlbanianArabicBelarusianBulgarianCatalanChineseCroatianCzechDanishDutchEnglishEstonianFilipinoFinnishFrenchGalicianGermanGreekHaitian CreoleHebrewHindiHungarianIcelandicIndonesianIrishItalianJapaneseKoreanLatvianLithuanianMacedonianMalayMalteseNorwegianPersianPolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwahiliSwedishTaiwaneseThaiTurkishUkrainianVietnameseWelshYiddish
Multilingual community supported by vBET Translator 4.9.2