No announcement yet.

Settings / Members missing after 4.2.5 to 5.4.2 upgrade

  • Filter
  • Time
  • Show
Clear All
new posts

  • Settings / Members missing after 4.2.5 to 5.4.2 upgrade

    I have run an upgrade on a test DB. Everything works well (it would seem) except User Profiles and Settings.

    When trying to access them, I just get an error "That action could not be completed. Please try again, and if this occurs again please contact the system administrator and tell them how you got this message."

    If I try to go to "My Profile", the link leads to a folder .../forum/member/... This folder does not exist, though.
    Same thing with user settings ../forum/settings/... does not exist

    I am assuming that the missing signatures in the posts are also to be attributed to this problem?

    Any help much appreciated.

  • #2
    vBulletin 5 does not use folders. They are virtual links and everything is run from index.php in reality.

    Make sure you have NO vBulletin 4 files present on the server. Unlike earlier versions, a vB4 to vB5 upgrade requires a clean directory (aside from attachments and avatars if they are stored in the file system). The presence of any vB4 files will cause errors and break stuff.

    Assuming it's not that - Please put your site into debug mode and let us know the full error that is displayed:
    Last edited by Mark.B; Tue 10th Jul '18, 10:47am.

    TalkNewsUK - My vBulletin 5.5.1 Demo
    AdminAmmo - My Cloud Demo


    • #3
      The vBulletin 4 installation is on the same server (the forum is still live so that I can check the migration before doing it on the live database). However, the files are in a different directory (/forum rather than /forum_vb5).

      How do I put the forum into debug mode?


      • #4
        I added $config['Misc']['debug'] = true; to the config.php file and it made no difference. No extra messages, just the same as before.....


        • #5
          What is also now happening is when I log in the logged in version of the forum homepage is shown in the log in window. Strange ...


          • #6
            OK. Got debug mode running.

            Error is:
            Debug: Error
            occurred in file /home/DOMAIN/public_html/forum_vb5/includes/vb5/frontend/routing.php on line 140
            • Function setRoutes in file /home/DOMAIN/public_html/forum_vb5/includes/vb5/frontend/application.php line 21
            • Function init in file /home/DOMAIN/public_html/forum_vb5/index.php line 48

            Debug Information:
            • Page ID:
            • Parent ID:
            • Page Template ID:
            • Route ID:
            • Page Type:
            • Screen Layout ID:
            • Screen Layout Template:
            • Channel ID:
            • Node ID:
            • Database Asserts: 113 (?)
            • AJAX Requests: 3
            • Facebook Active: Yes
            • Style ID: 49
            • Templates/Renders: 18/28
            • CSS Templates: 4
            • JS Files: 7
            • Included Files: 153
            • Autoloaded Classes: 147
            • Current Time: Tue, 10 Jul 2018 19:20:20 +0200
            • Page Time:

            P.S. Turning debug off again as some other users have access for testing


            • #7
              P.S. For some reason, my database has increased from 550MB (vB4) to 1210MB (vB5). Is this normal?


              • #8
                I just completed a new trial upgrade.
                - Created a copy of the vB4 database
                - Ran the upgrade script with no errors
                - Checked the forum
                - The issue of the missing profile / settings for members remains

                Any help appreciated here. Thanks.


                • #9
                  Received the following error email (maybe it helps?):
                  BTW -- I only tried to open my user profile ....nothing else

                  Database error in vBulletin 5.4.2:

                  Invalid SQL:

                  ### Channels ###
                  SELECT follow.title AS title, follow.nodeid AS keyval, 'node' AS sourcetable, IF(follow.lastcontent = 0, follow.lastupdate, follow.lastcontent) AS lastactivity,
                  follow.totalcount AS activity, type.class AS type,
                  (follow.nodeoptions & 512) AS noUnsubscribe
                  FROM node AS follow
                  INNER JOIN contenttype AS type ON type.contenttypeid = follow.contenttypeid

                  INNER JOIN subscribediscussion AS sd ON sd.discussionid = follow.nodeid AND sd.userid = 23
                  UNION ALL

                  ### Users ###
                  SELECT follow.username AS title, follow.userid AS keyval, 'user' AS sourcetable, IFNULL(follow.lastpost, follow.joindate) AS lastactivity,
                  follow.posts as activity, 'Member' AS type,
                  0 AS noUnsubscribe
                  FROM user AS follow
                  INNER JOIN userlist AS ul ON ul.relationid = follow.userid AND ul.userid = 23
                  WHERE ul.type = 'follow' AND ul.friend = 'yes'
                  ORDER BY title ASC LIMIT 100;

                  MySQL Error : Illegal mix of collations for operation 'UNION'
                  Error Number : 1271
                  Request Date : Friday, July 13th 2018 @ 05:42:21 AM
                  Error Date : Friday, July 13th 2018 @ 05:42:21 AM
                  Script :
                  Referrer :
                  IP Address :
                  Username : USER
                  Classname : vB_Database_MySQLi
                  MySQL Version : 10.1.31-MariaDB-cll-lve

                  Stack Trace:
                  #0 vB_Database->getErrorData() called in [path]/vb/database.php on line 1188
                  #1 vB_Database->halt() called in [path]/vb/database/mysqli.php on line 201
                  #2 vB_Database_MySQLi->execute_query() called in [path]/vb/database.php on line 557
                  #3 vB_Database->query_read() called in [path]/vb/db/result.php on line 126
                  #4 vB_dB_Result->rewind() called in [path]/vb/db/result.php on line 63
                  #5 vB_dB_Result->__construct() called in [path]/packages/vbforum/db/mysql/querydefs.php on line 6500
                  #6 vBForum_dB_MYSQL_QueryDefs->getUserFollowing() called in [path]/vb/db/query/method.php on line 175
                  #7 vB_dB_Query_Method->execSQL() called in [path]/vb/db/assertor.php on line 304
                  #8 vB_dB_Assertor->assertQuery() called in [path]/vb/db/assertor.php on line 653
                  #9 vB_dB_Assertor->getRows() called in [path]/vb/api/follow.php on line 387
                  #10 vB_Api_Follow->getFollowing() called in [path]/vb/api/user.php on line 192
                  #11 vB_Api_User->fetchProfileInfo() called in [path]/vb5/route/profile.php on line 98
                  #12 vB5_Route_Profile->setBreadcrumbs() called in [path]/vb5/route.php on line 387
                  #13 vB5_Route->getBreadcrumbs() called in [path]/vb/api/route.php on line 341
                  #14 vB_Api_Route->getRoute() called in [path]/vb/api/wrapper.php on line 199
                  #15 vB_Api_Wrapper->__call() called in /home/DOMAIN/public_html/forum_vb5/includes/api/interface/collapsed.php on line 101
                  #16 Api_Interface_Collapsed->callApi() called in /home/DOMAIN/public_html/forum_vb5/includes/vb5/frontend/routing.php on line 120
                  #17 vB5_Frontend_Routing->setRoutes() called in /home/DOMAIN/public_html/forum_vb5/includes/vb5/frontend/application.php on line 21
                  #18 vB5_Frontend_Application::init() called in /home/DOMAIN/public_html/forum_vb5/index.php on line 48


                  • #10
                    Everything else seems to be working, as far as I can tell.

                    It's "just"
                    - access to user profile
                    - access to user settings
                    - display of user signatures
                    That are giving errors.

                    Please advise ..... PLEASE


                    • #11
                      Thanks to Trevor for pointing me in the right direction. It was all down to a collation issue. So, for anyone who may experience this issue in future, "just" change the collation of the database, all tables and columns to utf8

                      I used the following to make life a bit more simple:


                      Related Topics