VaultWiki [Paid] 4.1.7 Patch Level 1

[pegasus]

Eliminate the 3 -> 4 upgrade-path: https://www.vaultwiki.org/issues/3273/
Also, a way to detect how much the server can handle would be good. XenForo's cache rebuilder keeps track of how long its been executing. If we can do something like this with the importer, that would be ideal.

Depending on the wiki, you might be able to import 1000 pages in a single request, but in other wikis, you might not be able to get 25 before the server decides PHP is taking too long. While I would love to write and recommend CLI-based imports, it's not a process we can expect the average admin to be able to tackle.

 

[Alpha1]

So server benchmark + fetch settings = number of pages per request.
Or just allow us to enter the number of pages to import per request. Please add an automatic jump to the next request.
My wiki is fairly large, but still only 800 articles. So even if it would be 25 articles per request this would be fine for my scenario. (As long as it keeps on requesting until all is done) I don't know if others have many more or not.

 

[xIsabel38]

A few questions:

If a user creates malicious pages, how will an admin know about this? Is there an alert system in place when wiki pages are created or edited?

Is there a way for users to select which template styles they want to use when creating a page? Like if I want pages for "Weapons" to all look the same can users choose a "Weapon Template" to base it off of?
Is there a Page List?
Is there any integrate between this and the Trophy system?
Is there a trail version or a way to trail this add-on before purchasing?
If purchased and disliked, is there a refund policy?
Can the folder icons in your wiki be easy changed to various other images?

 

[pegasus]

1. If you have untrusted usergroups with wiki edit permissions, you can require that new pages and edits are sent to a moderation queue first. There is an alert system in place to notify moderators when new content needs moderation.

2. It is possible to base pages off of templates, but there is not currently a way to force users to use a specific template.
3. There are many different types of page lists in VaultWiki. I'm not quite sure what you're looking for.
4. We are currently working on Trophy integration.
5. We have never released a trial version for a Beta. There will be a trial version after 4.0.0 final.
6. No. You cannot get a refund if you don't like the product. VaultWiki is a visible source product and it is very easy to make copies. Once you download it, you can't get a refund. It is like this for most software you buy in the US.
7. Yes, you can set a wiki image path and upload your custom images there.

Please remember that this is beta software. Some things may not work correctly and you should be willing to report bugs if you find them so they can be fixed promptly. If VW doesn't yet do something that you need, just make a feature request. We are constantly developing new features, and we're very open to user suggestions.

 

[xIsabel38]

1. If you have untrusted usergroups with wiki edit permissions, you can require that new pages and edits are sent to a moderation queue first. There is an alert system in place to notify moderators when new content needs moderation.

I intend to let all registered users be able to create Content.

2. It is possible to base pages off of templates, but there is not currently a way to force users to use a specific template.

Page List.

While it may not be possible to force a template, can they be selected by users to use?
Do you know of other sites besides yours that are using this product that I may be able to view?

 

[pegasus]

Special:All Pages are alphabetized: https://www.vaultwiki.org/pages/Special:AllPages
Pages per Area are by last update: https://www.vaultwiki.org/demo?do=list
Pages in Categories are grouped by first character: https://www.vaultwiki.org/pages/category/category:example?do=listing
Pages in Books in editor-defined order: https://www.vaultwiki.org/books/documentation/book:admin-manual?do=contents

A template chooser is an editor button we haven't added yet, but that would be very easy to add. We have already used implemented a page-chooser for inserting wiki attachments into pages and other posts.
Here are two feature requests that you may want to bump so that devs look into it sooner:
https://www.vaultwiki.org/issues/1730/
https://www.vaultwiki.org/issues/1291/

In the interest of our clients' privacy, we try not to share that information unless a client has said it was okay. Of the users who posted in our Share Your Site's Wiki thread, I don't think any of them are on XenForo or have even upgraded to version 4 yet. One of the best examples of our last generation product is here: http://www.runicgamesfansite.com/showwiki.php

That said, we do have a number of clients who are testing version 4 for all the platforms we support and are actively posting in our bug tracker.

 

[pegasus]

A development update:

When Beta 5 drops, all the wiki_*.php scripts (like wiki_index.php) shall be removed, and we will now route through XenForo's index.php and admin.php scripts. This was previously thought impossible to do under 1.1, but after significant refactoring it has been achieved.

This was a challenging endeavor not only because VaultWiki 4 was originally designed with vBulletin's output handlers in mind, but because VaultWiki doesn't have a static route that can be defined in XenForo's ACP (both admin-defined and user-defined routes are possible). Thankfully, and we never noticed this before, the hook init_router_public allows developers to modify XenForo's router by adding an arbitrary class to the execution chain, thus providing a level of customization nowhere near possible using XenForo's built-in Prefix handlers.

This change did simplify some of our plugin code, and allowed us to remove 4 rather significantly hackish classes that were the source of many bugs in previous releases.

In short, what does this change mean for customers?

• wiki_index.php and other clunky-looking file names are gone
• Improved stability
• Compatibility with more third-party addons
• Easier Friendly URL installation

With this change (and others I haven't mentioned that are already coming in Beta 5), we believe XenForo may with this single release become the ideal platform for VaultWiki.

 

[pegasus]

pegasus updated VaultWiki with a new update entry:

Changes in 4.0.0 Beta 5

(released September 3, 2013)

• Link multiple language versions of pages
• Wiki routed through XenForo index.php
• Wiki user criteria for trophies and promotions
• Collapse class for TABLE BB-Code
• Configurable lengths for main-tab List blocks
• Fixed fatal error in RSS feeds
• Fixed forum integrations not working
• Fixed not saving protected state for pages
• Fixed not saving approved/denied state for edits
• Fixed user tags in wiki content not sending alerts
• Fixed redirect...

Read the rest of this update entry...

 

[Rho Delta]

Is there a way to get this to look more like wikipedia format?

 

[Alpha1]

What is current status of the VW3 -> VW4 upgrade / import function? I see B5 has changed the upgrade tool: https://www.vaultwiki.org/issues/3273/
Please prioritize the functionality to allow for a stable vb + VW3 -> XF + VW4 upgrade.

 

[pegasus]

What is current status of the VW3 -> VW4 upgrade / import function?
Please prioritize the functionality to allow for a stable vb + VW3 -> XF + VW4 upgrade.

As far as I know, a direct import from vB+VW3 into VW4+XenForo is already possible using the existing VW3 importer.

Is there a way to get this to look more like wikipedia format?

I'm not sure what you mean. You can edit the Style Properties if you are looking for more of a MediaWiki "look." If you want to hide the wiki areas from the index (which would make it difficult to create pages), you can set all the Display Orders to 0. If you want to hide page lists from appearing under an area's description, you can now set the List Preview length to 0 in Beta 5. If you want to hide the List view entirely, there is a permission for that. If you want to move comments to a separate tab like MediaWiki, there is a setting for that. If you want to use MediaWiki-style syntax in your pages, there is a setting for that.

 

[Alpha1]

As far as I know, a direct import from vB+VW3 into VW4+XenForo is already possible using the existing VW3 importer.

Bug report here: https://www.vaultwiki.org/issues/3313/

 

[Alpha1]

The installation instructions included in the XF package refer to the following blog:
https://www.vaultwiki.org/blogs/55/
I'm pretty sure this ins incorrect.

The manual on your site states this:
https://www.vaultwiki.org/manual/vaultwiki-4-manual/VW4:Running-the-VaultWiki-Upgrade-Script

In the XenForo Admin Control Panel, go to the Applications tab and click VaultWiki > Run Upgrade Script.

This needs clarification. There is no such thing in the applications tab. Do you mean that the upgrade needs to take place from AdminCP > Home > List Addons > Vaultwiki > Upgrade addon ?
If so then which file needs to be used. There is an xml product in the package but its named 'stub' so this does not seem to be correct.
If the upgrade needs to take place from the VW admin panel, then this does not work because the VW Admin panel is inaccessible after upload of new files.

 

[pegasus]

There should be an 'UPGRADE' stub XML in the package now too. Users upgrading from Beta 4 should use this file to fix access to the upgrade script.

 

[Alpha1]

Doesn't work. On upgrade:

The specified add-on does not match the add-on you chose to upgrade.

On install:

Route prefixes must be unique. The specified prefix 'wiki' already exists.

 

[pegasus]

Ugh, that's the whole point. In that case, we will have to instruct Beta 4 users to:
1. Run a database query:

DELETE FROM xf_route_prefix WHERE addon_id = 'vaultwiki'

2. Then install the UPGRADE stub as a new addon, not as an upgrade to VaultWiki.

In the mean time I am updating the /library/vw/Install.php file so that it has this as a callback when installing the stub file.

 

[pegasus]

As of Beta 5 build 002, the UPGRADE stub will now remove the conflicting prefix entries before trying to add its own.

There are other fixes in build 002 as well.

 

[masterchief]

I click on INSTALL and nothing happens .. where is the install script?

 

[Alpha1]

OK. I ran the query, installed the extra addon, went to the VW upgrade script and clicked 'upgrade'. Nothing happens.
I'm giving up for today.

 

[pegasus]

1-click button fixed in build 003. As before, you can always add &step=1 to the URL to exit 1-click mode if it doesn't seem to be working.