Issue: 4.0.17 upgrade to 4.0.18 - vboptimise add-on conflict

Issue Tools
- View Changes

June 2, 2017 10:39 AM

stained

Junior Member

4.0.17 upgrade to 4.0.18 - vboptimise add-on conflict

Just carried out the upgrade which went smoothly. However, clicking on my wiki tab produces an empty page. Not white, just header, footer and nothing where the wiki menu should be. Noticed that showwiki.php doesn't exist. Instead, it has been changed to showwiki.php.old. If I go there I see the "wiki currently disabled message" even though te product is enabled both in wiki settings and in the vb plugin list.

Issue Details

Issue Number 5091

Issue Type Bug

Project VaultWiki 4.x Series

Category Install / Upgrade

Status Fixed

Priority 3 - Loss of Functionality

Affected Version 4.0.18

Fixed Version 4.0.19

Milestone (none)

Software DependencyvBulletin 4.x w/ ckEditor

License TypePaid

Users able to reproduce bug 0

Users unable to reproduce bug 0

Attachments 0

Assigned Users (none)

Tags (none)

June 2, 2017 11:05 AM

stained

Junior Member

Okay. I performed the upgrade a couple of times more and this time the wiki loads but the styling is messed up. Works fine in default VB but not with my style.

Reply
June 2, 2017 11:11 AM

stained

Junior Member

Fixed. All good.

Reply
June 2, 2017 11:13 AM

pegasus

VaultWiki Team

This sounds like the last refresh of your style cache was triggered during the upgrade but before you finished the upgrade. Do you use add-ons like vB Optimise or anything that caches your style templates? You would need to clear any caches like this after an upgrade.

Reply
June 2, 2017 11:20 AM

stained

Junior Member

Yep, you're exactly right It was vboptimise. I flushed the cache and the wiki was back with the correct styling.

Reply
June 2, 2017 1:19 PM

stained

Junior Member

Okay, have been having a play and noticed that I have some missing phrases. Also, the wiki blocks are not showing. I saw them very briefly after the upgrade but since then nothing.

On phrases, I am, for example, unable to promote a thread to a wiki page. This was happening before the upgrade today actually. I don't get a dropdown menu to select a category for the thread so when I save that page just to see what happens, vault attempts to tell me that I'm an idiot but can't find the phrase 'vw_invalid_area'.

I have cleared the vboptimise, vb and browser caches multiple times but no change.

Reply
June 2, 2017 1:41 PM

stained

Junior Member

Getting there Found the reason for no sideblocks: they were turned on generally and permissions were correct but they were off for the areas. Working as you designed them now apart from the index page. Can't seem to get any blocks showing there.

Still having probs with the missing phrase thing and the inability to promote threads to wiki.

Reply
June 2, 2017 2:08 PM

pegasus

VaultWiki Team

There is a setting for index sideblocks, Options > VaultWiki: Content Types > Wiki Index Sidebar Blocks.
For the Convert Threads to Wiki, I can confirm there is a problem with the area drop-down. Looking into it now.

Reply

June 2, 2017 2:12 PM

pegasus

VaultWiki Team

In vault/core/view/ui/imod/vw.php, find:

Code:

				$test = array(
					'itemtypeid' => $pagetypeid
				);

Replace with:

Code:

				$test = array(
					'itemtypeid' => $pagetypeid,
					'typelist' => array($pagetypeid)
				);

June 2, 2017 2:27 PM

stained

Junior Member

Many thanks. The edit worked perfectly. Now, the wiki index sideblocks..

Reply
June 2, 2017 2:30 PM

stained

Junior Member

Ah okay, I see the setting. It is currently set to any block for the index but I don't see the blocks.

Reply
June 4, 2017 10:32 AM

pegasus

VaultWiki Team

Even though the setting says that, try changing it and saving the setting again. I think there are some cases where this setting was not applied to the index correctly, and saving it again can correct it.

Otherwise, I am marking this as Fixed in the next release. Our install process will now detect the presence of vBOptimise and flush its cache automatically.

Reply
June 5, 2017 7:43 AM

stained

Junior Member

Hi,

Yes, changing the setting and then saving did result in the correct display of the sideblocks. Many thanks for your assistance.

Reply

+ Reply

All times are GMT -4. The time now is 4:56 PM.

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: 4.0.17 upgrade to 4.0.18 - vboptimise add-on conflict

Issue Tools