Upgrade to VB5 but can login into forum

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • kichigaikid
    Member
    • Nov 2008
    • 47
    • 3.7.x

    Upgrade to VB5 but can login into forum

    I've upgrade from VB4 to VB5 but I cant login into forum. The forum are going nowhere.

    My forum URL is http://community.siutao.com but when I click forum i goes to http://community.siutao.com/#

    I cant also login into admincp via http://community.siutao.com/admincp or http://community.siutao.com/markasadmin (when i rename the admincp into markasadmin)

    I can login into admincp via http://community.siutao.com/core/admincp

    How can i back to my forum?
  • kokopellitr
    New Member
    • Sep 2012
    • 1
    • 3.8.x

    #2
    i am also have this problem.

    Comment

    • Mark.B
      vBulletin Support
      • Feb 2004
      • 24288
      • 6.0.X

      #3
      Originally posted by kokopellitr
      i am also have this problem.
      Please start your own thread with full details.

      - - - Updated - - -

      Originally posted by kichigaikid
      I've upgrade from VB4 to VB5 but I cant login into forum. The forum are going nowhere.

      My forum URL is http://community.siutao.com but when I click forum i goes to http://community.siutao.com/#

      I cant also login into admincp via http://community.siutao.com/admincp or http://community.siutao.com/markasadmin (when i rename the admincp into markasadmin)

      I can login into admincp via http://community.siutao.com/core/admincp

      How can i back to my forum?
      You should never be using "/core" in any URL via the browser.
      It sounds like you have your URLs set wrongly either in the admincp or more likely in one of your config files.
      MARK.B
      vBulletin Support
      ------------
      My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
      My Unofficial vBulletin Cloud Demo: https://www.adminammo.com

      Comment

      • kichigaikid
        Member
        • Nov 2008
        • 47
        • 3.7.x

        #4
        Originally posted by Mark.B

        You should never be using "/core" in any URL via the browser.
        It sounds like you have your URLs set wrongly either in the admincp or more likely in one of your config files.
        i didn't use /core URL in browser.

        I give u my config.php files

        The first one in root folder of my forum :

        [QUOTE]| When making changes to the file, the edit should always || be to the right of the = sign between the single quotes |
        | Default: $config['admincpdir'] = 'markasadmin'; |
        | Example: $config['admincpdir'] = 'myadmin'; GOOD! |
        | Example: $config['myadmin'] = 'admincp'; BAD! |
        \*-------------------------------------------------------*/




        // ****** Base URLs ******
        // The following settings all deal with the url of your forum.
        // If set incorrectly your site/software will not function correctly.
        // These urls should NOT include a trailing slash
        // This is the url and web path of your root vBulletin directory
        $config['baseurl'] = 'http://community.siutao.com';




        // This will only be used if you wish to require https logins
        // You will not need to change this setting most of the time.
        $config['baseurl_login'] = $config['baseurl'];


        // If you do wish to use https for login, uncomment this line
        // Then fill in your https url.
        //$config['baseurl_login'] = 'https://www.yourdomain.com/folder';




        // ****** System Paths ******


        // This setting allows you to change the name of the admin folder
        $config['admincpdir'] = 'markasadmin';


        // ****** Cookie Settings ******
        // These are cookie related settings.
        // This Setting allows you to change the cookie prefix
        $config['cookie_prefix'] = 'bb';




        // ****** Special Settings ******
        // These settings are only used in some circumstances
        // Please do not edit if you are not sure what they do.


        // You can ignore this setting for right now.
        $config['cookie_enabled'] = true;


        $config['report_all_php_errors'] = false;
        $config['no_template_notices'] = true;


        // This setting enables debug mode, it should NEVER be used on a live site
        $config['debug'] = false;


        // Assumes default location of core.
        // These are the system paths and folders for your vBulletin files
        // This setting is for where your vbulletin core folder is
        $config['core_path'] = realpath(dirname(__FILE__)) . '/core';


        // This is the url and web based path to your core directory
        $config['baseurl_core'] = $config['baseurl'] . '/core';[QUOTE]

        - - - Updated - - -

        The one in core/includes/config.php

        /*----------------------------------------------------------------------*\
        | ****** NOTE REGARDING THE VARIABLES IN THIS FILE ****** |
        +------------------------------------------------------------------------+
        | If you get any errors while attempting to connect to MySQL, you will |
        | need to email your webhost because we cannot tell you the correct |
        | values for the variables in this file. |
        | |
        | When making changes to the file, the edit should always be to the |
        | right of the = sign between the single quotes |
        | Default: $config['admincpdir'] = 'admincp'; |
        | Example: $config['admincpdir'] = 'myadmin'; GOOD! |
        | Example: $config['myadmin'] = 'admincp'; BAD! |
        \*----------------------------------------------------------------------*/




        // ****** DATABASE TYPE ******
        // This is the type of the database server on which your vBulletin database
        // will be located. Valid options are mysql and mysqli, for slave support add
        // _slave to the end of the database class.
        // Try to use mysqli if you are using PHP 5 and MySQL 4.1+
        $config['Database']['dbtype'] = 'mysql';


        // ****** DATABASE NAME ******
        // This is the name of the database where your vBulletin will be located.
        // This must be created by your webhost.
        $config['Database']['dbname'] = 'siutaoc_mydatabase';


        // ****** TABLE PREFIX ******
        // Prefix that your vBulletin tables have in the database.
        $config['Database']['tableprefix'] = 'vbstc_';


        // ****** TECHNICAL EMAIL ADDRESS ******
        // If any database errors occur, they will be emailed to the address specified here.
        // Leave this blank to not send any emails when there is a database error.
        $config['Database']['technicalemail'] = '[email protected]';




        // ****** MASTER DATABASE SERVER NAME AND PORT ******
        // This is the hostname or IP address and port of the database server.
        // If you are unsure of what to put here, leave the default values.
        //
        // Note: If you are using IIS 7+ and MySQL is on the same machine, you
        // need to use 127.0.0.1 instead of localhost
        $config['MasterServer']['servername'] = 'localhost';
        $config['MasterServer']['port'] = 3306;


        // ****** MASTER DATABASE USERNAME & PASSWORD ******
        // This is the username and password you use to access MySQL.
        // These must be obtained through your webhost.
        $config['MasterServer']['username'] = 'xxxxxxxx';
        $config['MasterServer']['password'] = 'xxxxxxxx';


        // ****** MASTER DATABASE PERSISTENT CONNECTIONS ******
        // This option allows you to turn persistent connections to MySQL on or off.
        // The difference in performance is negligible for all but the largest boards.
        // If you are unsure what this should be, leave it off. (0 = off; 1 = on)
        $config['MasterServer']['usepconnect'] = 0;






        // ****** SLAVE DATABASE CONFIGURATION ******
        // If you have multiple database backends, this is the information for your slave
        // server. If you are not 100% sure you need to fill in this information,
        // do not change any of the values here.
        $config['SlaveServer']['servername'] = '';
        $config['SlaveServer']['port'] = 3306;
        $config['SlaveServer']['username'] = '';
        $config['SlaveServer']['password'] = '';
        $config['SlaveServer']['usepconnect'] = 0;






        // ****** PATH TO ADMIN & MODERATOR CONTROL PANELS ******
        // This setting allows you to change the name of the folders that the admin and
        // moderator control panels reside in. You may wish to do this for security purposes.
        // Please note that if you change the name of the directory here, you will still need
        // to manually change the name of the directory on the server.
        $config['Misc']['admincpdir'] = 'markasadmin';
        $config['Misc']['modcpdir'] = 'modcp';


        // Prefix that all vBulletin cookies will have
        // Keep this short and only use numbers and letters, i.e. 1-9 and a-Z
        $config['Misc']['cookieprefix'] = 'bb';


        // ******** FULL PATH TO FORUMS DIRECTORY ******
        // On a few systems it may be necessary to input the full path to your forums directory
        // for vBulletin to function normally. You can ignore this setting unless vBulletin
        // tells you to fill this in. Do not include a trailing slash!
        // Example Unix:
        // $config['Misc']['forumpath'] = '/home/users/public_html/forums';
        // Example Win32:
        // $config['Misc']['forumpath'] = 'c:\program files\apache group\apache\htdocs\vb3';
        $config['Misc']['forumpath'] = '/home/siutaoc/public_html/community';


        // ****** USERS WITH ADMIN LOG VIEWING PERMISSIONS ******
        // The users specified here will be allowed to view the admin log in the control panel.
        // Users must be specified by *ID number* here. To obtain a user's ID number,
        // view their profile via the control panel. If this is a new installation, leave
        // the first user created will have a user ID of 1. Seperate each userid with a comma.
        $config['SpecialUsers']['canviewadminlog'] = '1';


        // ****** USERS WITH ADMIN LOG PRUNING PERMISSIONS ******
        // The users specified here will be allowed to remove ("prune") entries from the admin
        // log. See the above entry for more information on the format.
        $config['SpecialUsers']['canpruneadminlog'] = '1';


        // ****** USERS WITH QUERY RUNNING PERMISSIONS ******
        // The users specified here will be allowed to run queries from the control panel.
        // See the above entries for more information on the format.
        // Please note that the ability to run queries is quite powerful. You may wish
        // to remove all user IDs from this list for security reasons.
        $config['SpecialUsers']['canrunqueries'] = '';


        // ****** UNDELETABLE / UNALTERABLE USERS ******
        // The users specified here will not be deletable or alterable from the control panel by any users.
        // To specify more than one user, separate userids with commas.
        $config['SpecialUsers']['undeletableusers'] = '1';


        // ****** SUPER ADMINISTRATORS ******
        // The users specified below will have permission to access the administrator permissions
        // page, which controls the permissions of other administrators
        $config['SpecialUsers']['superadministrators'] = '1';


        // ****** CACHE CONFIGURATION *****
        // Here you can configure different methods for caching items.
        // The following are the cacheing classes that can be used.
        // vB_Cache_Db - This setting stores the data in the database
        // vB_Cache_Memcached - This stores the data in memcache
        // vB_Cache_Memory - This setting uses php's memory while a page is being generated.
        // Each cache area can use its own cache type.
        $config['Cache']['class'][0] = 'vB_Cache_Db'; //regular cache
        $config['Cache']['class'][1] = 'vB_Cache_Memory'; //fastest cache
        $config['Cache']['class'][2] = 'vB_Cache_Db'; //largest cache and longest life.


        //Cache options are
        //vB_Cache_Memory - fastest but doesn't survive a page load.
        //vB_Cache_Db- significant speed improvement and available to everyone.
        //vB_Cache_Filesystem good performance, reduces traffic and load on db server. Not available to everyone- your web server must be able to write to the database.
        //vB_Cache_Memcached excellent performance but usually only available to dedicated or virtual hosted sites.




        // ******** FILESYSTEM CACHE CONFIGURATION ******
        //If you use filesystem cache you MUST uncomment the line below.
        //set the path to somewher writeable by the web server process. This location must already exist. Please put
        // this somewhere outside the document root. Otherwise you have just created a serious security issue.
        //Don't include the final '/'


        //$config['Cache']['fileCachePath'] = '/valid/writeable/for/my/webserver';




        // ****** DATASTORE CACHE CONFIGURATION *****
        // Here you can configure different methods for caching datastore items.
        // vB_Datastore_Filecache - to use includes/datastore/datastore_cache.php
        // vB_Datastore_APC - to use APC
        // vB_Datastore_XCache - to use XCache
        // vB_Datastore_Memcached - to use a Memcache server, more configuration below
        // $config['Datastore']['class'] = 'vB_Datastore_Filecache';


        // ******** DATASTORE PREFIX ******
        // If you are using a PHP Caching system (APC, XCache, eAccelerator) with more
        // than one set of forums installed on your host, you *may* need to use a prefix
        // so that they do not try to use the same variable within the cache.
        // This works in a similar manner to the database table prefix.
        // $config['Datastore']['prefix'] = '';


        // It is also necessary to specify the hostname or IP address and the port the server is listening on
        /*
        $config['Datastore']['class'] = 'vB_Datastore_Memcached';
        $i = 0;
        // First Server
        $i++;
        $config['Misc']['memcacheserver'][$i] = '127.0.0.1';
        $config['Misc']['memcacheport'][$i] = 11211;
        $config['Misc']['memcachepersistent'][$i] = true;
        $config['Misc']['memcacheweight'][$i] = 1;
        $config['Misc']['memcachetimeout'][$i] = 1;
        $config['Misc']['memcacheretry_interval'][$i] = 15;
        */


        // ****** The following options are only needed in special cases ******


        // ****** MySQLI OPTIONS *****
        // When using MySQL 4.1+, MySQLi should be used to connect to the database.
        // If you need to set the default connection charset because your database
        // is using a charset other than latin1, you can set the charset here.
        // If you don't set the charset to be the same as your database, you
        // may receive collation errors. Ignore this setting unless you
        // are sure you need to use it.
        // $config['Mysqli']['charset'] = 'utf8';


        // Optionally, PHP can be instructed to set connection parameters by
        // reading from the file named in 'ini_file'. Please use a full path to
        // the file.
        // Example:
        // $config['Mysqli']['ini_file'] = 'c:\program files\MySQL\MySQL Server 4.1\my.ini';
        $config['Mysqli']['ini_file'] = '';


        // ******** IMAGE PROCESSING OPTIONS ********
        // Images that exceed either dimension below will not be resized by vBulletin.
        // If you need to resize larger images, alter these settings.
        $config['Misc']['maxwidth'] = 2592;
        $config['Misc']['maxheight'] = 1944;


        // ******** SPECIAL SETTINGS ********
        // The following are settings/permissions that are not normally used but
        // are here for reference. Please be careful using them. Do not enable or
        // uncomment without understanding what they do first.


        // This allows you to disable modifications and extensions to the software.
        // If your site is not functioning well after installing or using a third
        // party modification, please enable this.
        // define("DISABLE_HOOKS", true);


        // This allows you to shut down all mail that is being sent by vBulletin.
        // This is useful for test environments
        // define("DISABLE_MAIL", true);


        // This allows you to enter debug mode, which is for support or development
        // to help understand how pages are built. This should NEVER be enabled in
        // a live environment.
        // $config['Misc']['debug'] = true;


        // This enables debug logging. The debuglogger is controlled from the
        // file core/includes/xml/logger.xml. This is safe to run on a live
        // environment, assuming the log location is secure, however it may
        // impact peformance to have the logging on.
        // $config['Misc']['debuglogging'] = true;
        - - - Updated - - -

        When I pointed to the forum, the URL links to http://community.siutao.com/#

        Comment

        • Wayne Luke
          vBulletin Technical Support Lead
          • Aug 2000
          • 74154

          #5
          Originally posted by kichigaikid
          When I pointed to the forum, the URL links to http://community.siutao.com/#

          On your site, the Forum tab, CMS tab and Custom tab can be deleted. They aren't really used.
          Translations provided by Google.

          Wayne Luke
          The Rabid Badger - a vBulletin Cloud demonstration site.
          vBulletin 5 API

          Comment

          • Acido
            Member
            • Sep 2003
            • 45

            #6
            ok , thank you!

            Comment

            Related Topics

            Collapse

            Working...