VaultWiki [Paid] 4.1.7 Patch Level 1
- Thread starter pegasus
- Start date
Carla Birch
Well-known member
It's not live sorry.Can I see your setup?
Any sites that have a really active vaultwiki?
The Dark Wizard
Well-known member
Carla Birch
Well-known member
Unable to uninstall version 4 RC2
In uninstall/xf.php on line 17 it reads: require_once(vw_Hard_Core::get_dir() . '/controller/install/uninstall/vw.php'); i edited that to require_once(vw_Hard_Core::get_dir() . '/controller/uninstall/vw.php');
It then gives the error: Fatal error: Class 'vw_UnInstall_Insert_Controller' not found in /var/www/vhosts/****/httpdocs/vault/core/controller/uninstall/insert/xf.php on line 20
PHP:
Warning: Uncaught exception 'ErrorException' with message 'require_once(/var/www/vhosts/****/httpdocs/vault/core/controller/install/uninstall/vw.php): failed to open stream: No such file or directory' in /var/www/vhosts/****/httpdocs/vault/core/controller/uninstall/xf.php:17 Stack trace: #0 /var/www/vhosts/****/httpdocs/vault/core/controller/uninstall/xf.php(17): XenForo_Application::handlePhpError(2, 'require_once(/v...', '/var/www/vhosts...', 17, Array) #1 /var/www/vhosts/****/httpdocs/vault/core/controller/uninstall/xf.php(17): require_once() #2 /var/www/vhosts/****/httpdocs/vault/core/model/vw.php(357): require_once('/var/www/vhosts...') #3 /var/www/vhosts/****/httpdocs/vault/core/model/vw.php(328): vw_Hard_Core::locate_children('UnInstall_Contr...', '/var/www/vhosts...', 'XF') #4 /var/www/vhosts/****/httpdocs/vault/core/model/vw.php(183): vw_Hard_Core::locate_class('Controller', 'UnInstall_Contr...', '/var/www/vhosts...', '') #5 /var/www/vhosts in /var/www/vhosts/****/httpdocs/vault/core/controller/uninstall/xf.php on line 17 Fatal error: main(): Failed opening required '/var/www/vhosts/****/httpdocs/vault/core/controller/install/uninstall/vw.php' (include_path='/var/www/vhosts/****/httpdocs/library:.') in /var/www/vhosts/****/httpdocs/vault/core/controller/uninstall/xf.php on line 17In uninstall/xf.php on line 17 it reads: require_once(vw_Hard_Core::get_dir() . '/controller/install/uninstall/vw.php'); i edited that to require_once(vw_Hard_Core::get_dir() . '/controller/uninstall/vw.php');
It then gives the error: Fatal error: Class 'vw_UnInstall_Insert_Controller' not found in /var/www/vhosts/****/httpdocs/vault/core/controller/uninstall/insert/xf.php on line 20
pegasus
Well-known member
Our Demo site https://www.vaultwiki.org/xf/ is currently running 1.4 beta.
Carla Birch
Well-known member
It has the following:
PHP:
class vw_Install_DB_Insert_Controller
{
protected $_insertions = array();
public function get()
{
$this->_insertions = ksort($this->_insertions);
return $this->_insertions;
}
}pegasus
Well-known member
Yes, just change the Wiki Base URL setting so that it points to your sub-domain. Make sure the sub-domain is parked on your XenForo forum directory.
@Carla Birch I am generating RC 2 build 002 now. It should resolve most, if not all, of the issues you were having.
Carla Birch
Well-known member
Many thanks, i'll download and test it out when its ready
Carla Birch
Well-known member
Code:
Fatal error: Class 'vw_UnInstall_Insert_Controller' not found in /var/www/vhosts/****/httpdocs/vault/core/controller/uninstall/insert/xf.php on line 20When trying to uninstall now.
Carla Birch
Well-known member
@pegasus Trying to upload an attachment gives the following error.
So it seems, like part the table was not installed.
PHP:
Database Error: UPDATE `vw_attachmentedit` SET `ip_id` = 157674 WHERE attacheditid = 2 Mysqli prepare error: Unknown column 'ip_id' in 'field list'
vw_DB_Controller_XF->throw_error() in /var/www/vhosts/****/httpdocs/vault/core/controller/db/xf.php at line 122
vw_DB_Controller_XF->query_write() in /var/www/vhosts/****/httpdocs/vault/core/model/db/mysql/vw.php at line 893
vw_DB_MySQL_Model->shutdown_or_run() in /var/www/vhosts/****/httpdocs/vault/core/model/db/mysql/vw.php at line 662
vw_DB_MySQL_Model->update() in vw/XenForo/DataWriter.php at line 401
vw_XenForo_DataWriter->log_ip() in /var/www/vhosts/****/httpdocs/vault/core/controller/dm/attach/edit/vw.php at line 196
vw_DM_Attach_Edit_Controller->post_save_each() in vw/XenForo/DataWriter.php at line 419
vw_XenForo_DataWriter->_postSave() in XenForo/DataWriter.php at line 1409
XenForo_DataWriter->save() in /var/www/vhosts/****/httpdocs/vault/core/controller/dm/xf.php at line 378
vw_DM_Controller_XF->save() in /var/www/vhosts/****/httpdocs/vault/core/controller/dm/attach/vw.php at line 233
vw_DM_Attach_Controller->save() in /var/www/vhosts/****/httpdocs/vault/core/controller/dm/attach/xf.php at line 38
vw_DM_Attach_Controller_XF->save() in /var/www/vhosts/****/httpdocs/vault/core/controller/dm/xf.php at line 378
vw_DM_Controller_XF->save() in /var/www/vhosts/****/httpdocs/vault/core/controller/ui/edit/attach/vw.php at line 123
vw_UI_Edit_Attach_Controller->save_more() in /var/www/vhosts/****/httpdocs/vault/core/controller/ui/edit/vw.php at line 204
vw_UI_Edit_Controller->save() in /var/www/vhosts/****/httpdocs/vault/core/controller/ui/create/vw.php at line 229
vw_UI_Create_Controller->publish() in /var/www/vhosts/****/httpdocs/vault/core/controller/ui/area/vw.php at line 126
vw_UI_Area_Controller->publish() in /var/www/vhosts/****/httpdocs/vault/core/controller/ui/area/vw.php at line 37
vw_UI_Area_Controller->execute() in /var/www/vhosts/****/httpdocs/vault/core/controller/ui/stack/vw.php at line 168
vw_UI_Stack_Controller->execute() in vw/XenForo/ControllerPublic/Wiki.php at line 68
vw_XenForo_ControllerPublic_Wiki->actionIndex() in XenForo/FrontController.php at line 347
XenForo_FrontController->dispatch() in XenForo/FrontController.php at line 134
XenForo_FrontController->run() in /var/www/vhosts/****/httpdocs/index.php at line 13So it seems, like part the table was not installed.
Mouth
Well-known member
Can you promote/copy an existing forum thread to a wiki entry? If so, will it keep the existing forum discussion 'attached' to the wiki entry discussion?
Can I link existing forum topics and existing wiki entries discussion together?
Can a new wiki entry automatically create a discussion topic in the user selected forum, or is the discussion external to the forums and within the wiki?
Can I link existing forum topics and existing wiki entries discussion together?
Can a new wiki entry automatically create a discussion topic in the user selected forum, or is the discussion external to the forums and within the wiki?
pegasus
Well-known member
This feature is planned, but is not yet part of VaultWiki: https://www.vaultwiki.org/issues/3439/
The wiki discussion is not a topic in a selected forum. It is a separate content type that is attached to the wiki.
Mouth
Well-known member
It's planned to make the forum discussion integrated with the wiki entry, or you will be copying/duplicating the forum discussion into the wiki discussion content item?
I don't understand why the wiki duplicates discussion content type, when XF already has discussion inherit?
I just cannot see "Seamlessly Integrates With Your Community" when discussion on wiki content is separate to where community discussion occurs.
pegasus
Well-known member
It's planned to have a moderation tool like Move Threads / Copy Threads like you already have for other threads, that can move a thread from a forum to a wiki discussion or back again.
Wiki pages are not threads. So it doesn't make sense to have the comments as threads. As far as data management goes, it's more logical and performant to save wiki comments separately, based on difference in behaviors, avoiding conflicts, and other reasons. Instead the comments are replies to the article, or replies to a discussion on the article. Another example you might be familiar with: in most blogs, comments appear right below the blog. You don't have to create a thread in another forum that links back to the blog.
You don't want wiki discussions to be in exactly the same place as community discussions. That defeats a lot of the benefit of having a wiki, which is to create a knowledge base that is easy to distinguish for regular community discussion. You want discussions about wiki content to be right under the appropriate wiki page. In really early versions of VaultWiki (version 1), it worked the way you are talking about and it was a confusing user experience, because the discussion was a different page and it wasn't even in the wiki.
Regardless if XenForo also has something it calls a "discussion", and VaultWiki calls something else a "discussion", they are not exactly the same thing, and the important thing to keep in mind is that content is not duplicated. It just happens that the word "discussion" seems to be the best word to describe them.
"Seamlessly Integrates With Your Community" is talking about the user experience. Comments look and feel like regular replies -- you can quote them, search them, and post them like other forum posts. There's lots of other examples of integration with your community, but really you can read about them everywhere on the Feature List; I don't need to make another duplicate post of it.
And of course there will technically be seams in the backend code -- if there were no seams at all, it would just be XenForo with no addons.
Mouth
Well-known member
We'll agree to disagree.
I want my wiki knowledge-base to be easily accessible and searchable, without a user having to wade through discussion posts/replies to find authoritative/accurate content. Approved users who are verified/knowledgeable are allowed to create and edit wiki entries. The wiki entry can always be 'trusted' by the reader with a higher degree of competency/accuracy. General discussion on/about that wiki entry can be accessible directly from the wiki entry/page, but using XF's already excellent and core discussion functionality.
For example, Xenforo's Resource Manager ( https://xenforo.com/community/resources/vaultwiki.1959/ ) - the overview tab is the content (the wiki entry) and the discussion tab is a direct link to the discussion forum topic about this resource(wiki) content. That to me is making the valuable and accurate/authoritative content easily available, with discussion being seamlessly integrated and providing a great user experience. In a wiki scenario, the highly valuable and accurate/authoritative content (eg. overview tab on Resource Manager) is editable/up-dateable by approved editors and wiki content managers.
pegasus
Well-known member
Well, it sounds like you are arguing about a point that doesn't make any difference to the end user. Perhaps a third-party add-on developer would care, but I feel like a developer would easily figure out how things are saved in the wiki once they look at the database. Whether a comment is stored in a forum or in a separate container, the end user never sees that -- even in your explanation.
So why add the extra step of having to choose a forum to save things in? We used to save things in forums in VaultWiki 3 (vBulletin only) and almost every admin found that confusing and hated it. They didn't want to make new forums when they installed their wiki -- they just wanted to start making wiki things. Some wondered quite vocally why they had bothered buying a wiki if the containers were just "fancy looking forums and threads". In VaultWiki 4, we removed that step, and you don't need forums at all anymore. Your containers are obviously wiki containers, easy to identify and purpose-built (the information needed for the wiki containers is not fetched into memory to slow things down in regular forums).
Despite however you feel about how a comment is treated in the database, we used years of research and customer opinions regarding usability and comprehension of concepts to make our decisions about how things are stored in VaultWiki 4. After all, VaultWiki is 6 years old and heavily shaped by customer feedback. The result in the 4.x series is more organized, more identifiable, and better performing data than when everything was all mixed together.
So why add the extra step of having to choose a forum to save things in? We used to save things in forums in VaultWiki 3 (vBulletin only) and almost every admin found that confusing and hated it. They didn't want to make new forums when they installed their wiki -- they just wanted to start making wiki things. Some wondered quite vocally why they had bothered buying a wiki if the containers were just "fancy looking forums and threads". In VaultWiki 4, we removed that step, and you don't need forums at all anymore. Your containers are obviously wiki containers, easy to identify and purpose-built (the information needed for the wiki containers is not fetched into memory to slow things down in regular forums).
Despite however you feel about how a comment is treated in the database, we used years of research and customer opinions regarding usability and comprehension of concepts to make our decisions about how things are stored in VaultWiki 4. After all, VaultWiki is 6 years old and heavily shaped by customer feedback. The result in the 4.x series is more organized, more identifiable, and better performing data than when everything was all mixed together.
Mouth
Well-known member
And there's the rub - XenForo is a discussion community. Forums are at the core of the community. If we only wanted a wiki, then we wouldn't have XenForo. But we have XenForo, and an integrated and seemless add-on doesn't separate discussion into two different silos - discussion and wiki. It's one, it's together, it's integrated.
My $0.02c - good luck with VaultWiki XF addon.
pegasus
Well-known member
With your last comment, I feel like you did not actually read anything else from the post above, my responses before it, or take them in. Thank you for trolling; you are now on Ignore.
Since you brought it up, other users might be interested to know that XF Resource Manager is an exception to a rule, it seems. You seem to have missed that XenForo has at least 3 separate venues for discussion already:
- Forum threads (or Discussions as you call them)
- Conversations
- Profile posts
Neither Conversations nor Profile Posts require that you select a forum to save them in. They are obviously separated into different silos. Yet you still feel like they are part of the same community.
You should make the same moot arguments about XenForo itself. I invite you to do that.
Last edited:
