Wiki Frontpage Customization

[Kaelon]

Hi there,

The main page of my Wiki -- domain.com/wiki -- is a special page which lists all of the namespaces. Is there any way to:

1. Customize the layout and content of this page?

2. Redirect users to another Wiki page?

3. Add search boxes and other Wiki content to a front page, as in this implementation of VaultWiki?

I've been reviewing the Documentation and ran a couple of searches, but didn't see this information readily accessible, so I apologize if it has already been answered elsewhere, but I'm hoping you can help with some context. Thanks!

[pegasus]

There is a new feature in RC 1 which allows you to specify a different wiki page to appear at domain.com/wiki

vBulletin Options > VaultWiki: Server Settings > Replace Wiki Tab with URL

You should enter a wiki URL into this field. The URL of the page entered will be changed to domain.com/wiki, and will now replace the default home page. (The old page URL should 301 to its new location at domain.com/wiki)

[Kaelon]

Thanks, Pegasus!

Is there a way to include the Searchbox (from the default Wiki page) in a custom page?

[pegasus]

There's not, but you can link to the Special:Search page or code your own search box. If you make your own, the custom page can't be cached - you'll need to dynamically add the user's security token to the form:

[var]user|securitytoken[/var]

[Kaelon]

Thanks, Pegasus!

Where can I find more information about the [var] tags?

[Mokonzi]

Details can be found here:

http://www.vaultwiki.org/manual/Parser-Extensions

[InformationNirvana]

I think the default wiki home page here @ vw.org is unimpressive.
I think more thought needs to go into what most people would want for a default wiki homepage.
A search box on the default wiki home page seems like a good idea.
Of course making the default wiki home page easy to customize is an excellent idea.

[vimto]

I've been testing the Replace Wiki Tab with URL option and added a link to my Main Page url, This just took me back to the default showwiki.php page as before and I had to click on the Wiki link there to take me to my main page.

Once on my Main Page I could no-longer edit it, viewing it was fine but if I tried to do anything else it just came up with the old page-not-found error messages in IE and FireFox.

I've had to revert this back to as it was before without anything in the Replace Wiki Tab with URL option to make the site workable (so I can edit things on that page)

FYI I used the complete url to my Main Page http://www.bluedragons.co.uk/forums/...itle=Main+Page

[pegasus]

Ah, it seems that this doesn't exactly work for non-Simple URLs. It also doesn't work unless the default namespace has a custom path.

These are two separate bugs, I've created reports here: http://www.vaultwiki.org/issues/1370/
And here: http://www.vaultwiki.org/issues/1369/

If you have problems with this feature, please continue any discussion there, or create a new report. If you're not using Simple URLs you will not be able to merge threads with the selected page or make the page a translation of another page (using its own Apply tab should work fine) until the next build.

[vimto]

Thanks for looking into this, much appreciated.

[Kaelon]

There is a new feature in RC 1 which allows you to specify a different wiki page to appear at domain.com/wiki

vBulletin Options > VaultWiki: Server Settings > Replace Wiki Tab with URL

You should enter a wiki URL into this field. The URL of the page entered will be changed to domain.com/wiki, and will now replace the default home page. (The old page URL should 301 to its new location at domain.com/wiki)

pegasus -- unfortunately, this didn't work. I entered several URL's -- one to the main Wiki page at http://www.aelyria.com/wiki/Wiki and another to the specific showwiki.php page at http://www.aelyria.com/forums/showwiki.php?title=Wiki and going to www.aelyria.com/wiki still resolved to the old Special Page that shows all of the namespaces. Is this a bug? Or is there something that I am missing?

[pegasus]

As mentioned in this post, it's a combination of two bugs.

[Kaelon]

As mentioned in this post, it's a combination of two bugs.

Ah, thanks. I had actually erroneously only implemented one of the two bug fixes and not both.