[EliasAlucard]

Originally Posted by thincom2000

Make sure your PHP version is at least 5.3. VaultWiki's source code won't parse on lower versions.

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.

I'm on PHP 5.4... and no, I didn't get that far. Just the sign in and then blank.

By the way, is it possible to export VaultWiki's article database to MediaWiki? You know, if I'd change my mind later.

[thincom2000]

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.

[thincom2000]

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.

[thincom2000]

Originally Posted by EliasAlucard

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.

We have heard your concerns and there is now a sub-section in the current EULA to cover this:

In the event of compulsory liquidation of ownership, currently Cracked Egg Studios, LLC, on the grounds that the number of members falls below the minimum prescribed by statute, the Software shall thereafter be released to the community under the GNU General Public License version 3 to continue the project and do with as they please.

This has also been a serious concern of ours, because VaultWiki was created under similar circumstances to what you describe. The owner of a software called NuWiki mysteriously disappeared, and because of a proprietary EULA, myself and a few other users of that software pooled our resources to create VaultWiki from scratch. We don't want VaultWiki to die out, even if we do.

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.

[thincom2000]

The Lite version of Gamma 6 has been posted today, above.

(released June 8, 2014)

• Status Icons are now Font-Based
• Serious error fixed: removing old revisions deletes the entire page
• Fixed Bug: race condition - AJAX requests occur before AJAX params are ready
• Fixed Bug: bbcode does not have options field in Lite version
• Fixed Bug: index URL caches with guest session attached
• Fixed Bug: invalid index URL for guests with cookies disabled
• About 30 other bugs that weren't limited to vBulletin are fixed

[ywwz]

Ah.... I got this when trying vault/install/index.php

Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM in /home3/name/public_html/mywebsite/forum/vault/core/model/vw.php on line 308

My PHP version is 5.4.29
What should I do [email protected]@

[thincom2000]

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:

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

Replace with:

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

[ywwz]

Originally Posted by thincom2000

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:

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

Replace with:

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

Thank you so much for your professional help, I'll try these code first and contact my site hoster if necessary. All the best!

[thincom2000]

The Gamma 7 version of VaultWiki Lite has been posted today, above. Here are some details of the release:

(released July 1, 2014)

• HTML5 MicroData in Wiki Pages
• vw_additional.css for easier CSS overrides
• Opt Wiki Areas In/Out of Web Search Results
• Improved CSS caching
• CSS separated into multiple templates for easier management
• fatal error searching wiki content in vB3
• word wrap occurs in CODE blocks
• word wrap is not multi-byte safe
• About 25 other bugs that weren't limited to vBulletin are fixed

[halkum]

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.

[halkum]

Nevermind, I was running PHP 5.2. Updated and looks to be working correctly now.

[halkum]

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.

[thincom2000]

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.

[thincom2000]

Originally Posted by halkum

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.

The error message refers to an incorrect file name, but the message means that VaultWiki is having trouble automatically finding your vBulletin root directory.

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"...

[thincom2000]

Release Candidate 1 has been posted today. Here are some of the changes in this release:
(released July 28, 2014)

• History updated: more detailed and user-friendly
• Fixed setting rebuilds in Debug Mode
• Fixed fatal error subscribing via tab
• Fixed sample area being invisible
• Fixed signatures failing to parse
• Fixed database error previewing new pages
• About 35 other bugs that weren't limited to vBulletin are fixed