• Register
    • Help

    striker  0 Items
    Currently Supporting
    • Home
    • News
    • Forum
    • Wiki
    • Support
      • Manage Subscriptions
      • FAQ
      • Support For
        • VaultWiki 4.x Series
        • VaultWiki.org Site
    • What's New?
    • Buy Now
    • Manual
    • 
    • Support
    • VaultWiki 4.x Series
    • Bug
    • Install of gamma 6 on our vb 4.2.2 installation

    1. Welcome to VaultWiki.org, home of the wiki add-on for vBulletin and XenForo!

      VaultWiki allows your existing forum users to collaborate on creating and managing a site's content pages. VaultWiki is a fully-featured and fully-supported wiki solution for vBulletin and XenForo.

      The VaultWiki Team encourages you to join our community of forum administrators and check out VaultWiki for yourself.

    Issue: Install of gamma 6 on our vb 4.2.2 installation

    • Issue Tools
      • View Changes
    1. issueid=3824 July 2, 2014 10:50 PM
      tommythejoat tommythejoat is offline
      Regular Member
      Install of gamma 6 on our vb 4.2.2 installation
      Install fails with fatal error - PM and Settings generate a fatal error also.

      When installing gamma 6 on vB 4.4 I encountered a fatal error.
      Code:
      Fatal error: Call to a member function fetch() on a non-object in /home/mb2nawc/public_html/vault/plugins/bbcode.php on line 50
      The running installation is affected by this problem with a fatal error in PM and Member Settings functions of:
      Code:
      Fatal error: Class 'vw_Hard_Core' not found in /home/mb2nawc/public_html/packages/vw/attach/vwcomment.php on line 103
    Issue Details
    Issue Number 3824
    Issue Type Bug
    Project VaultWiki 4.x Series
    Category Install / Upgrade
    Status Fixed
    Priority 2 - Fatal / Database Errors
    Affected Version 4.0.0 Gamma 6
    Fixed Version 4.0.0 Gamma 7
    Milestone VaultWiki 4 Gamma X
    Software DependencyvBulletin 4.x
    License TypePaid
    Users able to reproduce bug 0
    Users unable to reproduce bug 0
    Attachments 0
    Assigned Users (none)
    Tags (none)




    1. July 2, 2014 10:56 PM
      pegasus pegasus is offline
      VaultWiki Team
      According to our instructions "How to Upgrade to VaultWiki 4" which is linked from the site's forum home page and in a warning in VaultWiki 4's upgrade manual, VaultWiki 3 must be disabled in vBulletin's Product Manager when you run the upgrade process or VaultWiki 3 will interfere with the upgrade/install script.

      You can re-enable VaultWiki 3 after installation is complete, but it is not compatible with the install/upgrade script (for the same reason VaultWiki 3 was not compatible with Tapatalk). This was a design flaw in VaultWiki 3 and unfortunately, there is not a way to handle this automatically from VaultWiki 4 without requiring some kind of admin intervention (install a patch on VaultWiki 3 first, etc). The simplest solution is just to have it disabled while VaultWiki 4 installs.

      You will continue to receive fatal errors on some pages even though VaultWiki 4 has not finished installing, because vBulletin automatically executes some files if they exist in certain directories. The fatal error occurs because VaultWiki 4 is not actually installed, but vBulletin found the files and wants to run them.

      Once you disable VaultWiki 3, return to the install script and click "Continue." When the installation is complete, you can re-enable VaultWiki 3.

      I will leave this report open for now, because since refactoring the install script in the middle Betas, it might now be possible to write a work around for this issue within the install script. I'm not sure.
      Reply Reply  
    2. July 2, 2014 11:17 PM
      tommythejoat tommythejoat is offline
      Regular Member
      Oops! ignore this I disabled the wrong version. I did not think about both being there.
      Once you disable VaultWiki 3, return to the install script and click "Continue." When the installation is complete, you can re-enable VaultWiki 3.
      Doing this still displays the error as soon as it tries to build the index.
      Code:
      creating_wiki_index
      
      Fatal error: Call to a member function fetch() on a non-object in /home/mb2nawc/public_html/vault/plugins/bbcode.php on line 50
      Reply Reply  
    3. July 2, 2014 11:17 PM
      pegasus pegasus is offline
      VaultWiki Team
      Fixed in the next build. In vault/core/model/parser/instance/vb3.php, find:
      Code:
      		$hook = parent::get_hook($hook_name, $registry);
      Add after:
      Code:
      		foreach (get_object_vars($this->_default) AS $property => $value)
      		{
      			if (!property_exists($this->model, $property))
      			{
      				$this->model->$property =& $this->_default->$property;
      			}
      		}
      Reply Reply  
    4. July 2, 2014 11:28 PM
      tommythejoat tommythejoat is offline
      Regular Member
      The install succeeded and I re-enabled VW3. I now get the following errors on displaying any page.
      Code:
      Warning: Missing argument 2 for vB_WikiAutoLinker::parse(), called in ..../vault/core/model/plugins/bbcode/vb3.php on line 103 and defined in ..../vault/class/bbcode/autolink.php on line 323
      
      Warning: Missing argument 2 for vB_WikiAutoLinker::parse(), called in ..../vault/core/model/plugins/bbcode/vb3.php on line 103 and defined in ..../vault/class/bbcode/autolink.php on line 323
      
      Warning: Missing argument 2 for vB_WikiAutoLinker::parse(), called in ..../vault/core/model/plugins/bbcode/vb3.php on line 103 and defined in ..../vault/class/bbcode/autolink.php on line 323
      
      Warning: Missing argument 2 for vB_WikiAutoLinker::parse(), called in ..../vault/core/model/plugins/bbcode/vb3.php on line 103 and defined in ..../vault/class/bbcode/autolink.php on line 323
      
      Warning: Missing argument 2 for vB_WikiAutoLinker::parse(), called in ..../vault/core/model/plugins/bbcode/vb3.php on line 103 and defined in ..../vault/class/bbcode/autolink.php on line 323
      
      Warning: Missing argument 2 for vB_WikiAutoLinker::parse(), called in ..../vault/core/model/plugins/bbcode/vb3.php on line 103 and defined in ..../vault/class/bbcode/autolink.php on line 323
      Will your fix above address this?
      Reply Reply  
    5. July 3, 2014 12:08 AM
      pegasus pegasus is offline
      VaultWiki Team
      No, it appears that VaultWiki 3 and VaultWiki 4 cannot be active simultaneously without side effects. If you wish to have both enabled, you should disable autolinks in VaultWiki 4's Wiki Links settings, since VaultWiki 3 is already creating autolinks according to the error you posted above.

      Seeing this, I suspect there would be other conflicts with both versions accessing the same BB-Codes, so another option is to just leave the VaultWiki 4 product disabled until you are ready to perform the migration.

      Neither system is really designed to work together -- the side-by-side installation was only designed to allow better data failover during migrations, and to give early adopters a means to "down-grade" when VaultWiki 4 wasn't yet ready for production or the migration failed. You can use one or the other by disabling/enabling each one.
      Reply Reply  
    + Reply

    Assigned Users
    Loading Please Wait
    Tags
    Loading Please Wait
    • Contact Us
    • License Agreement
    • Privacy
    • Terms
    • Top
    All times are GMT -4. The time now is 9:12 AM.
    This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Learn more… Accept Remind me later
  • striker
    Powered by vBulletin® Version 4.2.5 Beta 2
    Copyright © 2023 vBulletin Solutions Inc. All rights reserved.
    Search Engine Optimisation provided by DragonByte SEO (Pro) - vBulletin Mods & Addons Copyright © 2023 DragonByte Technologies Ltd.
    Copyright © 2008 - 2013 VaultWiki Team, Cracked Egg Studios, LLC.