Board Blew Up

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • uncle fuzzy
    New Member
    • Oct 2016
    • 13
    • 5.2.x

    Board Blew Up

    Somehow my Board blew up. When I go to the Board, I get a screen like that shown below. Logging on as Administrator doesn't help. There seems to be no way to get back into the admin panel to fix things. I notice that the website is shown as my street address, so something seems to be amiss there. Running 5.2.3.

    Any ideas?
  • Wayne Luke
    vBulletin Technical Support Lead
    • Aug 2000
    • 73976

    #2
    Your .htaccess file is not working. If it was working before, then you need to contact your hosting provider. If you just upgraded, you did not rename the htaccess.txt file to .htaccess

    Only thing I can guess on the address is that a form was improperly filled in using your browser's Autofill functionality.

    You should upgrade the site to 5.4.0 as well. 5.2.3 is out of date.
    Translations provided by Google.

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

    Comment

    • uncle fuzzy
      New Member
      • Oct 2016
      • 13
      • 5.2.x

      #3
      The site worked fine until I tried to change something in the settings. When I saved the settings, it blew up.

      There is indeed an htaccess.txt file but it is for another part of the website; it is used by Joomla. I don't seem to have a .htaccess for vbulletin. Would it be in the vbulletin directory? I there a way to create a proper version?

      Comment

      • uncle fuzzy
        New Member
        • Oct 2016
        • 13
        • 5.2.x

        #4
        Forgot about ls -a. There is a .htaccess file in the vbulletin directory. Contents are:
        <IfModule mod_rewrite.c>

        RewriteEngine On




        # In some cases where you have other mod_rewrite rules, you may need to remove the

        # comment on the following RewriteBase line and change it to match your folder name.

        # This resets the other mod_rewrite rules for just this directory

        # If your site was www.example.com/forum, the setting would be /forum/

        #RewriteBase /




        # Send css calls directly to the correct file VBV-7807

        RewriteRule ^css.php$ core/css.php [NC,L]




        # Redirect old install path to core.

        RewriteRule ^install/ core/install/ [NC,L]




        # Main Redirect

        RewriteCond %{REQUEST_URI} !\.(gif|jpg|jpeg|png|css)$

        RewriteCond %{REQUEST_FILENAME} !-f

        RewriteCond %{REQUEST_FILENAME} !-d

        RewriteRule ^(.*)$ index.php?routestring=$1 [L,QSA]




        # Because admincp is an actual directory.

        RewriteRule ^(admincp/)$ index.php?routestring=$1 [L,QSA]




        </IfModule>




        <IfModule mod_deflate.c>

        AddOutputFilterByType DEFLATE application/atom+xml \

        text/javascript \

        application/x-javascript \

        application/javascript \

        application/json \

        application/rss+xml \

        application/vnd.ms-fontobject \

        application/x-font-ttf \

        application/xhtml+xml \

        application/xml \

        font/opentype \

        image/svg+xml \

        image/x-icon \

        text/css \

        text/html \

        text/plain \

        text/x-component \

        text/xml

        </IfModule>




        <IfModule mod_expires.c>

        ExpiresActive On

        ExpiresByType application/x-javascript A1209600

        ExpiresByType text/javascript A1209600

        ExpiresByType application/javascript A1209600

        ExpiresByType text/css A31536000

        ExpiresByType image/x-icon A2592000

        ExpiresByType image/icon A2592000

        ExpiresByType application/x-ico A2592000

        ExpiresByType application/ico A2592000

        ExpiresByType image/gif A2592000

        ExpiresByType image/jpeg A1209600

        ExpiresByType image/jpg A1209600

        ExpiresByType image/png A1209600

        ExpiresByType application/x-shockwave-flash A1209600

        ExpiresByType font/ttf A2592000

        ExpiresByType font/otf A2592000

        ExpiresByType font/x-woff A2592000

        ExpiresByType image/svg+xml A2592000

        ExpiresByType font/truetype A2592000

        ExpiresByType font/opentype A2592000

        ExpiresByType application/x-font-woff A2592000

        ExpiresByType application/vnd.ms-fontobject A2592000

        </IfModule>




        <IfModule mod_headers.c>

        Header set Connection keep-alive

        <filesmatch "\.(ico|flv|gif|swf|eot|woff|otf|ttf|svg)$">

        Header set Cache-Control "max-age=2592000, public"

        </filesmatch>

        <filesmatch "\.(jpg|jpeg|png)$">

        Header set Cache-Control "max-age=1209600, public"

        </filesmatch>

        <filesmatch "\.(eot|woff|otf|ttf|svg)$">

        Header set Cache-Control "max-age=2592000, public"

        </filesmatch>

        # css and js should use private for proxy caching https://developers.google.com/speed/...geProxyCaching

        <filesmatch "\.(css)$">

        Header set Cache-Control "max-age=31536000, private"

        </filesmatch>

        <filesmatch "\.(js)$">

        Header set Cache-Control "max-age=1209600, private"

        </filesmatch>

        </IfModule>

        Comment

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

          #5
          If you changed a setting and it blew up, then the URL entered into settings is probably what you changed and inaccessible for some reason.

          To change your URL, you will need to follow these steps:
          1. Upload upload/core/install to your server.
          2. Upload do_not_upload/tools.php to your server. Place this in the /core/admincp directory.
          3. Load tools.php in your browser by going to your_vbulletin/admincp/tools.php
          4. There will be a tool on that page that allows you to update your URL.
          5. When your site works properly, delete /core/install and /core/admincp/tools.php from your server.

          If your vBulletin is installed in an sub-directory under JOOMLA, you need to uncomment this line in your .htaccess file:
          Code:
          #RewriteBase /
          Do this by removing the #. You will also need to replace the / with the path to your forums as specified in the instructions above this line.
          Translations provided by Google.

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

          Comment

          • uncle fuzzy
            New Member
            • Oct 2016
            • 13
            • 5.2.x

            #6
            vbulletin is a subdirectory, but not under Joomla. vbulletin and joomla run in separate worlds (supposedly . . ) within the same root directory. The two should not be interacting, although they share the same mysql database.

            I assume the uploads go into the vbulletin subdirectory under the website's root directory.

            I have been running 5.2.3. Does it make sense to upgrade to 5.4.0 as a part of this process? Or should I get back to a stable 5.2.3 before doing the upgrade?

            If I do this reinstall, will I need to update all my vbulletin settings? Will the existing threads/posts/registrations be unaffected?

            Comment

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

              #7
              .htaccess files are not a vBulletin or a Joomla thing. They are Apache control files and subdirectories will inherit directives from .htaccess files in their parents. vBulletin doesn't interact with Joomla. The directories I listed are vBulletin directories. I know nothing about Joomla and it is irrelevant to the operation of vBulletin.

              I didn't say anything about a "Reinstall". If you do a reinstall, you will lose all data. That is the very essence of an installation. You shouldn't be running any scripts in the installation directory. It is only needed because it contains files for tools.php to work properly. The steps I listed are very explicit and should be followed without deviation.

              Once the site is online, then you can upgrade to 5.4.0. Simply upgrading will not resolve your current problems and could make things worse.
              Translations provided by Google.

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

              Comment

              • uncle fuzzy
                New Member
                • Oct 2016
                • 13
                • 5.2.x

                #8
                Sorry for the confusion. I misspoke about "reinstall".

                Where do I find upload/core/install? vbulletin did my original install, so I don't have any of the files nor do I see them in the Members Area.

                Comment

                • uncle fuzzy
                  New Member
                  • Oct 2016
                  • 13
                  • 5.2.x

                  #9
                  1. I downloaded the 5.2.0 files from the Member Area. I assume those are the correct files since 5.2.3 is patches.
                  2. I uploaded the upload/core/install folder into vbulletin/core
                  3. I uploaded do_not_upload/tools.php into the core/admincp directory
                  4. I went to vbulletin/admincp/tools.php, as directed in your post, and got the mess I've been getting.

                  5. Thinking there might be a typo in the instructions, I tried vbulletin/core/admincp/tools.php in the browser (since that is where I was told to place tools.php). I got a server error:
                  "The server encountered an internal error or misconfiguration and was unable to complete your request.

                  Please contact the server administrator at [email protected] to inform them of the time this error occurred, and the actions you performed just before this error.

                  More information about this error may be available in the server error log.

                  Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request."

                  6. I checked permissions on tools.php. They were 775, so I assume that's not an issue.

                  Any ideas?

                  Comment

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

                    #10
                    Actually, 5.2.3 isn't a patch but a full release. You should have already had the files from your original download.

                    You need to download vBulletin 5.2.3 if you're running vBulletin 5.2.3. Do not mix versions. You can download this by clicking More Download options on the download screen. Select vBulletin 5.2.3 from the drop-down menu.

                    Please purchase a Support Contract and open a support ticket so we can fix your site.


                    Translations provided by Google.

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

                    Comment

                    • uncle fuzzy
                      New Member
                      • Oct 2016
                      • 13
                      • 5.2.x

                      #11
                      Got it. Board is working now. Have a support contract (ready for the next problem).

                      Thanks for the help.

                      Comment

                      • super-sonic
                        New Member
                        • Mar 2018
                        • 2
                        • 5.3.x

                        #12
                        how did you fix this issue ? i have the same problem many thanks in advance any help would be greatful

                        i have had this issue for sometime but it effect mostly devices and yet it displays fine in opera on devices wierd issue indeed

                        my website is here on this link if it helps http://www.volvoenthusiastsclub.org/forum/

                        Comment

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

                          #13
                          Originally posted by super-sonic
                          how did you fix this issue ? i have the same problem many thanks in advance any help would be greatful

                          i have had this issue for sometime but it effect mostly devices and yet it displays fine in opera on devices wierd issue indeed

                          my website is here on this link if it helps http://www.volvoenthusiastsclub.org/forum/
                          Something on the server is blocking the CSS from being loaded on Mobile Devices. Could be due the fact that you are not using SSL for your site.

                          Translations provided by Google.

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

                          Comment

                          • super-sonic
                            New Member
                            • Mar 2018
                            • 2
                            • 5.3.x

                            #14
                            Originally posted by Wayne Luke

                            Something on the server is blocking the CSS from being loaded on Mobile Devices. Could be due the fact that you are not using SSL for your site.
                            it does it on https aswell i have tested on both

                            Comment

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

                              #15
                              Then you will need to talk to your hosting provider and ask why they are blocking access to css.php on mobile devices. The site behaves the same on mobile and desktop devices. We just use CSS to redraw the page based on your device's screen resolution.
                              Translations provided by Google.

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

                              Comment

                              Related Topics

                              Collapse

                              Working...