Announcement

Collapse
No announcement yet.

[Help] Error from update 5.0.3

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • [Help] Error from update 5.0.3

    Hello everyone!

    So a few days ago I noticed there was an update for vBulletin 5 Connect, so I just had to download it. Once I downloaded the update I started updating it from "install/update.php" Everything worked fine, not a warning or a error message UNTIL I noticed that my entire forum stoppped working.

    So I thought I had some missed files or somthing new in my config files. So I reconfiged all config files, also re-uploaded all files 4 times.(Last time just now) I talked to my host support they couldn't see anything they said that I'm probably missing a file. Config files and all that where correct according to them.

    Anyways, I got not clue what the problem is. I checked the php file where the error is located. It's the same since the old api file. IF I upload the old API files the main page works on the forum but nothing else. I'm getting a little pissed since my website some how got a hacking target so everyone tries to hack it, so as it is my gaming community just have the forums right now. So right now the entire website is down.

    Code:
    Fatal error: Call to a member function fetch_userinfo_value() on a non-object in /forums/core/vb/api/state.php on line 341

  • #2
    Did the upgrader finish?

    If so, can you login to the AdminCP?
    Lastly, if you can login to the AdminCP, go into the usergroup manager and turn off password expiry for the administrator usergroup
    Then, turn your forum back on, if it was set to off.

    If this still isn't working, let us know.

    Comment


    • #3
      Hi,

      Yes the update was finished and completed. After the update was done it askes you to go to the admincp or the forums I think not 100% but at least the admincp. I've tried all of them, forums, admincp, topics and all that still the same issue.

      Sincerely

      Comment


      • #4
        Going to open a ticket for you, I've got an idea whats wrong, but i'll need to poke the database.

        Looks like you've got a ticket in with wayne Already though.
        Last edited by Zachery; Tue 2nd Jul '13, 2:50pm.

        Comment


        • #5
          Yes, thats correct but didn't give me a response until now so I thought I where going on here to get some help.

          Comment


          • #6
            That's fine its not something we've run across before.

            Comment


            • #7
              Ben - Did you get a resolution to this? Looks like I have the same exact problem.

              Same symptoms and process that got me there.

              Thanks!

              (i did open a ticket as well : 1203299)
              Last edited by ecrotty; Tue 2nd Jul '13, 5:25pm. Reason: added ticket info

              Comment


              • #8
                Escrotty, I've so far got not solution to this, the operator who answered my ticket recommended me to restart my website since it's catching apparently, but when I talked to my support they said that my php catching system was turned off on my domain as well that it's not possible to restart any server since there are more then me who using the same server but have an additional domain.

                Comment


                • #9
                  Originally posted by Ben_Sherman View Post
                  Escrotty, I've so far got not solution to this, the operator who answered my ticket recommended me to restart my website since it's catching apparently, but when I talked to my support they said that my php catching system was turned off on my domain as well that it's not possible to restart any server since there are more then me who using the same server but have an additional domain.
                  Ok. Looks like we are at the same stage. I was asked to restart apache as well.

                  That didn't do the trick.

                  I have a bit more flexibility in my server so perhaps I can try a few more things out that you may unable to do while working with support.

                  I'll try and keep you updated with the issues and any possible resolution that I come across.

                  Comment


                  • #10
                    I have a very rough-and-ready fix

                    1) Edit /forum/core/vb/api/state.php

                    There are a few lines that you should comment out, these are the blocks and this is how they should be commented out:
                    PHP Code:
                    /*
                    * Check password is the same as username
                    */
                    protected function checkPasswordEqualsUsername()
                    {
                        
                    /*if (!defined('ALLOW_SAME_USERNAME_PASSWORD') AND vB::getCurrentSession()->fetch_userinfo_value('userid'))
                        {
                            // save the resource on md5'ing if the option is not enabled or guest
                            if (vB::getCurrentSession()->fetch_userinfo_value('password') == md5(md5(vB::getCurrentSession()->fetch_userinfo_value('username')) . vB::getCurrentSession()->fetch_userinfo_value('salt')))
                            {
                                if (!$this->location['settings'] AND !$this->location['login'])
                                {
                                    return array(
                                    'error' => 'username_same_as_password',
                                    'args' => array(
                                    vB5_Config::instance()->baseurl . '/settings/account'
                                    ));
                                }
                            }
                        }*/
                        
                    return false;



                    PHP Code:
                    /*
                    * Check profile fields
                    */
                    protected function checkProfileUpdate()
                    {
                        
                    /*if (vB::getCurrentSession()->get('profileupdate') AND !$this->location['settings'] AND !$this->location['login'])
                        {
                            return array(
                            'error' => 'updateprofilefields',
                            'args' => array(
                            vB5_Config::instance()->baseurl . '/settings/account'
                            ));
                        }*/
                        
                    return false;

                    PHP Code:
                    /*
                    * Check if user's password is expired
                    *
                    * @return mixed error phrase name on success, false on failure
                    */
                    protected function checkPasswordExpiry()
                    {
                        
                    /*$usergroupid = vB::GetCurrentSession()->fetch_userinfo_value('usergroupid');
                        $usergroup = vB_Api::instanceInternal('usergroup')->fetchUsergroupByID($usergroupid);
                        $passwordexpires = $usergroup['passwordexpires'];

                        if (vB::getCurrentSession()->fetch_userinfo_value('userid') AND $passwordexpires)
                        {
                            $passworddaysold = floor((vB::getRequest()->getTimeNow() - vB::GetCurrentSession()->fetch_userinfo_value('passworddate')) / 86400);

                            if ($passworddaysold >= $passwordexpires)
                            {
                                if (!($this->location['settings']
                                OR $this->location['login']
                                OR $this->location['lostpw']*/
                                // OR $this->location['admincp'] // Now checked in checkBeforeView()
                                /*))
                                {
                                    return array(
                                    'error' => 'passwordexpired',
                                    'args' => array(
                                    $passworddaysold,
                                    vB5_Config::instance()->baseurl . '/settings/account'
                                    ));

                                }
                            }
                        }*/
                        
                    return false;


                    So three blocks that need to have large chunks commented out

                    2) Now load your forum, it will be very slow but will work, log in
                    3) Log into the admin panel
                    4) Clear the cache. I repaired and optimized the database via the admin panel for the sake of it. Now the forum will be faster and will work.

                    One problem, as soon as you uncomment those blocks the forum gives the same error again. And I'm not sure how secure leaving all 3 of those functions permanently returning false is. Now your forum won't check if someone's password is expired (mine had those checks disabled anyway) and the tool to check password security won't work (the one in admin panel which checks if the password is the username) and the 'Check Profile Fields' will always return false (that there were no updates to profile fields).

                    And just to emphasise, clearing the cache at least from within the forum does not get rid of the error as like I said as soon as you uncomment the bits above the error comes back.
                    Last edited by scamtacular; Wed 3rd Jul '13, 8:06am.

                    Comment


                    • ecrotty
                      ecrotty commented
                      Editing a comment
                      That did it.

                      I understand it's more of a workaround but I did want to let you know :

                      1 - it worked.
                      2 - thanks.

                    • scamtacular
                      scamtacular commented
                      Editing a comment
                      Yes sorry it is more of a workaround but the functions are still present (they just all return "Everything's fine" even if users have expired or insecure passwords or "Nothing new" if a profile is updated, but these shouldn't really impact on a forum at all). I'm just an administrator of a forum running this buggy code, not a vBulletin specialist, so I was quite surprised I managed to get around the problem!

                    • ecrotty
                      ecrotty commented
                      Editing a comment
                      No reason to be sorry! It was a tremendous help and service that you did putting it out there for others.

                      The VB team would be included in that group.

                      I'm sure we aren't the only ones with this problem.

                      And you did a great job cleaning up the post too with the code tags.

                      Hats off.

                  • #12
                    This is unbelievable, just did yet an other upgrade and I get the same problem.

                    Since I'm not alone with this problem why would you guys not prioritise this before anything else gets done?
                    And I'm not 100% sure about this, but since all of this happen to me I can no longer make new forum categorys or forums.
                    I only get 'invalid_route_contact_vbulletin_support' and just to be cleared I did not pay $249.00 to just sit and wait and hope some day my website will work again.

                    -Sincerely
                    Ben
                    Last edited by Ben_Sherman; Fri 2nd Aug '13, 4:44am.

                    Comment

                    Related Topics

                    Collapse

                    Working...
                    X