Upgrade and compatibility questions

[tommythejoat]

I have been neglecting both the vBulletin software and VaultWiki for quite a while now and the performance of the site is declining and we are getting lots of javascript related errors in the site error log.

Rather than try to fix everything that seems to be broken, I want to upgrade to the latest vB 4.2.4 and VW 14 releases. does anyone have some advice on how to go about doing this.

We have several important Wiki articles that have gotten broken from the overuse of vBulletin attachments. In some cases several generations of history have been lost. i.e. there used to be 15 revisions and now there are 6.

I do not mind making fixes to the php code or the database but keeping track of all the variable in the process is becoming difficult and as I mentioned in another thread, I have not succeeded in getting much help.

I am also redoing my personal web site to use responsive design and would like to have our Message Board and Wiki become responsive facilities with good support for smart phones.

[pegasus]

1. Upgrade vBulletin.
2. Upgrade VaultWiki: Download the latest version from here, upload the contents of the upload/ folder to your site, navigate to /vault/install/index.php, and follow the onscreen instructions.

For both of these, you are not so far back that I would anticipate any problems. If you just want to hire us to do the VaultWiki upgrade for you, we still offer paid Upgrade services in our Members area.

Regarding any pages where revisions have disappeared, if this problem persists on the current version, you would need to submit a ticket with a link to a page with this problem so we can look into it. The most common reason for revisions disappearing, and only if they were moderated/rejected, is a change to permissions. However, I suspect that you have probably checked already.

I cannot speak to responsive design under vBulletin. From my understanding, the default vBulletin style does not provide this. However, vBulletin does have a mobile style that should be triggered when visiting the site on smart phones.