[Suite] Forum in /forum to Suite /index with v4.0.1

[ZoDesigns.com]

Now v4.0.1 says the issue has been resolved so we can now have our forum in /forum and our CMS in /index. My question is if you already have a forum in /forum (actually it is a subdomain), how does the upgrade to the CMS take place? Will it be done automatically or?

[Harv]

I am waiting for someone to comment on this as well - I've been waiting for this to be resolved. Bump

[jhabers]

I am waiting for someone to comment on this as well - I've been waiting for this to be resolved. Bump

copy this to your root as index.php

<?php
/**
 * If you want to move this file to the root of your website, change this 
 * line to your vBulletin directory and uncomment it (delete the //).
 *
 * For example, if vBulletin is installed in '/forum' the line should 
 * state:
 *
 *    define(VB_RELATIVE_PATH, 'forum');
 *
 * Note: You may need to change the cookie path of your vBulletin 
 * installation to enable your users to log in at the root of your website.
 * If you move this file to the root of your website then you should ensure 
 * the cookie path is set to '/'.
 *
 * See 'Admin Control Panel
 *    ->Cookies and HTTP Header Options
 *      ->Path to Save Cookies
 */
define(VB_RELATIVE_PATH, 'forum');

// Do not edit.
if (defined('VB_RELATIVE_PATH'))
{
    chdir('./' . VB_RELATIVE_PATH);
}

/**
 * You can choose the default script here.  Uncomment the appropriate line 
 * to set the default script.  Note: Only uncomment one of these, you must 
 * add // to comment out the script(s) that you DO NOT want to use as your 
 * default script.
 *
 * You can choose the default script even if you do not plan to move this 
 * file to the root of your website.
 */
/**
 * Use the CMS as the default script:
 */
require('content.php');

/**
 * Use the forum as the default script:
 */
//require('forum.php');

[jhabers]

then use this as your index.php file in your /forum folder

<?php
/**
 * If you want to move this file to the root of your website, change this 
 * line to your vBulletin directory and uncomment it (delete the //).
 *
 * For example, if vBulletin is installed in '/forum' the line should 
 * state:
 *
 * define(VB_RELATIVE_PATH, 'forum');
 *
 * Note: You may need to change the cookie path of your vBulletin 
 * installation to enable your users to log in at the root of your website.
 * If you move this file to the root of your website then you should ensure 
 * the cookie path is set to '/'.
 *
 * See 'Admin Control Panel
 * ->Cookies and HTTP Header Options
 *   ->Path to Save Cookies
 */
//define(VB_RELATIVE_PATH, 'forums');

// Do not edit.
if (defined('VB_RELATIVE_PATH'))
{
 chdir('./' . VB_RELATIVE_PATH);
}

/**
 * You can choose the default script here.  Uncomment the appropriate line 
 * to set the default script.  Note: Only uncomment one of these, you must 
 * add // to comment out the script(s) that you DO NOT want to use as your 
 * default script.
 *
 * You can choose the default script even if you do not plan to move this 
 * file to the root of your website.
 */
/**
 * Use the CMS as the default script:
 */
//require('content.php');

/**
 * Use the forum as the default script:
 */
require('forum.php');

[steven s]

Well it still doesn't work on subdomains.

In fact, this works better for me

<?php

chdir('/home/pathtoforum/public_html');
require_once('/home/pathtoforum/public_html/content.php');

[thunderclap]

The HOME Navbar button disappears off The Front Page now. Anyone else notice this?

[melbo]

copy this to your root as index.php

Where did you find that?

[steven s]

The HOME Navbar button disappears off The Front Page now. Anyone else notice this?

No and if you are having an issue, you really need to start your own thread.

[jhabers]

Where did you find that?

one of the dev's posted it in the project forum for this "bug"

[ZoDesigns.com]

But v4.0.1 was supposed to fix the "bug" so I should not have to use that "fix", correct?

[WhatChaMissin]

But v4.0.1 was supposed to fix the "bug" so I should not have to use that "fix", correct?

I totally agree, there shouldn't be a fixed for something that is reported as fix. Either it's not fixed or I'm missing something. Either way an official answer would be appreciated.

[thunderclap]

No and if you are having an issue, you really need to start your own thread.

Why? I was just making an observation and didn't intend to hijack your precious thread.

[steven s]

Why? I was just making an observation and didn't intend to hijack your precious thread.

1) It's not my thread.
2) Your post had nothing to do with this thread.
3) If you are looking for help, the topic should be in the subject line so someone may be able to help you.
4) No need for an attitude.

[melbo]

I was really expecting the contents of my fresh vB4.0.1.zip to have a / folder as well as the normal /upload folder so that the CMS would be in the root. Is this just a rewrite workaround for those of us with an existing (and SEO linked) /Forum?

[steven s]

I was really expecting the contents of my fresh vB4.0.1.zip to have a / folder as well as the normal /upload folder so that the CMS would be in the root. Is this just a rewrite workaround for those of us with an existing (and SEO linked) /Forum?

I wouldn't mind an index.php or content.php file that you dropped in the root directory if it actually worked. I really thought we would have seen a new setting in the admincp.