You don't get access to support and new versions of software. Installed version of software continues to work as before.

After you decide you want to upgrade, you purchase new license and upgrade software to new version.

It's explained on their site.

so i will not return to lit version if i purchase the full version and my license expires

No, full version (whichever it is) continues to work indefinitely. Only problem is if you found bugs that affects you and you can't access support or newer version with this (or those) bug(s) solved.

From my experience, developers are very quick to solve reported bugs and you have one year support upon purchase, so you could say you're pretty safe in having working wiki version on your site, even if you don't ever plan on purchasing additional years of support.

I'm currently running VaultiWiki 3.0.11 Lite on vB 4.2.3. I plan to migrate to XF 1.5.

How do I upgrade to VaultWiki 4? What is the order of operations to upgrade and preserve my data to move to XF?

This is a good mod

Posted 4.0.6 Patch Level 2 (released October 10, 2015)

• Fixes a Denial of Service vulnerability that was introduced in 4.0.4

4.0.6 also:

• New Feature: Allow Renaming of BB-Code Tags created by VaultWiki
• New Feature: refuse to install/upgrade if Zend Opcache is poorly configured
• Changed: Merged Syntax Manager settings to BB Code Manager
• Fixed Bug: "Unregistered" created "Wiki" in Activity Stream in vB4
• Fixed Bug: editor toolbar shows 'Array' and extra separators in vB3
• Fixed Bug: list and create buttons are linked to preview length
• Fixed Bug: BB-Code button images broken in BB Code Manager in vB
• Fixed Bug: tagcloud.php fatal error on some forum pages in lite in vB4
• Fixed Bug: reinstall might use old Memcache/Xcache entries in vB
• Fixed Bug: improper URL protocol locks admins out on some servers
• Fixed Bug: truncated reason input might be invalid UTF8
• Fixed Bug: URL resolver doesn't support // protocol
• Fixed Bug: base URL starting with // doubles host
• Fixed Bug: database error viewing tag cloud in vB4

Since 4.0.5 was not uploaded here, the following also applies:

• Fixed Bug: mysql version detection not working
• Fixed Bug: editor not word-wrapping in vB4.1.4+
• Fixed Bug: quoted text should automatically be updated for expected parser states
• Fixed Bug: database error rebuilding URLs in lite
• Fixed Bug: sitemaps are missing in vB in lite

Posted 4.0.7 (released October 30, 2015)

• Permission for Contributions on Profile
• Style Properties for Wiki Icon Colors
• Fixed database error creating BB-Code with blank varname
• Fixed possible duplicate entries in area listing
• Fixed new wiki content not being indexed
• Fixed corrupt pages on activity stream
• Fixed database error viewing areas with corrupt contents

4.0.7 includes changes from 4.0.6 Patch Level 3:

• Fixed the Plagiarizer Vulnerability (HTML/Javascript injection via Permissions escalation)

Two recently disclosed vulnerabilities in 4.0.7 (Template Usage and Template Expansion) do not affect the Lite version, but Node Overload affects Lite since 4.0.0. See: https://www.vaultwiki.org/articles/181/

I have uploaded the Lite version of the patch. We recommend updating immediately.

Database error in vBulletin 4.2.3:

Invalid SQL:
SELECT * FROM `bbcode` WHERE productid = 'vaultwiki';

MySQL Error : Unknown column 'productid' in 'where clause'
Error Number : 1054
Request Date : Wednesday, December 2nd 2015 @ 03:25:16 AM
Error Date : Wednesday, December 2nd 2015 @ 03:25:17 AM
Script : http://***.ru/vault/install/index.php
Referrer : http://***.ru/vault/install/index.php
IP Address : 109.110.42.69
Username : Anton Fisher
Classname : vB_Database_MySQLi
MySQL Version : 10.1.8-MariaDB

It is not clear from your post where this was a fresh installation or an upgrade. If it was an upgrade, what was the version before the upgrade? You have also provided the error message out of context. What is the rest of the output from the progress window?

You may have noticed that it took a long time to respond to your post. There are much faster response times on the support site.