Major Additions - VaultWiki: A Wiki for your forum

** THIS MOD IS NO LONGER SUPPORTED **
We are no longer developing this, a newer version is available here: https://vborg.vbsupport.ru/showthread.php?t=309676

** DOWNLOAD REMOVED **
The download attached to this thread has been removed due to known unpatched security issues: https://www.vaultwiki.org/pages/Book...-Patch-Level-2

We do not recommend using this version, and we cannot offer support for it any longer.

VaultWiki does not bridge from other wiki products (like MediaWiki, etc). It is a wiki product written just for vBulletin.

About VaultWiki
"The powerful editing options in VaultWiki allow your community to collaborate to create and publish content pages for your site. Multiple users can edit the same page, and your staff can moderate changes as they are made. VaultWiki maintains a detailed history of every page, making it just as easy to reverse unwanted changes.

Use to create general site content, user manuals, wikis... VaultWiki works by extending vBulletin's forum and permissions systems - easily create and designate forum areas for different purposes. With a little imagination, VaultWiki can be configured to do almost anything."

Features and the Full Version
The find out more about VaultWiki Lite's features or to purchase the full commercial version, see the comparison here: http://www.vaultwiki.org/features/

VaultWiki Lite cannot import data from other wiki products. If you want to do this, you'll need the full commercial version.

Requirements:

• PHP 4.4.0 or higher
• MySQL 4.1.2 or higher
• vBulletin 3.6.x, 3.7.x, 3.8.x, 4.0.x, 4.1.x, 4.2.x
• about 1 MB of space

Copyright Info
VaultWiki Lite places a copyright notice in your forum's footer on any page where wiki functions are used. You are not allowed to modify the source code or phrases to remove this copyright.

Troubleshooting and Support
While VaultWiki Lite is offered for free on vbulletin.org, you will receive faster responses to support questions made at the official VaultWiki site: http://www.vaultwiki.org/

[thincom2000]

It's working correctly for me. Make sure that .ratingBox in template vw-tabbed.css has:

	float: {vb:stylevar right};

Also if you edited any of the CSS templates before upgrading, they pretty much all need to be reverted because the CSS was rewritten.

For a close-enough list of template changes, compare to the important change list for "3.0.0 RC 2" here: http://www.vaultwiki.org/threads/2109/

[Stefanus]

Originally Posted by thincom2000

It's working correctly for me. Make sure that .ratingBox in template vw-tabbed.css has:

	float: {vb:stylevar right};

Also if you edited any of the CSS templates before upgrading, they pretty much all need to be reverted because the CSS was rewritten.

For a close-enough list of template changes, compare to the important change list for "3.0.0 RC 2" here: http://www.vaultwiki.org/threads/2109/

Thanks thincom2000, but the problem is with "Store CSS Stylesheets as Files?" if "Yes" the css problems occurs.


1.) Links in footnotes gets rendered in capital letters:

[FOOTNOTE] Military History Society [/FOOTNOTE]

Gets renderd as:

http://samilitaryhistory.org/VOL022JO.HTML

This renders the links quite useless.

2.) Links of the footnotes say [1] does not link to the footnote but revert to the main CMS page.
The link in the footnote box work fine.

[thincom2000]

1) In vault/special_class_bbcode.php, find:

		$linkbits = explode('|', strtoupper($link));
		$link = $linkbits[0];
		unset($linkbits[0]);

Replace with:

		$linkbits = explode('|', $link);
		$link = $linkbits[0];
		unset($linkbits[0]);
		$linkbits = array_map('strtoupper', $linkbits);

2) Same file, find:

		if ($this->registry->options['vault_seo'])
		{
			$return_value .= $_SERVER['REQUEST_URI'];
		}

Replace with:

		$relpath = special_fetch_url();
		$return_value .= $relpath;

[Stefanus]

Originally Posted by thincom2000

1) In vault/special_class_bbcode.php, find:

Thanks :up:

Now only the "Store CSS Stylesheets as Files?" problem that is causing some havoc.

[thincom2000]

It wouldn't make a difference what the setting is, it would pull from the same CSS templates. Also, my test board has CSS stored as files...

What is your vB version, this may have some effect? Your profile says 3.7.4...
Also, if you are using a CDN or have a far future expires header, your browser may not be loading the new CSS - try clearing your browser cache.

[Leica.Robbiani]

Hi thincom2000,

thanks for all, I did the file edits, now it seems everything is working fine.

But one thing:
The additional buttons (reflist, footnote, redirect etc.) are also present in any other forum, but without any function. I think for some users this circumstance looks like an issue.

There are two ways now:
One idea is, the wiki-editor with the additional buttons is only present in the wiki-forum, the other idea is to get the functions of these buttons to all forums. So nobody get's worry about buttons which are not working. I know my members, what they find, they will use.

I don't know, what's easier to do.

best regards

L.R.

[thincom2000]

It is much easier to remove them from the non-wiki editor. Using them outside wiki forums is not possible in the Lite release because normal vB uses the regular BB-Code parser and not the parser I included with the wiki.

I will work on this and release a patch with the change and the previous few pages of file edits some time this weekend.

[Stefanus]

Originally Posted by thincom2000

It wouldn't make a difference what the setting is, it would pull from the same CSS templates. Also, my test board has CSS stored as files...

What is your vB version, this may have some effect? Your profile says 3.7.4...
Also, if you are using a CDN or have a far future expires header, your browser may not be loading the new CSS - try clearing your browser cache.

Hi,
Version: vBulletin 4.0.3 Patch Level 1

There is a definite correlation between CSS stored as files or not, causing the problem, or aggravating the problem from somewhere else as when this is saved as files the problem occurs otherwise not.

No CDN, nor any far future expires headers used.

[Stefanus]

Originally Posted by thincom2000

It is much easier to remove them from the non-wiki editor. Using them outside wiki forums is not possible in the Lite release because normal vB uses the regular BB-Code parser and not the parser I included with the wiki.

I will work on this and release a patch with the change and the previous few pages of file edits some time this weekend.

Thanks :up:

[thincom2000]

Update released. Includes all bug fixes (see the included changelog).