• Hello,

    I have a fairly large site running vbulletin. I’d like to create a few pages internally using wordpress since it’s so easy to use.

    However I’m afraid that after installing wordpress, the default home page will become the wordpress page, rather than my forum CMS.

    How do I avoid this? Any help is appreciated.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Greetings

    These ideas come to you in the absence of my any knowledge regarding vbulletin.

    This article should prove helpful: https://stackoverflow.com/questions/6358293/how-can-i-serve-static-pages-alongside-wp-3-0-multi-site

    The gist of it is for when you already have the WordPress and want to add non-WordPress pages alongside.

    In your case it’s reverse, one possibility to install the WordPress and rename the index.php to disable it front-end. Another method would be do a subfolder install of WordPress, put the redirection plugin in place and configure, then if needed promote the WordPress to appear as if at the root.

    FYI if you’re really good you can write your own .htaccess rules instead of using the plugin.

    Good Luck

    Thread Starter alaera

    (@alaera)

    Thanks for the reply. It looks as though I could simply ensure that my current index file persists after installing wordpress?

    I’m not sure how a redirect plugin would help, perhaps I’m missing something?

    What happens when you install wordpress in a subfolder on a blank site? Does the root index file change? If I were to install wordpress in a root folder, how would I then access it?

    Great questions,

    What happens when you install wordpress in a subfolder on a blank site? Does the root index file change?

    Yes, that essentially is correct. A blank site would have no index file, before nor after installation of WordPress into a subfolder of the root.

    If I were to install wordpress in a root folder, how would I then access it?

    WordPress always is “accessed” via it’s index.php , no matter where it is installed. Generally there’s 3 possibilities:

    1. WordPress installed in THE site’s root directory
    2. WordPress installed in any subdirectory of the root directory
    3. WordPress installed in any subdirectory of the root directory, and with its index.php moved to the root. That’s the “promotion” scenario I mentioned above.

    So if vbulletin uses its own index.php in the root, I think option 2 is you only possibility.

    If vbulletin uses index.html, any of the three options are available. With options 1 or 3, you would need the WordPress redirection plugin or .htaccess rules to force requests for index.html to bypass index.php which normally has higher priority.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Install WordPress but don't make it default landing page’ is closed to new replies.