Issue: VaultArticle causing vbulletin search issue

Issue Tools
- View Changes

August 11, 2010 3:53 PM

gv1.3

New Member

VaultArticle causing vbulletin search issue

vaultwiki install has changed a vbulletin contenttype

Hi,

I upgraded to the latest version of vaultwiki and am running vbulletin 4.0.5.

Since upgrading if I click on Advanced Search link on my forum I get a FATAL ERROR. You can try it out here - http://www.toyotagtturbo.com/forums/search.php

I get the same error if I search for a term under 4 letters in length.

I opened a ticket with vbulletin support and they checked in to it for me and told me the following:

"Fatal error: Trying to get contenttype class id from invalid contenttype '15' on line 533 in [path]/vb/types.php in [path]/vb/vb.php on line 287

I checked the database and that contenttype is not from the default vB. It's from an add-on: VaultArticle

My guess is that this is from your VaultWiki add-on. The options are to either removed that add-on, including all the changes it made to the database, or contacting the author for help fixing this."

Could you check in to this for me and suggest some possible solutions please as my users are now unable to perform an advanced search.

Thank you,

Dylan

Issue Details

Issue Number 1912

Issue Type Bug

Project VaultWiki 3.x Series

Category Searching

Status Not a Bug

Priority 2 - Fatal / Database Errors

Affected Version 3.0.2

Fixed Version (none)

Milestone VaultWiki 3.0.5

Software DependencyAny

Users able to reproduce bug 1

Users unable to reproduce bug 0

Attachments 0

Assigned Users (none)

Tags vBulletin Maintenance

August 11, 2010 4:50 PM

pegasus

VaultWiki Team

In your AdminCP, go to vBulletin CMS, and click "Clear CMS Cache". This happens when you disable/re-enable VaultWiki (or any product with content-types) using the [APM] Advanced Product Manager modification, but content types were purged while VaultWiki was disabled (like if it was disabled during a vBulletin upgrade). That modification (APM) doesn't have support for vB_Cache, so the content types are not rebuilt when you re-enable a product.

I reported this issue to the mod creator months ago, but my guess is they still haven't fixed it. The only workaround for now is to make sure you do all your enabling/disabling through vB's default Product Manager.

Reply
August 12, 2010 12:20 PM

gv1.3

New Member

Hi mate thanks for the reply. I dont have any advanced product manager modification installed. I have very few mods installed on my vB.

I also do not have the Vbulletin CMS installed so dont appear to have an option to "clear cms cache"

Any other ideas on this one?

Thanks

Reply
August 12, 2010 1:07 PM
pegasus

VaultWiki Team
I was only able to reproduce this issue by using the mod I mentioned above. It seems to be working fine in default vB (suite).

Do you just not have the CMS installed, or do you only own a forum license (i.e. not the full suite)? If you only have the forum license, I would be interested to see whether this is a vBulletin bug in only that branch. It seems there is no longer an option in the vB Members Area to download JUST the forum. So you would need to email a copy of admincp/plugin.php (remove your license info) to:

Code:

support@vaultwiki.org

Because of a design issue in vBulletin, it may not be possible to clear the type-cache manually when the CMS is not installed. However, before complaining to them, you can try Settings > Options > Server Settings and Optimization Options > Disable Content Caching = Yes.
Reply
August 12, 2010 2:37 PM

gv1.3

New Member

Thanks for the reply.
I only own a forum license, I use Joomla for CMS (different database)

I sent the plugin.php file to the address you supplied.

I disabled content caching as you suggested above and everything works fine! However when I re-enable it the problem is back.

Thanks for your help on this one I appreciate it.

Reply
August 13, 2010 12:33 AM

pegasus

VaultWiki Team

It looks like the code in the forum-only version is correct. I would try disabling, then re-enabling VaultWiki. This should clear the type-cache. If this works, I don't really know what made it wrong to begin with. It's possible the cache was corrupted before, or the cache update was delayed for some reason.

I have made some changes to how VaultWiki calls the cache-rebuild for the next release, in the interest of making the code simpler.

Reply
August 13, 2010 1:00 PM

gv1.3

New Member

Hi,

I disabled and enabled vaultwiki and everything is working fine now.

Thanks for your assistance with this, I really appreciate it.

Regards,

Dylan

Reply

+ Reply

All times are GMT -4. The time now is 2:20 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: VaultArticle causing vbulletin search issue

Issue Tools