|
VaultWiki Lite 4.x: Wiki for vBulletin Forums
1 Attachment(s)
VaultWiki allows your existing forum users to work together on creating and managing a site's content pages, rather than competing to make popular threads. VaultWiki is a fully-featured and fully-supported wiki add-on solution for vBulletin.
Encourage Users to Work Together VaultWiki allows 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. Create All Kinds of Content With VaultWiki, you can create general site content, user manuals for your products, wikis, eBooks, eCommerce product pages, and more. With a little imagination, VaultWiki can be purposed to do almost anything. Seamlessly Integrates With Your Community At its core, VaultWiki is an add-on product for your vBulletin forum platform. Its pages all meld with the forum's existing style. Users write new content with the same editor and BB-Codes they are already familiar with. The content is indexed by your forum's built-in search engine. And each user's contributions are acknowledged on his or her profile. Attract New Membership VaultWiki creates content and content URLs that are designed to drive new traffic to your site. With guides for search engines embedded in every page, each page preserves its value when it comes to generating traffic. Fast, Responsive Support Subscriptions come with free support in our forums and bug tracker system, and documentation is available online at all times. Paid installation and upgrade services can be ordered via our web site. Active Development The team at VaultWiki.org are actively involved in the development process. VaultWiki is constantly updated to be compatible with the newest forum software releases, to meet web standards, and to incorporate new technologies. Bugs are fixed promptly and new features come out all the time. Demo Demo link: https://www.vaultwiki.org/pages/ Depending on our mood each day, the demo may be the full version or the Lite version. License For licensing details, please see the relevant "VaultWiki Lite" sections of the VaultWiki License Agreement here: https://www.vaultwiki.org/pages/Info...ense-Agreement Features the Full Version The find out more about VaultWiki Lite's features or to purchase the full commercial version, see the comparison here: https://www.vaultwiki.org/features/ Requirements The following requirements are based on the full version. The Lite version has fewer MySQL tables, fewer files, and takes up less disk space. PHP: 5.3+ (5.4+ recommended, 5.5+ recommended for big boards) MySQL: 4.4.1+ (5.1+ recommended) MySQL tables: 75+ (for some shared hosts) MySQL max_allowed_packet: ?M+ (500K + expected language row length) Disk Space: 12M+ (1G+ recommended) iNodes: 5000+ (for some shared hosts) Memory limit: 32M+ (128M+ recommended for vBulletin) Copyright Info VaultWiki Lite places a copyright notice in your forum's footer on any page where wiki functions are used. It also places a few nag screens that admin users can see. You are not allowed to modify the source code or phrases to remove this copyright or the nag screens. You can purchase an Ad Removal and/or Branding Removal license for VaultWiki Lite from the official VaultWiki support site. Simply register an account there to access VaultWiki Lite downloads and extras such as these. Technical Support You will probably receive faster responses to support questions if you post at the official support site: https://www.vaultwiki.org/support/4X/ Using an old version? You should check here periodically to make sure there are no known security issues affecting that version: https://www.vaultwiki.org/pages/Book...rable-Versions |
Quote:
The requested page http://www.vaultwiki.org/wiki/ cannot be found. If this problem persists please contact us. Mention the error message received and the page you were trying to reach. We are sorry for any inconvenience caused and we will do all we can to fix the error as soon as possible. |
Demo link updated: https://www.vaultwiki.org/pages/
|
Hi, great work. I've been checking out this wiki software, and I'm seriously contemplating using the premium version on my forum. One important question: is it compatible with the GNU Free Documentation License? Is there any option to choose between copyleft licenses, and so on? I remember when I installed MediaWiki a few years ago, I had the choice of licensing all content between the GFDL and various Creative Commons licenses. How does it work with VaultWiki?
And how stable is it now, considering that it's still in beta stage? |
Well, I'm using old (v3) version of VW, and I can say that support you get from developer is great.
In case of a bug, you'll pretty soon receive code you need to change, so you don't need to upload new version. This version (v4) probably would need some more time to reach full stability, but has some great options. So, you can buy old one and start using it, till new version reaches desired stability. |
Quote:
Quote:
Quote:
And why should I use VaultWiki over MediaWiki? I don't like the proprietary EULA of VaultWiki. I prefer the GNU GPL, but I understand they're doing this because they want to be able to charge for the premium version. However, they could just do donations instead, would be much better. In any case, I'd like to know if there's a license option for the content created in VaultWiki. Using MediaWiki, one can choose between the GFDL or Creative Commons, how does that work with VW? |
Quote:
|
I'm trying to install VaultWiki Lite, but I get a blank page after I sign in. This wasn't of much help.
Quote:
The important question here is, why would I use VaultWiki over a hell of a lot more stable, mature, secure, powerful and open source, MediaWiki? All I need is this: https://www.mediawiki.org/wiki/Exten...rs_Integration Or this: https://vborg.vbsupport.ru/showthread.php?t=270517 To get the important vBulletin integration VaultWiki offers. I don't like VaultWiki's EULA. |
Then don't, and get out of the topic?
|
Quote:
If you want completely integrated wiki product for your vBulletin forum, there's only one wiki product you can use: VaultWiki. Others, in best case scenario, has bridges that help a bit integrating two different software platforms. About features I like very much in VW4, it's thread headers, based on forum headers, but just in threads, then handling languages. There are of course more new features, but these two are my favorites. And yes, there would be more new features, as developer listens to community. I know that for a fact, thread headers was my suggestion. |
Quote:
Quote:
VaultWiki would have been a lot more stable, mature, feature rich and powerful, had it been open source. What happens if the main author/developer dies in a car accident tomorrow, for example? Who will maintain the proprietary source code? VaultWiki will die out in such a scenario. VW's vBulletin integration is very compelling, but I think the best thing thincom/pegasus can do, is go GNU GPL v3 and ask for donations. I and many others would happily and much rather, fund VaultWiki with such an approach. |
Quote:
If there are features that MediaWiki has (vanilla or not) that VaultWiki doesn't have, you are welcomed to make feature requests. We recognize MediaWiki as competition, know it sets the standard, and that we have to exceed that standard when we can. VaultWiki was created by CES in 2007 after they used MediaWiki for a year and decided it didn't have the features they needed (granted that was MW 1.4 versus MW 1.22 or whatever it's up to now). Ignoring the forum integrations, there are many aspects VaultWiki (full) now has over MediaWiki: BB-Code, better permissions, language/translation management, book/chapter management, easier media insertion. I'm currently compiling a list of feature comparison between MediaWiki and VaultWiki. This is what I have so far (for MediaWiki, these are all "Yes" for VaultWiki). If I'm incorrect on any of these points, please let me know. If an Extension lets you do it, let me know, but the final list would only include popular and active extensions (e.g. Extension:AutoLink is no longer maintained). Here's the MediaWiki list: New Licenses: FREE Free updates: Yes Pages indexed by forum search: No Automatically create links: No Store link data: Yes Syntax uses BB-Code: No Pages use tabs: Yes Post comments: No (a talk page isn't the same as individual user comments) Show comments below: No Multiple Discussions: No Collapsible sections: No Split content: No Auto-TOC: Yes Fully parsed preview: No Editable by multiple users: Yes Edit paragraphs: Yes Protect pages: Yes Blacklist titles: Yes Pages show list of contributors: No Create categories: Yes BB-Code variables: Yes List of all edits: Yes Fully parsed versions: Yes Compare two edits: Yes Approve edits: No Revert a page: Yes Post reusable attachments: Yes Easily find, insert, upload: No View, compare, undo: Yes Write pages in any language: Extension required Translate pages: Extension required Easily switch between translations: No Keep your pages organized in multiple areas: No Use prefixes to keep similar pages unique: Yes Icons show new articles, comments, edits: No Place wiki content on other forum pages: No Moderation tools for handling multiple pages simultaneously: No Anonymous pages allow stand-alone pages: No Create synonyms: Yes (VaultWiki also lets you create them in reverse, and set expiration) Create templates: Yes Integrate templates with content using arguments: Yes Customize keyword-rich URLs: Yes Makes use of canonical URLs and 301 redirects: Yes Use RSS syndication to keep users informed: Extension required Promote wiki content with Facebook: No Add pages to Books: No Read book collections with simple navigation: No Place chapters in any order: No View statistics: Yes Look up recent edits: Yes Pages meeting various criteria: Yes List of edits made by any user: Yes User contributions in user's profile: No User can have wiki preferences: Yes Utilize wiki usage data for trophies or other promotions: No Users can subscribe to pages or discussions: Yes Users can organize their subscriptions: Yes Notifications can be sent instantly, daily, weekly: Yes Pages maintained by group members: No Private pages for group members: No Control CSS for each forum style: No Change image paths for each style: No Quickly jump to other wiki pages: Yes Watch recent wiki activity live: No View technical analysis of each page: No Find similar or related wiki content: No Customize the sidebar: No Use wiki sidebar in forum sidebar: No Specify which Special pages each usergroup can access: No Allow usergroups to edit, protect, and undo edits: Not forum usergroups Define moderators to manage new and existing content: Yes Import wiki information seamlessly: Yes Various settings let you fine-tune look and feel: Yes Fully phrased using the forum language system: separate system used Developer hooks through forum plugin system: separate system used |
A note on the MIN_PACKET (minimum max_allowed_packet value). vBulletin support has in the past recommended at least 32M, and sometimes as much as 128M, to prevent MySQL gone away and other packet-related database errors.
Some users are still using default or host-restricted packet values of 1M, 2M, or even 500K. VaultWiki now uses a dynamic minimum, calculated based on your current forum and expected query size. The most packet-expensive query in vBulletin is the one that caches phrase translations in columns on the language table. Rather than do this one column at a time, it updates all the columns at once, which quickly uses up all available packet space. To determine the requirement, VaultWiki builds this query without executing it, and calculates how many bytes it will transfer. If the current max_packet is exceeded, or only has a small margin, then VaultWiki will refuse to install. If this happens, your only option is to upgrade your max_allowed_packet. There is nothing VaultWiki can do to improve this - as I describe above, max_allowed_packet errors are due to a design flaw in the vBulletin language system. |
The first post is now updated: you can purchase Ad Removal and Branding Removal for VaultWiki Lite from the official site. If you need help installing or upgrading, you can also purchase install or upgrade services from the main site. Previously these options were only available for licensed users, but now they are available to anyone, including Lite users.
If you do purchase one of these extras, you would have to always download it from there in the future, because the Members area will automatically remove those elements for you, and the ZIP attached to this thread will not. |
Quote:
A blank page is usually due to a PHP error, but you have errors hidden. You will have to turn on 'display_errors' in your php.ini file to see them. But I suspect that the error you see is due to your PHP version being too low. If it is, we need to create a bug report, because you should AT LEAST be able to reach the screen that says your site doesn't meet the PHP requirement. |
Quote:
By the way, is it possible to export VaultWiki's article database to MediaWiki? You know, if I'd change my mind later. |
Any VaultWiki > MediaWiki tool would be a lossy conversion, since there is a lot of functionality and page types that simply don't exist in MediaWiki. We have not written something like this, but we do plan to eventually have a generic export tool that would export XML or something like that. It is not high on the priority list right now, as it's not one of those every-day features that our users ask for.
Even so, we still have to do some research to see if there is a mostly loss-less format that other wiki software might be able to import. From what I have seen, it's rare for any software to provide an export function to a competing software. For example, if you search online for a MediaWiki exporter to Dokuwiki, what you will find is: - a Dokuwiki function that imports MediaWiki - third parties that wrote scripts to do this However there is not a script within MediaWiki itself to do this. If we expect that most software and VaultWiki continues to follow this model, I am not aware if MediaWiki or other potentially intermediate software currently includes a function to import VaultWiki data. As far as the blank page, it really sounds like a PHP error. You will need to track down the error message by enabling 'display_errors' or viewing your error logs. Once you have the error you can report it here or the VaultWiki site. The VaultWiki site has faster response time. |
Just wanted to note that I uploaded a new ZIP today. Technically it's the same version, but a lot of issues getting the installation/un-installation process to run smoothly are fixed.
For example, previous versions of the ZIP could not be extracted using the WinZIP client, and there were fatal errors whenever cron jobs tried to run. These are now resolved. Also, starting with the new upload, the Javascript will be minified from now on. If you want access to the un-minified Javascript, please download VaultWiki Lite from the main support site since you can choose your download settings there. |
Quote:
Quote:
But of course, while we are alive we would like to profit from it if we can. Cracked Egg Studios, LLC is a publicly registered company, so you can with a little research find out if all of ownership suddenly dropped dead at once, like during a suspicious period of inactivity. |
The Lite version of Gamma 6 has been posted today, above.
(released June 8, 2014)
|
Ah.... I got this when trying vault/install/index.php
Quote:
What should I do ah@@ |
You might have PHP 5.4.29 installed on your server as you say, but apparently your server also has PHP < 5.3 installed, and it is using that instead for vBulletin. You will have to make sure in your Apache, nginx, or other config, that it is using the correct path to the PHP 5.4.29 binary when a .php request comes in.
If you maintain multiple versions of PHP, it is usually easier to keep track of this if the PHP path has the version number in it. But I have found that it is sometimes possible to update the wrong PHP location if you forget to set your prefixes properly when you compile the update. If this error did not occur, then the loaded page should tell you that the PHP version is too low, and the actual PHP version that is executing the page. You can try to get at least that far, so it can give you some clues about your version, by editing vault/core/model/vw.php. Find: Code:
$classname::select_child($class, $file, $depends);Code:
call_user_func_array(array($classname, 'select_child'), array(&$class, &$file, $depends)); |
Quote:
|
The Gamma 7 version of VaultWiki Lite has been posted today, above. Here are some details of the release:
(released July 1, 2014)
|
Getting this error when installing:
Fatal error: Configuration: You must insert a value for dirs.core in /vault/core.php in /home/uta/public_html/forum/vault/core/model/vw.php on line 109 Looked and there is no core.php in my vault folder. |
Nevermind, I was running PHP 5.2. Updated and looks to be working correctly now.
|
1 Attachment(s)
Running PHP 5.4 currently.
VaultWiki has been installed. I have yet to do any post installation configuration though. It seems when the VaultWiki plugin is enabled on my forums, suddenly BBCode does not display correctly on the forums. It just shows the tags around the text. I disable VaultWiki, and suddenly BBCode parses correctly. Screenshot of example of what I mean attached. |
I cannot reproduce the problem on my Lite wiki. If you can, I would advise you to submit a Support Ticket through the Members area at vaultwiki.org, so that a developer can resolve this for you.
|
Quote:
If you had some sort of open_basedir restriction which jails PHP to the vBulletin directory, this would be confusing to VaultWiki. However, from the error message, I don't see such a restriction. If you have a Windows server with PHP 5.2.4 - 5.2.6 installed, the behavior of the PHP function realpath is inconsistent in this environment. In all PHP versions below 5.3.0, realpath randomly fails to return a value, and in 5.3.1, it only works in some cases. I have logged a bug report at vaultwiki.org so that the developers can implement a workaround for these versions. Even if your PHP version is too low, VaultWiki is supposed to load far enough to tell you "your PHP version is too low"... |
Release Candidate 1 has been posted today. Here are some of the changes in this release:
(released July 28, 2014)
|
hello,
thanks for the product... but i cannot create any sections without purchasing? i noticed that you cannot do much of anything except use the wiki as a blog pretty much unless you pay... any chance of that changing? |
My understanding is that the Lite version is supposed to be like a "trial version" where most things are only possible if you pay. However, you should be able to create basic articles, link them all together, and view their change histories.
If you're having trouble performing a simple task, it might be a bug in the Lite version. If you can be more specific about the steps you are attempting, I can try to reproduce the problem and come up with a fix. |
I am just going in to the admin side and trying to create sections to see how it all works out. but no options for itl
|
VaultWiki 4 RC 2 is available today. For Lite users, it includes a bunch of stability improvements, as well as a new feature: users can give Reputation for wiki comments.
For a full list of the changes in RC 2 (not only for Lite users), see this snapshot from the tracker: https://www.vaultwiki.org/projectsea...suereportid=30 |
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.
Here's some of the relevant bits for Lite: (released September 23, 2014)
|
Getting this error when trying to install it.
Code:
Step 4 |
Thanks, I'll upload a new package tonight.
EDIT: Newer package uploaded. |
This was posted to Twitter moments ago:
"While debugging our @MediaWiki importer, we discovered that upgrades from Lite left users in non-upgraded state. Users who upgraded from VaultWiki Lite during RC should contact support for a data integrity review." Support is currently working on an alternate upgrade path to resolve affected installations without performing a re-install. |
Updated the thread here with 4.0.0 RC 4 Patch Level 1
(Released October 30, 2014)
|
Tried your product. Liked what I saw at first, but it broke my forum. I don't know if it was a conflict or what, but BBcodes simply did not work on the forum anymore.
Image codes did, but everything else did not. Tried disabling the VaultWiki, and even that didn't fix the problem, so I had to uninstall it entirely, and everything went back to normal. Like my friend EliasAlucard, I like the concept of VaultWiki because I want full integration without having multiple databases and user accounts. Since there is no MediaWiki bridge for vB4, I suppose I'll just go without a Wiki for now. I hope that I am able to reinstall it again in the future. |
| All times are GMT. The time now is 10:28 AM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
| X vBulletin 3.8.12 by vBS Debug Information | |
|---|---|
|
|
 More Information |
|
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|