If VaultWiki breaks your site, submit a ticket through the Members area of the VaultWiki web site, and the devs will usually try to fix both your site and VaultWiki for free.

@alfieb, thanks for reporting that issue with BB-Code parsing. It only occurred in the Lite version.

In vault/core/model/tag/vw.php, find:
Replace with:
I have uploaded a fixed ZIP now.

Tried again. Fresh install. Replaced the vw.php file. BBCodes are still broken.

The issue seems to be related to that file, because I was able to disable the plugin and delete that file, and now my BBCodes work without having to fully uninstall like I did the last time.

I don't know then. It works on my install with the new file. If you still have issues, then you will definitely have to request Ticket Support service as it's probably a conflict with another mod or a cache issue on your site.

How do i install it?

README says:


Installation
------------
1) Follow the instructions at:
https://www.vaultwiki.org/manual/vaultwiki-4-manual


but


Error 404 - Page Not Found
The requested page http://www.vaultwiki.org/manual/vaultwiki-4-manual cannot be found.

Thanks for reporting that issue. That URL should now redirect you to the correct location.

When will you have the V4 documentation on-line?

We installed the paid version a couple days ago but we are confused as to how to properly set it all up and maintain it.

D.

Someone is currently working on it. We wanted to have it ready at the same time as our gold release (which is the next release). I will see what I can do to accelerate this process and hopefully have it online before the holiday.

In the mean time, if you have a question about performing a specific task, I would be happy to answer it for you.

VaultWiki Lite is now gold/stable with 4.0.0 (released January 1, 2015)

• Content Feeds for Showcasing Wiki Content
• Fixed URL rebuild not clearing post cache
• Fixed Javascript breaking with PHP Suhosin patch
• Fixed some illogical permission stacking for wiki headers
• Fixed 'Patch Level' in version name breaks forward compatibility
• Fixed notifications not sending in various situations
• Fixed various PHP notices
• Fixed admin panel suggesting install-dir removal during upgrade
• Fixed can't WIKI link to the index
• Fixed DDoS still possible within small window
• Fixed race condition in permission cache
• About 40 other bugs are fixed

Hello! I installed your wiki and I dont know why but it works HORRIBLE on my vb4

I want to unistalled because the the wiki I dont know how, but it disabled the BBCODES, and all my posts are in html right now...

The problem is that the link that you give to the people for uninstalling it doesnt work... Please can you helpe with that? Thanks.

There aren't that many code changes in today's update. It's mainly a re-upload because some required files were missing from the last upload.

Let me re-iterate for users STILL experiencing the disabled-BB-Code issue. I cannot reproduce this issue on my test board. If you are experiencing this issue, I recommend setting up a test board that has this issue and filling out a Support Ticket over at the VaultWiki support site. It cannot be addressed without access to a board that has the issue. We have tried multiple times now to resolve this just by guessing what might be happening, and some users are still reporting problems, even on new installations. So if you have this issue, a Support Ticket is needed.

Just wondering where the xml file is for it

There is no XML file. vBulletin doesn't support multi-page install XML which is needed for better installation performance, so you must run /vault/install/index.php in order to install it.

Thanks for the info

Just posted: VaultWiki Lite v4.0.1 (released January 28, 2015)

• Fixed cached forum content showing as unparsed
• Fixed fatal error viewing discussion with comment by a deleted user
• Fixed missing error handling for some admin panels
• Fixed WYSIWYG editor using wrong character encoding
• Fixed global feeds only editable by moderators
• Fixed cron cleanup not using indexes
• Fixed feed content not adhering to search engine rules
• Fixed fatal error with some custom VW_DEPS_PATH values
• Fixed inability to name wiki content '0'
• Fixed CSS with PHP Suhosin path
• Fixed unexpected last-info for some update types
• Fixed some caches empty after install
• About 70 other bugs are fixed

Let me reiterate for everyone that the forum BB-Codes showing as unparsed is now fixed! This was occurring for some installations after the first-reading of a post if the forum had a post cache lifetime > 0 and the lifetime had not yet been reached for that post. @AkibaWorld @alfieb @halkum

lite version is basically a demo as most features are turned off, so basically useless.
But I guess that's how these lite versions are, to get us to buy full version

Hello.

Yes, the BB-code problem is solved, thanks. But I find some erros and I posted them here, on your website.

Link: https://www.vaultwiki.org/issues/4151/

I want to tell to everybody that this mod is very cool and easy to use, but you need to improve some things.

Congrats for the mod.

Today's update is not a new version, just some small changes for 4.0.1. Most notably there was a conflict with vBulletin 4.2's Mobile Style that is now resolved.

Regarding the security vulnerability announced here: https://www.vaultwiki.org/articles/168/

The vulnerability does not affect Lite versions. If you're using the full version, you should install one of the patches mentioned in the article.

VaultWiki Lite 4.0.2 (released March 15, 2015)

• Open Graph Integration
• Updated to YUI 3.18.1
• Fixed race condition in Javascript
• Fixed database error viewing allowed child in disallowed parent
• Fixed permissions for feeds too lax
• Fixed public facing patch numbers
• Fixed issues with low PCRE recursion and backtrack limits
• About 75 other bugs are fixed

Among the issues that are fixed in 4.0.2 is a newly discovered permissions vulnerability (users can do things admins expect them not to) that was introduced with the Feeds feature in 4.0.0.

I am having a problem accessing vaultwiki.org to purchases the pro version. I checked it out on http://ismysiteworking.com and it said the site was down.

edit: site is back online, so nvm


edit: and now it is down again, not sure why one moment I can use your site and the next I can't...

Pursuant to the announcement of this vulnerability: https://www.vaultwiki.org/articles/171/

I have updated this thread with the patched version.

Updated this thread with 4.0.2 Patch Level 2, which fixes a vulnerability affecting installations on vBulletin 3. Part of a multiple-disclosure here: https://www.vaultwiki.org/articles/172/

Update: VaultWiki Lite 4.0.3 (released April 13, 2015)

• AJAX Icon Previews
• Persistent popup menus
• Updated SSL certificate when fetching external content
• 2 vulnerabilities resolved
• About 25 bugs are fixed

Full announcement here: https://www.vaultwiki.org/articles/173/

Finally got our new vulnerability database up-to-date with all known disclosed issues: https://www.vaultwiki.org/pages/Book...rable-Versions

If you aren't always able to keep up with our news announcements, you can use this page to see if the VaultWiki version you're running is vulnerable. By clicking that version, you can read more about the specific vulnerabilities and if any workarounds are unavailable.

how to download the new version of vault wiki

Version Info
Installed Version
v4.0.3 Build 001
Latest Version Available
VaultWiki v4.0.3 Build 002- Now

there is a problem when trying Rebuild Content URLs

Database error in vBulletin 4.0.5:

Invalid SQL:
TRUNCATE TABLE `vw_path`;

There is nothing "invalid" about that SQL statement. Is there more to the error message?

Update: VaultWiki Lite 4.0.4 (released May 21, 2015):

• Filter Search by Page Type
• Fixed feeds not appearing in search, activity stream
• Fixed a few race conditions
• Fixed feed chooser on Promote tab
• Fixed some errors in live search results
• About 35 other bugs are fixed

The Lite version was not affected by "Photo of Loris" or other vulnerabilities disclosed on May 21, so this is just a regular maintenance release.

Just posted the update to Lite for VaultWiki 4 RC 3, which has been out 2 weeks now. It seems to have been a pretty stable release so far, so RC might be over soon. Even so, RC 3 did not change much compared to RC 2 when looking at the Lite version. It would seem that most of the core features are already pretty stable, and that mostly non-Lite features have been having problems.

RC 3 was released last September. I would recommend updating to a newer release.

Adding data to table: vw_page

Creating required and example areas
Database Error Database error

Invalid SQL:
UPDATE `vw_counter` SET `editcount` = CASE `pageid`
WHEN 3 THEN editcount + 1
END WHERE `pageid` IN (3) LIMIT 1;

MySQL Error : Unknown column 'pageid' in 'where clause'
Error Number : 1054

I've uploaded a more recent build which should resolve this issue for users who are encountering it.

If you get a message like "A node with the title Wiki was not found" after installation, you will need to reinstall, as there was a compatibility issue for MySQL < 5.6.4 in the last ZIP, which prevented the wiki tree from being created.

4.2.3 + VaultWiki Lite 4.x, After installed/enabled, Advanced Search page appears white. Disabling VW returns functionality.

Also was confused as to how to get a similar 'index' page that is shown in the first screenshot. Only showed the primary Wiki area, and no other content.

can i place adsense code inside Wiki content pages

i get the following erro after install and try access my forum
Fatal error: Call to a member function is_cloud_cachable() on a non-object in /home/..../public_html/vb/includes/block/tagcloud.php on line 136

and when disable the forum all run good

For the tagcloud.php fatal errors, or a blank screen on search.php, run the following MySQL query:
After this change you may have to go to AdminCP > Maintenance > Clean System Cache. If you don't have this option, try running VaultWiki's upgrade script, even if you are already on the latest version, since the upgrade script will rebuild the cache too.

can i place adsense code inside Wiki content pages

You can place your adsense code anywhere you want by editing the templates in vBulletin's style manager. A good template to place ad code is vw_node_shell, because it is used on every wiki page.

In the full version, you can also place one in the sidebar by doing one of these:

• Create a "Custom HTML" type wiki sideblock and put the adsense code as the content.
• For long articles, place adsense code in between sections by adding it to the vw_block_separator template.

We recommend that you use ad code that uses DOM methods instead of document.write.

Anyone know what happens if we have the full version and our license expires?