Issue: What to do after upgrading to VW 4?

Issue Tools
- View Changes

December 15, 2014 11:00 AM

beernuts

Junior Member

What to do after upgrading to VW 4?

Some PHP Versions Can't Parse //site.com URLs

We have just upgraded to VW 4 and everything appeared to go smoothly. However, there are a couple of issues:

1. We run our Wiki on a subdomain - http://wiki.{site}.com/index.php. However, when I try to set Wiki Base URL
to wiki.{site}.com and Filename of the Wiki PHP file to index, the control panel reverts that 'index' value to 'wiki_index'. So now the navigation tab is sending users to http://wiki.{site}.com/wiki_index.php, which isn't correct.

2. VW 3 is still installed in vBulletin products. Is it safe to uninstall VW3?

3. Do we need to update any of the files on the wiki subdomain? I didn't see anything about this setup in the manual.

Issue Details

Issue Number 4104

Issue Type Bug

Project VaultWiki 4.x Series

Category General

Status Fixed

Priority 3 - Loss of Functionality

Affected Version 4.0.0 RC 5

Fixed Version 4.0.0

Milestone VaultWiki 4.0 Gold

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)

December 15, 2014 11:14 AM
pegasus

VaultWiki Team
1. VaultWiki assumes that the sub-domain is parked on top of the normal domain. It will not let you name the wiki_index.php file the same as another existing file. If you want to name it index.php, you will have to modify vault/core/model/settings/vw_filename/vw.php. Find:

Code:

if ($value == '')

Replace with:

Code:

if (1)

Which will let you name the wiki file anything, even if it conflicts with another file.

2. I would maintain a backup of your current database with both VW3 and VW4. Make a note what the backup is. Make sure to upload the /vault folder from the /do_not_upload directory in the ZIP. Then remove VW3 from vBulletin products. I like to keep backups forever, but you can use your own discretion. If the backup is ever used, it would likely only be to run the import script again (if you discovered that the importer doesn't copy something you were used to).

3. The subdomain files for VaultWiki 4 are located in the /do_not_upload folder in the ZIP. These should replace all the sub-domain files if the wiki is the only thing on that subdomain. If you also use the sub-domain for the forum, then ONLY upload files that start with 'wiki_' and 'yui_'.
Reply
December 15, 2014 11:34 AM

beernuts

Junior Member

1. That worked, thanks.

2. I'm happy to leave VW3 installed, but can I disable it while leaving VW4 active?

3. I've uploaded the new subdomain files. The subdomain is at /home/{user}/public_html/wiki and VB is at /home/{user}/public_html/vb. Unfortunately I'm now getting a blank page. When I looked at the error logs, I saw a fatal error about chdir() not passing a valid directory. I looked through the code and in showwiki_proxy.php on the Wiki subdomain, on line 25 you have chdir(VW_VB_PATH) but I think that should be chdir(VW_DEPS_PATH) right? Unfortunately when I make that change, I just get error output when visiting our Wiki. Fatal Error: attempted to instantiate non-existent class vw_Dependency_Model

Reply
December 15, 2014 11:56 AM

pegasus

VaultWiki Team

2. Yes.

3. showwiki_proxy.php is no longer used. Any routing through showwiki_proxy.php should instead be pointed to wiki_index.php. You should also edit the file vw_config.php in the subdomain folder to make sure the paths are set correctly.

Reply

December 15, 2014 12:14 PM

beernuts

Junior Member

OK, still not sure what is going on.

I've edited vw_config.php and changed DEPOT_PATH to /home/{user}/public_html/wiki which is the document root for the subdomain.

I've changed DEPS_PATH to /home/{user}/public_html/vb which is the document root for vBulletin.

I have updated our nginx configuration. We have a server block specifically for our wiki.{domain}.com subdomain. It looks like this now:

Code:

server {
  server_name wiki.site.com;
  root "/home/user/public_html/wiki";

  index index.php;
  client_max_body_size 10m;

  access_log /home/user/_logs/wiki.access.log;
  error_log /home/user/_logs/wiki.error.log;

#  location /vault {
#      rewrite ^ $uri last;
#  }

#  location / {
#       if ($request_uri !~ \.(?:php|js|css)) {
#     set $redirect_url $fastcgi_script_name;
#
#     rewrite ^ /wiki_index.php last;
#       }
# }

location ~ ^/index\.php$ {
  rewrite ^ /wiki_index.php;
}

  location ~ "^(.+\.php)($|/)" {
    fastcgi_split_path_info ^(.+\.php)(.*)$;
    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
    fastcgi_param SCRIPT_NAME $fastcgi_script_name;
    fastcgi_param PATH_INFO $fastcgi_path_info;
    fastcgi_param SERVER_NAME $host;
#    fastcgi_param REDIRECT_URL $redirect_url;
    fastcgi_pass 127.0.0.1:9000;
    fastcgi_param PHP_VALUE "newrelic.appname=Site Name";
    include        fastcgi_params;
  }
}

But I'm still getting blank pages when viewing the wiki. In the error log I'm seeing

Code:

PHP message: PHP Fatal error:  require_once(): Failed opening required './vw_config.php' (include_path='.:/usr/share/php:/usr/share/pear') in /home/user/public_html/wiki/wiki_index.php on line 22" while reading response header from upstream, client: 173.216.46.71, server: wiki.site.com, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "wiki.site.com"

December 15, 2014 1:11 PM

pegasus

VaultWiki Team

Is vw_config.php in /public_html/wiki? The error message is saying it can't find it there.

Also, in your configuration, both DEPOT_PATH and DEPS_PATH should be the document root for vBulletin. It is rare that DEPOT_PATH would be set to something else.

Reply
December 15, 2014 1:16 PM

beernuts

Junior Member

Yes /home/user/public_html/wiki/vw_config.php does exist and is readable.

After changing the DEPOT_PATH to VB's root (I couldn't find any info on what to set this to before. I made my best guess), we've now got a page loading, but it's simply loading VB's FORUMHOME view.

Reply
December 15, 2014 1:23 PM

beernuts

Junior Member

OK, some clarification. wiki.{site}.com is loading the FORUMHOME view. wiki.{site}.com/index.php is loading the front page of the Wiki, but it's showing some default Home article and not our old wiki home page. As well, friendly URLs (wiki.{site}.com/Page) are simply redirecting to index.php instead of showing the content.

Can you give me an example nginx conf for VW? What we used to use no longer works, but what I found in the VW4 docs also isn't doing the job.

Reply
December 15, 2014 1:27 PM

pegasus

VaultWiki Team

In your /vault/config.php file, try changing the value of VW_DEFAULT_SCRIPT to 'wiki_index.php'
That value is used to route requests that might belong to non-wiki pages, but your wiki has a separate sub-domain anyway, so there's no need for it to be different.

Reply
December 15, 2014 1:29 PM

beernuts

Junior Member

OK, that change allowed wiki.{site}.com to load up the wiki content, but I'm still seeing some default page in place of our normal wiki homepage, and URLs are simply redirecting back to the wiki homepage (IE wiki.site.com/User:Username)

Reply

December 15, 2014 1:35 PM

beernuts

Junior Member

OK, I actually take back what I said. We are definitely having issues with the nginx rules. Loading up a Wiki article is throwing a nginx 404 so something is wrong with our rewrite rules.

Here is our current nginx config for the subdomain

Code:

server {
  server_name wiki.site.com;
  root "/home/site/public_html/wiki";

  index index.php;
  client_max_body_size 10m;

  access_log /home/site/_logs/wiki.access.log;
  error_log /home/site/_logs/wiki.error.log;


#  location /vault {
#      rewrite ^ $uri last;
#  }

#  location / {
#       if ($request_uri !~ \.(?:php|js|css)) {
#     set $redirect_url $fastcgi_script_name;
#
#     rewrite ^ /wiki_index.php last;
#       }
# }

location ~ ^/index\.php$ {
  rewrite ^ /wiki_index.php;
}

Obviously there is no code there to send all requests to wiki_index.php but when I enable our old code that did this, I get redirect loops.

December 15, 2014 1:52 PM

pegasus

VaultWiki Team

Your location / block looks okay to do what you want, (no index.php, just wiki.site.com/WikiPageTitle), but your wiki settings may not be set this way yet. The wiki would try to redirect you to the default script (in this case index.php), if it doesn't know what your URLs mean.

What are your values under Settings > Site Config?

To have no path between wiki.site.com and WikiPageTitle, you would need to leave the Wiki File Name setting blank.
You need URL format set to the second or third option (second is the old VW3 format).

We will deal with the issue of your old home page once you can access most other pages okay.

Reply
December 15, 2014 2:06 PM

beernuts

Junior Member

Settings have been changed to this: http://awesomescreenshot.com/03941bioed

But still getting hard (Web server) 404s on all pages because nginx is looking for a physical file called "User:beernuts" for example, instead of sending that request to the wiki script, because there is no rule in place that does that.

Reply
December 15, 2014 2:06 PM

beernuts

Junior Member

Also, no matter what I do, I can't set "Wiki Active" to yes. It always reverts to No.

Reply
December 15, 2014 2:14 PM

beernuts

Junior Member

OK, got the pages working now. I missed where you had said that the location / block looks correct. I re-enabled it and disabled everything else and now we're actually passing data into VaultWiki, but no nodes are found.

Reply
December 15, 2014 2:15 PM

beernuts

Junior Member

It seems like I can't change the settings. I can't enable the Wiki and I can't change the URL format.

Reply

+ Reply

All times are GMT -4. The time now is 6:06 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: What to do after upgrading to VW 4?

Issue Tools