Class_Core.php Errors in VB4.2

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Knightmane
    Member
    • Mar 2007
    • 35
    • 4.2.X

    [Forum] Class_Core.php Errors in VB4.2

    Yesterday afternoon, the entire vbulletin installation suddenly and without warning went blank. After having the server admins at Rackspace look into the problem, they sent me the following message and a list of the exact errors:


    We would note the forums on your site have the following errors in the
    error.log (/log/error.log):

    [Tue Mar 19 21:32:22 2013] [error] [client 59.167.208.223] PHP Parse
    error: syntax error, unexpected 'foreach' (T_FOREACH) in
    /srv/www/ravibrencreations.net/public_html/forum/includes/class_core.php
    on line 3920, referer: http://ravibrencreations.net/
    [Tue Mar 19 21:32:27 2013] [error] [client 59.167.208.223] PHP Parse
    error: syntax error, unexpected 'foreach' (T_FOREACH) in
    /srv/www/ravibrencreations.net/public_html/forum/includes/class_core.php
    on line 3920
    [Tue Mar 19 21:32:32 2013] [error] [client 59.167.208.223] PHP Parse
    error: syntax error, unexpected 'foreach' (T_FOREACH) in
    /srv/www/ravibrencreations.net/public_html/forum/includes/class_core.php
    on line 3920
    [Tue Mar 19 21:32:46 2013] [error] [client 59.167.208.223] PHP Parse
    error: syntax error, unexpected 'foreach' (T_FOREACH) in
    /srv/www/ravibrencreations.net/public_html/forum/includes/class_core.php
    on line 3920, referer: http://ravibrencreations.net/

    We have verified that the apache and php configuration files were the same from before the corruption with a restore from the offsite backup and no other site is having issues but this issue still remains so it will need to be investigated from your side with your forum software.


    Can anyone help me with this issue or is it something new previously undiscovered?
    Thank you in advance.
  • Lynne
    Former vBulletin Support
    • Oct 2004
    • 26255

    #2
    There is nothing on line 3920 in my class_core.php file for 4.2.0PL3. Do you have a modified file? What is on your line 3920 of the class_core.php file?

    Please don't PM or VM me for support - I only help out in the threads.
    vBulletin Manual & vBulletin 4.0 Code Documentation (API)
    Want help modifying your vbulletin forum? Head on over to vbulletin.org
    If I post CSS and you don't know where it goes, throw it into the additional.css template.

    W3Schools <- awesome site for html/css help

    Comment

    • Knightmane
      Member
      • Mar 2007
      • 35
      • 4.2.X

      #3
      There is nothing at my line 3920 either. But on a similar note, I tried to install a test board of a previous version and got the exact same error. Since the different versions use different class_core.php files, why would this error only be happening with Vbulletin? I never had any problems until yesterday.

      Comment

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

        #4
        Please use the config file to disable the plugin system.

        To do this, edit your vBulletin config.php file currently on the server by adding the following line after the <?php line:

        define('DISABLE_HOOKS', true);

        Then reupload the config.php file into your forum's includes folder.

        Afterward, go to the ACP -> Plugins & Products and under both 'Manage Products' and 'Plugin Manager' disable all non-vB products and plugins.

        Make sure to go to both the 'Manage Products' and 'Plugin Manager' locations.

        Then remove that line from the config file.
        Translations provided by Google.

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

        Comment

        • Knightmane
          Member
          • Mar 2007
          • 35
          • 4.2.X

          #5
          I haven't installed anything new in over a year, but I'll give your suggestion a try since nothing else is working anyway... I mean, not even AdminCP appears. brb.

          Comment

          • TheLastSuperman
            Senior Member
            • Sep 2008
            • 1799

            #6
            The host stated:

            "We have verified that the apache and php configuration files were the same from before the corruption with a restore from the offsite backup and no other site is having issues but this issue still remains so it will need to be investigated from your side with your forum software."

            So in fact something was corrupted and while yes all configuration settings may be the exact same, is your PHP version i.e. did they recompile PHP at all?


            Former vBulletin Support Staff
            Hacked recently? See my blog post "Recovering a Hacked vBulletin Site".
            Thinking outside the box? Need modification support? Visit www.vBulletin.org and have at it!

            Comment

            • Knightmane
              Member
              • Mar 2007
              • 35
              • 4.2.X

              #7
              Back... *sigh* I was really hoping it wasn't going to be that.

              Disabling DragonByte Tech: vBShout (Lite) restored the board.

              Without a shoutbox we are as good as dead. Now what do we do? The members are demanding live chat.

              EDIT:

              I spoke too soon... now no new posts can be made at all. I am getting frustrated with this.

              And no, Michael, they never mentioned whether they did or not.
              Last edited by Knightmane; Tue 19 Mar '13, 1:26pm.

              Comment


              • liamwli
                liamwli commented
                Editing a comment
                You should check the php version using the phpinfo option in the acp, what is it?
            • Knightmane
              Member
              • Mar 2007
              • 35
              • 4.2.X

              #8
              Looks like the php version is 5.4.6-1ubuntu1.2

              Comment

              • Zachery
                Former vBulletin Support
                • Jul 2002
                • 59097

                #9
                You should downgrade to PHP 5.3 at this time.

                Comment

                • Knightmane
                  Member
                  • Mar 2007
                  • 35
                  • 4.2.X

                  #10
                  I'll let them know to do that. They are still checking out the PHP installation one more time. Thanks for the message.

                  Comment

                  • Knightmane
                    Member
                    • Mar 2007
                    • 35
                    • 4.2.X

                    #11
                    The staff at Rackspace have emailed me the following message:

                    "We have completely uninstalled and reinstalled PHP and downgraded to PHP 5.3.10."

                    The results?

                    The forum is still completely inaccessible. Not even the config.php trick used earlier is working now. I absolutely cannot get back into the board at all.

                    Any further suggestions?

                    On a side note, I tried to install a phpbb3 board on my account on the server and that board is working perfectly. But it doesn't have our vbulletin threads and posts, so it's not very useful.

                    Comment

                    • Zachery
                      Former vBulletin Support
                      • Jul 2002
                      • 59097

                      #12
                      What is the specific errors you're getting now?

                      Comment

                      • Knightmane
                        Member
                        • Mar 2007
                        • 35
                        • 4.2.X

                        #13
                        Now it's posting the very first errors as seen on post #1 of this thread all over again.

                        PHP Parse
                        error: syntax error, unexpected 'foreach' (T_FOREACH) in
                        /srv/www/ravibrencreations.net/public_html/forum/includes/class_core.php
                        on line 3920

                        Again there is NOTHING on line 3920; I checked. I even uploaded a fresh class_corp.php from the zip file to be sure and the same errors persist.

                        Comment

                        • Trevor Hannant
                          vBulletin Support
                          • Aug 2002
                          • 24358
                          • 5.7.X

                          #14
                          After re-uploading the files, did you disable all modifications again - do you still get the same error?
                          Vote for:

                          - Admin Settable Paid Subscription Reminder Timeframe (vB6)
                          - Add Admin ability to auto-subscribe users to specific channel(s) (vB6)

                          Comment

                          • Knightmane
                            Member
                            • Mar 2007
                            • 35
                            • 4.2.X

                            #15
                            I have the Vbulletin installation at the bottom most bare-bones "no-plugins-installed" default and the problems still persist.

                            The official followup word from the Rackspace staff is this: "We're at a bit of a loss here - we've been doing phpbb upgrades on the other sites and not one glitch - all the other sites are working fine - it is literally *just* your forum."

                            I was able to get my board viewable once again but the same problems are still present. Perhaps if I set up a guest Admin account for one of you Vbulletin Support guys, you might come in and see what can be done yourselves?

                            My board is here: http://www.ravibrencreations.net/forum/forum.php

                            Comment

                            widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
                            Working...