Issue: Upgraded to VB 4.2

Issue Tools
- View Changes

March 18, 2013 4:46 AM

DirtRider

Junior Member

Upgraded to VB 4.2

Wiki now does not work

I just upgraded my forum to VB 4.2 and the menu item now does not show in my menu bar. If I do go into my WiKi and try and view any entry I get the following error

Configuration error: wiki_index.php was called by another PHP script.
This can cause an infinite loop if the calling script is the same as the DEFAULT_SCRIPT.

In my ACP I am seeing this message as well

VaultWiki 3.0.19 Error

Issue Details

Issue Number 2971

Issue Type Bug

Project VaultWiki 3.x Series

Category Core

Status Not a Bug

Priority 3 - Loss of Functionality

Affected Version 3.0.19

Fixed Version (none)

Milestone (none)

Software DependencyvBulletin 4.x

Users able to reproduce bug 0

Users unable to reproduce bug 0

Attachments 0

Assigned Users (none)

Tags (none)

March 18, 2013 9:55 AM

pegasus

VaultWiki Team

If you upgrade to vB 4.2, you have to upgrade VaultWiki after it.

For the Configuration Error, you should revisit your server configuration (.htaccess, probably) and make sure wiki_index.php is not passed into another script like vbseo.php. Sorry I can't be more specific without knowing the contents of your configuration.

As for the ACP message, where in the ACP are you seeing this? What did you click, or what form is it under?

Reply
March 18, 2013 10:04 AM

DirtRider

Junior Member

How do I upgrade the WiKi maybe this is what I need to do first

Reply
March 18, 2013 10:18 AM

pegasus

VaultWiki Team

Go to /vault/install/index.php

Reply
March 18, 2013 10:26 AM

DirtRider

Junior Member

Well I ran the upgrade.php in the install folder and it ran the upgrade but I still get this error if I try and get into the WiKi from the main menu

Configuration error: wiki_index.php was called by another PHP script.
This can cause an infinite loop if the calling script is the same as the DEFAULT_SCRIPT.

I also still get this error in my plugin and products CP

VaultWiki 3.0.20 Error

Reply
March 18, 2013 10:30 AM

pegasus

VaultWiki Team

If you have not yet setup your Rewrite Configuration, please do so now. See: https://www.vaultwiki.org/manual/vau...-configuration

If you still have problems, please post the contents of your .htaccess file and I will make any needed corrections.

Reply

March 18, 2013 10:35 AM

DirtRider

Junior Member

The thing is the WiKi always worked before I did the forum upgrade. Here is my .htaccess file

Code:

RewriteEngine On
Order allow,deny
#Baidu
deny from 180.76
deny from 119.63
deny from 123.125
deny from 220.181
#China
deny from 27.153.234
deny from 124.115.0
deny from 112.111.173
deny from 120.32.91
deny from 60.191.221
deny from 111.34.171
deny from 116.237.154
deny from 61.191.188
deny from 218.66.250
deny from 59.58.174
deny from 220.181.89
deny from 120.85.140
deny from 58.22.21
deny from 219.234.82
deny from 110.82.131
deny from 159.226.17
deny from 113.106.94
deny from 112.101.64
deny from 60.169.75
deny from 222.186.128
deny from 117.26.202
deny from 120.39.74
deny from 221.6.15
deny from 106.3.102
deny from 118.249.162
deny from 119.123.220
deny from 59.57.221
deny from 183.60.213
deny from 221.6.15
Deny from 121.61.118
deny from 61.160.247
deny from 110.85.4
#Russia
deny from 94.127.144
deny from 91.201.64
deny from 37.79.152
deny from 188.143.232
deny from 95.24.83
deny from 79.120.86
deny from 94.188.46
deny from 79.120.86
deny from 37.144.124
deny from 219.136.241
deny from 2.82.86
deny from 92.244.244
deny from 106.3.102
#Hong Kong
deny from 61.238.124
#Japan
deny from 150.70.64
deny from 122.133.142
deny from 150.70.172
deny from 175.177.226
deny from 150.70.75
#Other
deny from 112.216.70
allow from all 
#RULES for SEO translation links without any SEO engine (on raw vBulletin links)
#If you are using vB 'Mod Rewrite Friendly URLs' then put those rules JUST BEFORE vB rules
RewriteRule ^/?(af|sq|ar|hy|az|eu|be|bg|ca|zh-CN|hr|cs|da|nl|en|et|tl|fi|fr|gl|ka|de|el|ht|iw|hi|hu|is|id|ga|it|ja|ko|lv|lt|mk|ms|mt|no|fa|pl|pt|ro|ru|sr|sk|sl|es|sw|sv|zh-TW|th|tr|uk|ur|vi|cy|yi)/archive/index.php/(.*)?$ archive/index.php?/$2&language=$1 [L,QSA]
RewriteRule ^/?(af|sq|ar|hy|az|eu|be|bg|ca|zh-CN|hr|cs|da|nl|en|et|tl|fi|fr|gl|ka|de|el|ht|iw|hi|hu|is|id|ga|it|ja|ko|lv|lt|mk|ms|mt|no|fa|pl|pt|ro|ru|sr|sk|sl|es|sw|sv|zh-TW|th|tr|uk|ur|vi|cy|yi)/$ index.php?language=$1 [L,QSA]
RewriteRule ^/?(af|sq|ar|hy|az|eu|be|bg|ca|zh-CN|hr|cs|da|nl|en|et|tl|fi|fr|gl|ka|de|el|ht|iw|hi|hu|is|id|ga|it|ja|ko|lv|lt|mk|ms|mt|no|fa|pl|pt|ro|ru|sr|sk|sl|es|sw|sv|zh-TW|th|tr|uk|ur|vi|cy|yi)/(.*)?$ $2?language=$1 [QSA]

#--------------------------------------------------------------------------
#RULES for SEO translation links with vBSEO (have to be included before all rules to vbseo.php)
#RewriteRule ^/?(af|sq|ar|hy|az|eu|be|bg|ca|zh-CN|hr|cs|da|nl|en|et|tl|fi|fr|gl|ka|de|el|ht|iw|hi|hu|is|id|ga|it|ja|ko|lv|lt|mk|ms|mt|no|fa|pl|pt|ro|ru|sr|sk|sl|es|sw|sv|zh-TW|th|tr|uk|ur|vi|cy|yi)/$ vbenterprisetranslator_seo.php?vbet_lang=$1&redirected=/ [L,QSA]
#RewriteRule ^/?(af|sq|ar|hy|az|eu|be|bg|ca|zh-CN|hr|cs|da|nl|en|et|tl|fi|fr|gl|ka|de|el|ht|iw|hi|hu|is|id|ga|it|ja|ko|lv|lt|mk|ms|mt|no|fa|pl|pt|ro|ru|sr|sk|sl|es|sw|sv|zh-TW|th|tr|uk|ur|vi|cy|yi)/(.*)?$ vbenterprisetranslator_seo.php?vbet_lang=$1&redirected=/$2 [L,QSA]

#RewriteCond %{REQUEST_URI} !(admincp/|modcp/|vbseo_sitemap/|cron)
#RewriteRule ^((archive/)?(.*\.php(/.*)?))$ vbenterprisetranslator_seo.php [L,QSA]

#RewriteCond %{REQUEST_FILENAME} !-f
#RewriteCond %{REQUEST_FILENAME} !-d
#RewriteCond %{REQUEST_FILENAME} !^(admincp|modcp|clientscript|cpstyles|images)/
#RewriteRule $ vbenterprisetranslator_seo.php [L,QSA]
#---------------------------------------------------------------------------

#RULES for pages outside forum directory handled by vBulletin

#Those rules have to be in domain main folder
#RewriteRule ^/?(af|sq|ar|hy|az|eu|be|bg|ca|zh-CN|hr|cs|da|nl|en|et|tl|fi|fr|gl|ka|de|el|ht|iw|hi|hu|is|id|ga|it|ja|ko|lv|lt|mk|ms|mt|no|fa|pl|pt|ro|ru|sr|sk|sl|es|sw|sv|zh-TW|th|tr|uk|ur|vi|cy|yi)/$ index.php?language=$1&vbet_outside=true [L,QSA]
#RewriteRule ^/?(af|sq|ar|hy|az|eu|be|bg|ca|zh-CN|hr|cs|da|nl|en|et|tl|fi|fr|gl|ka|de|el|ht|iw|hi|hu|is|id|ga|it|ja|ko|lv|lt|mk|ms|mt|no|fa|pl|pt|ro|ru|sr|sk|sl|es|sw|sv|zh-TW|th|tr|uk|ur|vi|cy|yi)/(.*)?$ $2?language=$1&vbet_outside=true [L,QSA]

#This rule must be in each directory which have to be supported (without forum directory itself)
#RewriteCond %{QUERY_STRING} !vbet_outside=true
#RewriteRule ^(.*)$ $1?vbet_outside=true [L,QSA]

March 18, 2013 10:46 AM

pegasus

VaultWiki Team

Find this:

Code:

RewriteRule ^/?(af|sq|ar|hy|az|eu|be|bg|ca|zh-CN|hr|cs|da|nl|en|et|tl|fi|fr|gl|ka|de|el|ht|iw|hi|hu|is|id|ga|it|ja|ko|lv|lt|mk|ms|mt|no|fa|pl|pt|ro|ru|sr|sk|sl|es|sw|sv|zh-TW|th|tr|uk|ur|vi|cy|yi)/(.*)?$ $2?language=$1 [QSA]

Before it, put:

Code:

RewriteCond %{REQUEST_FILENAME} !^(?:vault/|wiki_)

Unless you have another .htaccess file in another directory, this is the only one I see that might be catching wiki_index.php

March 18, 2013 11:47 AM

DirtRider

Junior Member

Where must I look for this code?

Reply
March 18, 2013 6:30 PM

pegasus

VaultWiki Team

It's part of the .htaccess file you quoted me. That's the part I would try changing first.

Reply
March 18, 2013 8:43 PM

pegasus

VaultWiki Team

If this is an upgrade, you may be experiencing this issue: https://www.vaultwiki.org/issues/2976/

Reply

March 18, 2013 11:00 PM

DirtRider

Junior Member

Ok I tried both those fixes and still get this error

Code:

Warning: require_once(./vault/config.php) [function.require-once]: failed to open stream: No such file or directory in /home/davem/public_html/wiki_index.php on line 65

Fatal error: require_once() [function.require]: Failed opening required './vault/config.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/davem/public_html/wiki_index.php on line 65

March 18, 2013 11:13 PM

pegasus

VaultWiki Team

Sounds like you did not setup the config file... Not sure how you ran the upgrade script without the config file...

Did you follow this blog entry while upgrading? https://www.vaultwiki.org/blogs/55/
Please note any steps you may have missed, as it will help with diagnosis.

IMPORTANT: If you did not run the upgrade script yet, you may want to wait for Alpha 2 in a couple of days. It will resolve a number of showstopper and data loss issues you may not be prepared to deal with. In the mean time, you can re-upload 3.0.20 to your site to continue using your wiki.

Reply
March 19, 2013 12:23 AM

DirtRider

Junior Member

Ok I am going through these steps but am not sure about this one

In AdminCP > Plugins & Products > Product Manager, disable ALL products that have VaultWiki as a dependency. Note: Products and scripts that depend on VaultWiki will need to be completely rewritten for VaultWiki 4 before they can be reactivated.

Would it not be easier if I just let you have a look at this issue for me

Reply
March 19, 2013 11:30 AM

pegasus

VaultWiki Team

I have added an Install Service to your Members area. Please fill it out and I will have a look.

Reply
March 19, 2013 11:55 AM

DirtRider

Junior Member

Ok let me look at that, is this going to cost me extra then?

Reply

+ Reply

All times are GMT -4. The time now is 2:54 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: Upgraded to VB 4.2

Issue Tools