Issue: Am I missing something when upgrading on XF 2.1?

Issue Tools
- View Changes

June 17, 2019 5:56 PM

medic917

Junior Member

Am I missing something when upgrading on XF 2.1?

I'm trying to update to v4.1.0 Beta 1 Build 002 from Build 001.
I disabled addon per VW's manual and then uploaded contents of Build 002 (I downloaded build 2 with only new files). Then I re-enabled the addon.

The next step according to VW's manual is that I should look for the maintenance section in my XF admin panel under the Wiki section. I don't see it on my admin panel anywhere.

However, on version check, I see the version has updated, but not sure if it was a successful update as I only uploaded the new files...

Issue Details

Issue Number 5783

Issue Type Task

Project VaultWiki 4.x Series

Category Unknown

Status Closed (Merged)

Priority 3 - Loss of Functionality

Target Version Unknown

Resolved Version (none)

Milestone (none)

Software DependencyAny

License TypePaid

Votes to perform 0

Votes not to perform 0

Attachments 0

Assigned Users (none)

Tags xenforo

June 17, 2019 6:00 PM

medic917

Junior Member

Nvm, I am missing a step since on certain pages of the admin panel I'm being asked to upgrade when it tells me I'm on the latest 002 build version.

Reply
June 18, 2019 11:01 AM

pegasus

VaultWiki Team

Apologies, it looks like we had only updated the manual with install instructions for XF 2. The upgrade instructions at time of posting are only relevant for XF 1. I will make sure they are updated today.

For XF 2, all upgrades are handled through XenForo's add-on manager. In AdminCP > Add-ons > Add-ons, VaultWiki should appear under a section like "Upgradeable Addons" with an Upgrade button.

You do not need to run the upgrade script if you update to a new build of the same version you had before... unless you recently upgraded XenForo from 2.0.x to 2.1.x and have not also upgraded VaultWiki yet.

VaultWiki shows messages that an upgrade is pending in the following situations:
- You uploaded a new version number (more than a new build) and didn't run the Upgrade script yet.
- You upgraded from XenForo 2.0.x to 2.1.x, and didn't upload the 2.1.x version yet. After uploading the 2.1.x version, VaultWiki should appear under "Upgradeable Addons" like a normal version upgrade.

Reply
June 18, 2019 7:49 PM

medic917

Junior Member

Hmmm, for some reason I'm not getting the Upgradeable addons section anywhere in the addons page.

This is all I'm getting:

As mentioned in my first post, I uploaded "only" the new files of the new build. Whereas before I had the XF 2.1 build 001 version running.

Maybe because I didn't upload the addon-vaultwiki_stub-INSTALL.xml file? I only uploaded the contents in the upload folder.

Reply
June 19, 2019 10:09 AM

pegasus

VaultWiki Team

If you already had XF 2.1 installed and you were running build 001 on it, and now you uploaded build 002, then you don't need to do anything else. The stub XML is not used if you already use XF 2.1.

Where is it telling you that you have an upgrade pending?

Reply
June 19, 2019 3:41 PM

medic917

Junior Member

Weird, it was at the area manager saying I had build 002 version and contradictingly saying I have to update to the same build. But now it doesn't.

I guess it was due to old cache? Anyways, there's still a problem of bbcodes not rendering that I noticed after the update.

My settings however are correct and haven't changed. It was working fine before I uploaded build 002 files.

So I just needed to upload the new build 002 files since I had XF 2.1 already installed and build 001 running on it? That's what I did and now I noticed the bbcode issue.

Reply

June 19, 2019 3:44 PM

medic917

Junior Member

I am getting these errors showing up now.

Code:

ErrorException: [E_NOTICE] Undefined index: prefix src/addons/vw/vw/_core/view/ui/activity/vw.php:195
Generated by: User Jun 19, 2019 at 8:38 PM
Stack trace
#0 src/addons/vw/vw/_core/view/ui/activity/vw.php(195): XF::handlePhpError(8, '[E_NOTICE] Unde...', '/home/admin/web...', 195, Array)
#1 src/addons/vw/vw/_core/view/ui/activity/page/vw.php(21): vw_UI_Activity_View->normalize_and_prefix_title(Array)
#2 src/addons/vw/vw/_core/view/ui/activity/vw.php(122): vw_UI_Activity_Page_View->feedbit(Array, Array)
#3 src/addons/vw/vw/_core/controller/ui/activity/vw.php(54): vw_UI_Activity_View->feedbits(Object(vw_UI_Activity_Controller), 50)
#4 src/addons/vw/vw/_core/view/ui/ajax/activity/vw.php(39): vw_UI_Activity_Controller->get(Array, 1560973101, 0)
#5 src/addons/vw/vw/_core/view/reply/view/vw.php(48): vw_UI_AJAX_Activity_View->results(Array)
#6 src/addons/vw/vw/_core/view/reply/base/vw.php(134): vw_Reply_View_View->render_type('xml')
#7 src/addons/vw/vw/XF/Mvc/View.php(74): vw_Reply_base_View->render('xml')
#8 src/XF/Mvc/Renderer/AbstractRenderer.php(91): vw\vw\XF\Mvc\View->renderXml()
#9 src/XF/Mvc/Renderer/Xml.php(74): XF\Mvc\Renderer\AbstractRenderer->renderViewObject('vw\\vw:Wiki', 'public:vw_gener...', Array)
#10 src/XF/Mvc/Dispatcher.php(418): XF\Mvc\Renderer\Xml->renderView('vw\\vw:Wiki', 'public:vw_gener...', Array)
#11 src/XF/Mvc/Dispatcher.php(400): XF\Mvc\Dispatcher->renderView(Object(XF\Mvc\Renderer\Xml), Object(XF\Mvc\Reply\View))
#12 src/XF/Mvc/Dispatcher.php(360): XF\Mvc\Dispatcher->renderReply(Object(XF\Mvc\Renderer\Xml), Object(XF\Mvc\Reply\View))
#13 src/XF/Mvc/Dispatcher.php(53): XF\Mvc\Dispatcher->render(Object(XF\Mvc\Reply\View), 'xml')
#14 src/XF/App.php(2177): XF\Mvc\Dispatcher->run()
#15 src/XF.php(390): XF\App->run()
#16 index.php(20): XF::runApp('XF\\Pub\\App')
#17 {main}
Request state
array(4) {
  ["url"] => string(31) "/index.php?content-ajax/&c=feed"
  ["referrer"] => string(32) "http://*snip*/content/Books"
  ["_GET"] => array(2) {
    ["content-ajax/"] => string(0) ""
    ["c"] => string(4) "feed"
  }
  ["_POST"] => array(7) {
    ["ajax"] => string(1) "1"
    ["pageid"] => string(1) "0"
    ["uppertime"] => string(3) "NaN"
    ["lowertime"] => string(1) "0"
    ["filter"] => string(18) "1,5,10,11,22,25,26"
    ["_xfToken"] => string(8) "********"
    ["c"] => string(4) "feed"
  }
}

June 20, 2019 11:14 AM

pegasus

VaultWiki Team

If you are encountering this BB-Code issue, please edit any BB-Code in the AdminCP and hit the Save button.

Reply
June 20, 2019 5:36 PM

medic917

Junior Member

please edit any BB-Code in the AdminCP

You mean enable/disable bbcode parsing in the area manager? I tried this and it doesn't fix it.

Can you verify my notion on upgrading?

So I just needed to upload the new build 002 files since I had XF 2.1 already installed and build 001 running on it?

Reply
June 24, 2019 10:38 AM

pegasus

VaultWiki Team

Not in the Area Manager. In AdminCP > Content > BB code > Custom BB codes, edit a BB-Code and Save it.
Your notion on upgrading builds is correct.

Reply
June 24, 2019 5:23 PM

medic917

Junior Member

Ah, that fixed it. I wonder what caused that hiccup in the first place? Thanks for the details!

Reply

+ Reply

All times are GMT -4. The time now is 6:11 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

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

Issue: Am I missing something when upgrading on XF 2.1?

Issue Tools