Announcement

Collapse
No announcement yet.

VBulletin 4.1.0 and PCRE 8.21 : bug

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

  • [Forum] VBulletin 4.1.0 and PCRE 8.21 : bug

    Hello,

    I have just upgraded PCRE on my server to the 8.21 version and it caused bug on my forum.
    My Vbulletin is 4.1.0.
    When a message is entered, the following message comes and the message is empty :
    "Warning :Preg_replace()[function.preg-replace] :Compilation failed : internal error :unknow opcode in find_fixedlength() at offset 193 in [path]/includes/functions_newpost.php on line 279"

    When coming back to PCRE 8.20, it works.

    Is it a known bug?

    Thanks

    David

  • #2
    Please upgrade to 4.1.9... Does the problem still exist?
    Translations provided by Google.

    Wayne Luke
    The Rabid Badger - a vBulletin Cloud demonstration site.
    vBulletin 5 API - Full / Mobile
    Vote for your favorite feature requests and the bugs you want to see fixed.

    Comment


    • #3
      Hi,

      Unfortunately I plan to migrate to VB4.1.9 in next months.
      I have to do non regression tests, correct templates...

      Did you ever heard about such issues?

      REgards

      David

      Comment


      • #4
        Originally posted by XLD_Bull View Post
        Hi,

        Unfortunately I plan to migrate to VB4.1.9 in next months.
        I have to do non regression tests, correct templates...

        Did you ever heard about such issues?

        REgards

        David
        Only in older versions of the software. Unfortunately, I can't provide a fix at this time except to either downgrade PCRE or upgrade.
        Translations provided by Google.

        Wayne Luke
        The Rabid Badger - a vBulletin Cloud demonstration site.
        vBulletin 5 API - Full / Mobile
        Vote for your favorite feature requests and the bugs you want to see fixed.

        Comment


        • #5
          Hi,

          I have migrated to VB4.1.9 yesterday and tried to upgrade PCRE to 8.21.
          I have the same issue than with VB4.1.0

          An idea to fix the issue?

          Thanks

          David

          Comment


          • #6
            Issue appears to be a bug in PCRE 8.21. I recommend downgrading to 8.20 until they get it fixed.

            http://bugs.exim.org/show_bug.cgi?id=1187
            Translations provided by Google.

            Wayne Luke
            The Rabid Badger - a vBulletin Cloud demonstration site.
            vBulletin 5 API - Full / Mobile
            Vote for your favorite feature requests and the bugs you want to see fixed.

            Comment


            • #7
              Help

              same problem of empty post, my provider not downgrade PCRE 8.21

              URGENT PATCH REQUESTED !

              Comment


              • #8
                This is not a vbulletin bug, it is a PCRE bug. The only fix is to downgrade your PCRE to 8.20 for now.

                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


                • #9
                  Same problem here, I upgrade to latest version of vB 4.1.9 and still continue with the problem.

                  When the users create new post, reply or private message appear in blank with the error msg.

                  My host provider of course is not going to downgrade his host.

                  Please fix the problem!!!!!! The board is not working well!!!!!

                  Regards.

                  Comment


                  • #10
                    The problem at this time is a bug in the library, not vBulletin.

                    Comment


                    • #11
                      Probably its PCRE fault, but the Developers has to be helped in order to find a solution, when all users will be upgraded to the new edition. This has to be done, because the program provider will be tagged with tickets.

                      Comment


                      • #12
                        I would imagine that given the error message, it was this change [as listed in their 8.21 changelog] that is causing the problem.

                        Warning :Preg_replace()[function.preg-replace] :
                        Compilation failed : internal error :unknow opcode in find_fixedlength() at offset 193 in [path]/includes/functions_newpost.php on line 279


                        ChangeLog for PCRE
                        ------------------

                        Version 8.21 12-Dec-2011
                        ------------------------
                        .
                        .

                        7. While fixing 6 above, I noticed that a number of other items were being
                        incorrectly rejected as "not fixed length". This arose partly because newer
                        opcodes had not been added to the fixed-length checking code. I have (a)
                        corrected the bug and added tests for these items, and (b) arranged for an
                        error to occur if an unknown opcode is encountered while checking for fixed
                        length instead of just assuming "not fixed length"
                        . The items that were
                        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
                        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
                        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
                        Baby, I was born this way

                        Comment


                        • #13
                          Hi all,

                          for now I made this changes quiting the autocheck of parseurl

                          <label for="cb_parseurl"><input type="checkbox" name="parseurl" value="0" id="cb_parseurl" tabindex="1" {vb:raw checked.parseurl} /> {vb:rawphrase automatically_parse_links_in_text}</label>

                          with

                          <label for="cb_parseurl"><input type="checkbox" name="parseurl" value="0" id="cb_parseurl" tabindex="1" /> {vb:rawphrase automatically_parse_links_in_text}</label>

                          I made this change in:
                          edit post

                          New Posting Plantillas:
                          newpoll
                          newreply
                          newthread

                          Private Message Plantillas
                          pm_newpm

                          Thread Administration_Plantillas
                          threadadmin_easyspam_infraction

                          Visitor Message Plantillas
                          visitormessage_editor

                          Now at least the post are not in blank but the signatures don't work. But its better than a lot of blank post in the forum.

                          Please notify in this post when some change happens in PCRE or in vBulletin for put the code as normal.

                          Regards!

                          Comment


                          • #14
                            Same problem exists with PCRE 8.21 and VBulletin 3.8.x.
                            Greetings, Black Tiger

                            Comment


                            • #15
                              Originally posted by Black Tiger View Post
                              Same problem exists with PCRE 8.21 and VBulletin 3.8.x.
                              As I mentioned in a post somewhere - that code (in vb) is basically the same in all 3.x versions (right back to 3.0.0).

                              Indeed it may well be in vb2 as well, I didnt check.
                              Baby, I was born this way

                              Comment

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