Small Issue

**therock67** · January 4, 2010

Hi

I'm currently testing VB4 in a test directory so was waiting for vaultwiki before going live with update.

Upgraded straight from 2.5.0 to 3.0 Beta which I probably shouldn't have done and got an error Table '[databasename].vbvault_upgradelog' doesn't exist. I guessed that was from skipping versions so I uninstalled vaultwiki and ran a fresh install on the test forum.

Because it's just a copy of the database it has a few issues, like it's autolinking to the old wiki (which is still there on the live site) for some articles from the vb4 forums so I presume that's just caching issues and will disappear when I upgrade the live site. I then linked the new wiki back to the existing forums on the copy database. Apologies if that's just a stupid thing to do but I'm just testing things before upgrading.

However for the articles that are linking to the v3 vaultwiki I'm getting the below error message (either from clicking through autolinks or from accessing the forum directly by typing in the URL) and then clicking on an article. Apologies if this is entirely related to testing the wiki on a test forum but I just thought I'd let you know in case it was something else:

Error message:

Code:

Invalid SQL:
                       SELECT IF(thread.visible = 2, 1, 0) AS isdeleted,
                       post.pagetext AS description,
                       thread.*
                       , NOT ISNULL(subscribethread.subscribethreadid) AS issubscribed, emailupdate, folderid,
       commenter.usergroupid AS lastusergroupid,
       commenter.membergroupids AS lastmembergroupids,
       commenter.homepage AS lasthomepage, commenter.email AS lastemail,
       IF(commenter.displaygroupid > 0, commenter.displaygroupid, commenter.usergroupid) AS lastdisplaygroupid,
       protected.options AS protection
                       FROM vbthread AS thread

                       LEFT JOIN vbpost AS post ON(post.postid = thread.firstpostid)
       LEFT JOIN vbvault_article AS article ON (thread.threadid = article.threadid)
       LEFT JOIN vbdeletionlog AS deletionlog ON (deletionlog.primaryid = thread.threadid AND deletionlog.type = 'thread')
       LEFT JOIN vbsubscribethread AS subscribethread ON (subscribethread.threadid = thread.threadid AND subscribethread.userid = 32  AND subscribethread.canview = 1)
LEFT JOIN vbuser AS commenter ON (article.lastposterid = commenter.userid)
LEFT JOIN vbvault_protect AS protected ON (protected.targetid = 15439)
                       WHERE thread.threadid = 15439;

MySQL Error   : Unknown column 'article.lastposterid' in 'on clause'
Error Number  : 1054

**pegasus** · January 4, 2010

Did the upgradelog error message halt the upgrade or was it only in a log or report?

As for your article.lastposterid error, in vault/special_plugins.php, find:

Code:

$hook_query_joins .= "\r\nLEFT JOIN " . TABLE_PREFIX . "user AS commenter ON (article.lastposterid = commenter.userid)";

Replace with:

Code:

$hook_query_joins .= "\r\nLEFT JOIN " . TABLE_PREFIX . "user AS commenter ON (" . (VAULT_40X_COMPAT ? "thread" : "article") . ".lastposterid = commenter.userid)";

**therock67** · January 5, 2010

Originally Posted by pegasus

Did the upgradelog error message halt the upgrade or was it only in a log or report?

As for your article.lastposterid error, in vault/special_plugins.php, find:

Code:

$hook_query_joins .= "\r\nLEFT JOIN " . TABLE_PREFIX . "user AS commenter ON (article.lastposterid = commenter.userid)";

Replace with:

Code:

$hook_query_joins .= "\r\nLEFT JOIN " . TABLE_PREFIX . "user AS commenter ON (" . (VAULT_40X_COMPAT ? "thread" : "article") . ".lastposterid = commenter.userid)";

The errorlog message appeared at the end. It said the upgrade had completed successfully but the version number in the product manager was 2.5

When I clocked on the forums (not just on a wiki forum) I just got a blank page. Nothing else.

Sorry I didn't spend any time checking for error messages or anything I just uninstalled it and did a fresh install.

The fix for the second issue worked perfectly it seems.

Thanks very much for your help.