Announcement

Collapse
No announcement yet.

Upgrade Issue: vBulletin 4.2.3 patch 1 to vBulletin 4.2.3 patch

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

  • Upgrade Issue: vBulletin 4.2.3 patch 1 to vBulletin 4.2.3 patch

    “ Hi! During upgrade from vBulletin 4.2.3 patch 1 to vBulletin 4.2.3 patch 2 i am getting the following error
    Unexpected Text:
    <?xml version="1.0" encoding="windows-1252"?>
    <upgrade>
    <message replace="0">Skipping step, not needed</message>
    <status>Status: Processing Blog, Step 4 of 18</status>
    <longversion>vbblog</longversion>
    <version>vbblog</version>
    <nextstep>4</nextstep>
    <upgradenotice><![CDATA[<strong>Processing Blog</strong>]]></upgradenotice>
    </upgrade>

    Can i know what is the problem and how can I fix it”.

    I actually started upgrading since my CMS URLs stopped working..
    Last edited by msinus; Wed 31 Aug '16, 12:19am.

  • #2
    my config.php had this:

    <?php

    ini_set("display_errors", true);
    ini_set('memory_limit', -1);
    ini_set("max_execution_time", "2880");

    Comment


    • #3
      The same problem. screenshot of vBulletin upgrade http://prntscr.com/ccfc41
      We changed the mysql parameter
      MySQL Packet Size 256.00 MB

      Comment


      • #4
        I notice it's moved along. Try refreshing it each time it stops, you may find it's actually progressing.

        Also, remove the display errors line from config.php. It's possibly displaying php warnings that don't cause any issues, but their display will stop the script.
        MARK.B
        vBulletin Support

        Comment


        • #5
          Thank you Mark.
          I have rmeoved display errors line from config.php
          Still the same.

          Upgrading to 4.2.3
          Status: Aborted

          Comment


          • #6
            Unexpected Text:
            <?xml version="1.0" encoding="windows-1252"?> <upgrade> <message replace="0">Skipping step, not needed</message> <status>Status: Processing CMS, Step 16 of 33</status> <longversion>vbcms</longversion> <version>vbcms</version> <nextstep>16</nextstep> <upgradenotice

            Comment


            • #7
              You have BOM (Byte-Order-Mark) characters at the beginning of your config.php.
              You can use the editor Notepad++ to remove these characters and/or change the encoding of the file.
              this is my sig

              Comment


              • #8
                Thank you Pogo. It worked.
                Changed the config.php file encoding using notepadd++

                Comment

                Related Topics

                Collapse

                Working...
                X