VaultWiki

VaultWiki [Paid] 4.1.7 Patch Level 1

No permission to buy ($15.00)
@pegasus can you add some pictures of the latest release including the admin panels in ACP.
It's pretty basic. We just took the old Admin Panel, put the menu in XenForo's CP sidebar, changed the stylesheet for the panel contents, and put it under a "Wiki" tab. We didn't want to go too crazy with the changes, especially so late in RC.admin-panel-xf.webp
 
What errors are you getting? I have not tried it personally, but the author of Add-on Install & Upgrade suggested it was fixed in the last release of his mod. Otherwise, just use the standard "Install Add-on" option and perform the manual steps of uploading, etc.

EDIT: This was the post I was talking about: https://xenforo.com/community/threads/add-on-install-upgrade.35211/page-38#post-849548
It seems that it was stated to be fixed in the next release on Nov 2, 2014, but the last release of Add-on Install & Upgrade was Sep 29, 2014. So this issue is not fixed yet. You should use the standard "Install Add-on" procedures, which are also outlined in the VaultWiki Install Manual.
 
Last edited:
What errors are you getting? I have not tried it personally, but the author of Add-on Install & Upgrade suggested it was fixed in the last release of his mod. Otherwise, just use the standard "Install Add-on" option and perform the manual steps of uploading, etc.

EDIT: This was the post I was talking about: https://xenforo.com/community/threads/add-on-install-upgrade.35211/page-38#post-849548
It seems that it was stated to be fixed in the next release on Nov 2, 2014, but the last release of Add-on Install & Upgrade was Sep 29, 2014. So this issue is not fixed yet. You should use the standard "Install Add-on" procedures, which are also outlined in the VaultWiki Install Manual.
thanks for the quick reply!
 
@pegasus - any reason to fear the upgrade to the "actual" 4.0 from the current RC?

will it be a big deal? or easy as any other "standard" addon update?
 
You should not be afraid to upgrade, especially to a "stable" release. You still have to use VaultWiki's internal "Upgrade" link, but otherwise it should not be a big deal at all.
 
Hello, I have downloaded VaultWiki today for the first time and I have : 3 594 files, 1 463 directories inside the upload folder, why this big number of files please ? Thanks.
 
That sounds like the correct number of files to me. VaultWiki has a number of components in the download package that all work together to ensure cross-platform functionality:

- a modular framework made up of many basic components
- extended versions of most components within the framework to hook into XenForo
- actual XenForo add-on files
- actual VaultWiki program files

There are other things to consider that we noticed when developing VaultWiki:

#1 MVC programming tends to triple the number of files compared to procedural programming. If VaultWiki was not MVC, it would be about the same number of files as vBulletin 3.

#2 Everything in VaultWiki is modular. We probably could have combined a lot of files, but the smaller each module is, the more tuning can be done internally. This saves resources and computing power. In order to do that, modules need to be in separate files. In the future, our download page might offer the ability to exclude unwanted or unused modules, but at the current time you get all of them in the download package.

#3 If you use any kind of opcode cache (PHP comes with Zend Opcache since PHP 5.4), the number of files should have no bearing on your performance in a real-world setting.
 
for someone like me totally new to "running my own wiki"... is there an example of a "standard" setup?

like...
  • why would i create more areas? should i?
  • some samples of when to use a prefix? best practices?
  • page? book? category? special page? anonymous page? when/why would i use each?
really, i just don't know where to start to setup a "basic" wiki.

for example... say i want to start a Wiki on Game X.
  • Game X has 10 characters you can play as.
  • Game X has 4 roles each character can be.
  • Game X has 3 types of maps you can play on.
what does a basic/standard layout for this look like? the whole pages/books thing is confusing me ... :(
 
You can think of areas like forums and sub-forums. You use them to force users to pick a place to post the page for organization, and to control permissions. You need at least one.

Wiki pages are your standard wiki content that you will use for most things. Wiki pages have URLs based on their titles, and the WIKI BB-Code links to pages based on their titles.

If you find yourself wanting to have more than 1 page with the same title, but they are different kinds of things (like the color Blue vs the dog Blue), then you have 2 options: use a Prefix to be more specific, or make one of them anonymous. An anonymous page can have a duplicate title but the WIKI BB-Code won't work on it and its URL will use the page ID instead.

A Book is a container that you can use if you have a specific order in mind for reading some wiki pages and want "Next Page" navigation between those pages. A Book will provide a table of contents of all the pages that you add to it.

Categories are basically a tagging system for related wiki pages. You can tag many different pages to a category. Categories are not used for hierarchical organization, permissions, or really anything. Except maybe the user is interested to see "all wiki content tagged with -Games with Multiple-Endings-". In this way you can tag which games have multiple endings without it affecting the way you would prefer to organize those games normally.

Special pages are something different. You can't create new ones. They are pre-installed statistics reports that can help you decide what pages need work.

For a gaming web site, I would probably use Categories for a lot of things like "Multiple Playable Characters", "Multiple Playable Classes", (Individual consoles would probably be categories too), and I would use Areas to setup the general organization that makes sense in most cases -- this might be by Genre, but I can't be sure.

Just remember that pages can have multiple categories, but can only have 1 area. If you can't think of a great way to setup areas because games have lots of cross-over, you might do it by release year. Or if all else fails you can just do the old VaultWiki 3 way: have regular pages in one area, Books in another, Categories in another, and so on.
 
thank you - will definitely be diving into this tonight after work :)

one thing - i did notice this in my ACP:

Code:
Server Error Logs
Delete...
Undefined offset: 5
Today at 4:10 AM - vault/core/model/block/vw.php:71



Code:
Server Error Log
Error Info
ErrorException: Undefined offset: 5 - vault/core/model/block/vw.php:71
Generated By: haqzore, Today at 4:10 AM
Stack Trace
#0 /home/overalvd/public_html/vault/core/model/block/vw.php(71): XenForo_Application::handlePhpError(8, 'Undefined offse...', '/home/overalvd/...', 71, Array)
#1 /home/overalvd/public_html/vault/core/view/ui/stack/vw.php(482): vw_Block_Model->can('share', Array)
#2 /home/overalvd/public_html/vault/core/controller/ui/stack/vw.php(195): vw_UI_Stack_View->sidebar(Object(vw_UI_Stack_Controller), Array)
#3 /home/overalvd/public_html/library/vw/XenForo/ControllerPublic/Wiki.php(68): vw_UI_Stack_Controller->execute()
#4 /home/overalvd/public_html/library/XenForo/FrontController.php(347): vw_XenForo_ControllerPublic_Wiki->actionIndex()
#5 /home/overalvd/public_html/library/XenForo/FrontController.php(134): XenForo_FrontController->dispatch(Object(XenForo_RouteMatch))
#6 /home/overalvd/public_html/index.php(13): XenForo_FrontController->run()
#7 {main}
Request State
array(3) {
  ["url"] => string(64) "http://www.overwatch.zone/index.php?wiki_index/&title=Wiki-Pages"
  ["_GET"] => array(2) {
    ["wiki_index/"] => string(0) ""
    ["title"] => string(10) "Wiki-Pages"
  }
  ["_POST"] => array(0) {
  }
}
 
That can happen for wikis that were upgraded from RC 4. RC 4 didn't do a good job of setting some permissions that are required now. You can go to AdminCP > Wiki > Content > Sidebar Blocks, and click the Modify Permissions button. If you edit and save each one, the offset errors should disappear.
 
That can happen for wikis that were upgraded from RC 4. RC 4 didn't do a good job of setting some permissions that are required now. You can go to AdminCP > Wiki > Content > Sidebar Blocks, and click the Modify Permissions button. If you edit and save each one, the offset errors should disappear.
thank you.

i did not upgrade, i installed fresh at RC5 the first time.

still, i will do the above and see what happens.
 
@pegasus,

i did what you stated & let a day go by. now:



Server Error Logs
Mysqli statement execute error : Duplicate entry '3:1-0-0' for key 'race_condition'Yesterday at 2:34 AM - library/Zend/Db/Statement/Mysqli.php:214
Code:
Error Info
[SIZE=3]Zend_Db_Statement_Mysqli_Exception: Mysqli statement execute error : Duplicate entry '3:1-0-0' for key 'race_condition' - library/Zend/Db/Statement/Mysqli.php:214
Generated By: haqzore, Yesterday at 2:34 AM
Stack Trace
#0 /home/overalvd/public_html/library/Zend/Db/Statement.php(297): Zend_Db_Statement_Mysqli->_execute(Array)
#1 /home/overalvd/public_html/library/Zend/Db/Adapter/Abstract.php(479): Zend_Db_Statement->execute(Array)
#2 /home/overalvd/public_html/library/Zend/Db/Adapter/Abstract.php(574): Zend_Db_Adapter_Abstract->query('INSERT INTO `vw...', Array)
#3 /home/overalvd/public_html/library/XenForo/DataWriter.php(1624): Zend_Db_Adapter_Abstract->insert('vw_permission', Array)
#4 /home/overalvd/public_html/library/XenForo/DataWriter.php(1613): XenForo_DataWriter->_insert()
#5 /home/overalvd/public_html/library/vw/XenForo/DataWriter.php(294): XenForo_DataWriter->_save()
#6 /home/overalvd/public_html/library/XenForo/DataWriter.php(1405): vw_XenForo_DataWriter->_save()
#7 /home/overalvd/public_html/vault/core/controller/dm/xf.php(378): XenForo_DataWriter->save()
#8 /home/overalvd/public_html/vault/core/controller/cp/permission/vw.php(670): vw_DM_Controller_XF->save()
#9 /home/overalvd/public_html/vault/core/view/cp/block/vw.php(537): vw_CP_Permission_Controller->init_permissions_for_group(3)
#10 /home/overalvd/public_html/vault/core/controller/cp/block/vw.php(583): vw_CP_Block_View->permissions(Object(vw_CP_Block_Controller))
#11 /home/overalvd/public_html/vault/core/controller/cp/block/vw.php(113): vw_CP_Block_Controller->permission()
#12 /home/overalvd/public_html/library/vw/XenForo/ControllerAdmin/Wiki.php(115): vw_CP_Block_Controller->execute('permissions', 'post')
#13 /home/overalvd/public_html/library/XenForo/FrontController.php(347): vw_XenForo_ControllerAdmin_Wiki->actionIndex()
#14 /home/overalvd/public_html/library/XenForo/FrontController.php(134): XenForo_FrontController->dispatch(Object(XenForo_RouteMatch))
#15 /home/overalvd/public_html/admin.php(13): XenForo_FrontController->run()
#16 {main}
Request State
array(3) {
  ["url"] => string(68) "http://www.overwatch.zone/admin.php?wiki/&panel=block&do=permissions"
  ["_GET"] => array(3) {
    ["wiki/"] => string(0) ""
    ["panel"] => string(5) "block"
    ["do"] => string(11) "permissions"
  }
  ["_POST"] => array(6) {
    ["panel"] => string(5) "block"
    ["do"] => string(11) "permissions"
    ["_xfToken"] => string(8) "********"
    ["areaid"] => string(1) "3"
    ["submit"] => string(2) "Go"
    ["url"] => string(53) "http://www.overwatch.zone/admin.php?wiki/&panel=block"
  }
}

Undefined offset: 5Tuesday at 4:10 AM - vault/core/model/block/vw.php:71
Code:
Server Error Log

Error Info
ErrorException: Undefined offset: 5 - vault/core/model/block/vw.php:71
Generated By: haqzore, Tuesday at 4:10 AM
Stack Trace
#0 /home/overalvd/public_html/vault/core/model/block/vw.php(71): XenForo_Application::handlePhpError(8, 'Undefined offse...', '/home/overalvd/...', 71, Array)
#1 /home/overalvd/public_html/vault/core/view/ui/stack/vw.php(482): vw_Block_Model->can('share', Array)
#2 /home/overalvd/public_html/vault/core/controller/ui/stack/vw.php(195): vw_UI_Stack_View->sidebar(Object(vw_UI_Stack_Controller), Array)
#3 /home/overalvd/public_html/library/vw/XenForo/ControllerPublic/Wiki.php(68): vw_UI_Stack_Controller->execute()
#4 /home/overalvd/public_html/library/XenForo/FrontController.php(347): vw_XenForo_ControllerPublic_Wiki->actionIndex()
#5 /home/overalvd/public_html/library/XenForo/FrontController.php(134): XenForo_FrontController->dispatch(Object(XenForo_RouteMatch))
#6 /home/overalvd/public_html/index.php(13): XenForo_FrontController->run()
#7 {main}
Request State
array(3) {
  ["url"] => string(64) "http://www.overwatch.zone/index.php?wiki_index/&title=Wiki-Pages"
  ["_GET"] => array(2) {
    ["wiki_index/"] => string(0) ""
    ["title"] => string(10) "Wiki-Pages"
  }
  ["_POST"] => array(0) {
  }
}
 
Last edited:
I can see that the first error prevents admins from changing custom area permissions for sidebar blocks. It should still be possible to change regular usergroup permissions for sidebar blocks. In vault/core/view/cp/block/vw.php, find:
Code:
if (!isset($controller->cache["$groupid"]))
Replace with:
Code:
if (!isset($controller->cache["$groupid"]) AND empty($controller->area['areaid']))
For your original error, there are patch instructions here: https://www.vaultwiki.org/issues/4101/#note22327
That will make the error message stop appearing in the logs.
 
thank you - appreciate the support.

just as an FYI / to try & help with troubleshooting - your post above & linked post for the "original error" mention upgrades from RC4 as the culprit.

the very first time i ever installed VaultWiki was straight into RC5. i've never installed another version, nor upgraded.

not a complaint - just trying to do my part in helping troubleshoot.

thanks again for the support!
 
Yes, there was actually a flaw in the upgrade script from RC 4 -> RC 5 that failed to convert old permission formats from NULL values to 0 values in some cases (there is no difference in evaluation of the permission, so the bug doesn't create a rights-escalation scenario).

There was a separate bug in the direct installer for RC 5 where default permissions were not installed for every usergroup.

The two bugs had the same effect of offset "5" being missing.
 
For the duration of VaultWiki's currently ongoing IndieGogo campaign, we've decided to price-match one of the perks it offers, so that users who aren't interested in supporting or promoting VaultWiki for non-XenForo platforms can still receive the discounted price.

Until the end of the campaign on January 29, 2015, you can use the coupon code "INDGOGO" on our web site to receive 20% off any annual subscription for VaultWiki, including VaultWiki for XenForo.
 
im not sure if this is a style fix, or a wiki fix.
it seems the theme is off in some areas with a dark theme. how do i fix this?

Untitled.webp
 
Back
Top Bottom