Issue: Template pages have disappeared after upgrade to 3.0.2. Agh!

Check AdminCP > VaultWiki > Namespace Manager. At the bottom is a Namespace Functions form. Make sure that Template is assigned as the Template namespace, and not as your Default namespace.

Pegasus, before making any changes, please note that Templates were not setup (and still aren't). These were just pages that happened to be named Template: and were created in ignorance of the Template behaviors of VaultWiki.

If I start making changes to the functions, is there any possibility of my templates being overwritten or something like that?

PS - thanks for getting back to me so quickly!

Changing functions won't overwrite any pages, it just changes how certain pages interact with other pages...

If the Templates you created were regular wiki pages as you say, how are the rest of your pages (without the Template: prefix) faring? Can you find the Template pages in your forum list? If you can find the pages, or you see problems with other pages, you may have to click the [Rebuild All Namespaces] link at the bottom of the Namespace Manager. This was supposed to be done automatically during the upgrade but it's possible it didn't go quite as planned.

Yes, they're just regular wiki pages and they do still show up in the wiki list. Will try the rebuild.

As a further note, I was wrong with the title; templates aren't the only issue. Any page that is in a namespace gets auto-redirected to a page name without namespace prefix.

So most of the pages that I've created over the last couple of weeks are inaccessible.

Note: I have to wait a few hours for the board owner to come online. I am developing the wiki content but I don't have AdminCP access to the VaultWiki settings. I'll let you know if the changes fix the issue.

The Admin got sick of me bugging him so he gave me Admin to the vault wiki section of his site. Here's the problem.

In 2.5.7, you could create a page like Bob:Speaks, and you'd be taken to that page where you can edit-and-save the page. However, in 3.0.2, if you create the page Bob:Speaks and the Namespace 'Bob' hasn't been created, you are automatically taken to Default:Speaks.

So it looks like VW is checking the Namespace section of the page name and, looking for an existing namespace. If it doesn't find one, it simply replaces it with Default.

I would think that the behavior should be the following:
1. Parse out Namespace component
2. If namespace exists and page exists, get the page
3. If namespace DNE, store the page name, as is (including the namespace portion) as the full page name in the default name space (effectively making it Default:Bob:Speaks in this example)


If I'm right, then the only workaround would be to create the myriad of 'virtual namespaces' that I have in the namespace manager (which will create a large number of top-level forums; ick) and then move the appropriate articles out of the default forum and into their respective forums for each of the relevant namespaces, then rebuild all of the name spaces.

Is there an easier way?

Duplicated here. Bug confirmed.

Fixed for the next build. In vault/functions/showwiki.php, find:
Replace with:
Dev note: As of 3.0.2, vB_CES_Vault::fetch_instance('field')->fetch(item) no longer returns NULL when 'item' is not found. Instead, an empty string is returned. The goal was to have consistent output so that type matching worked with all input combinations.