Uploaded image for project: 'phpBB'
  1. phpBB
  2. PHPBB-10876

Xampp crashes on Develop when template has too many ORs in an IF statement

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • 3.1.0-a1
    • 3.1.0-dev
    • Template Engine
    • None
    • Tested on:
      Xampplite 1.7.7 on Windows 7 x86 SP1
      Xampplite 1.7.7 on Windows 7 x64 SP1

      Xampplite 1.7.7 includes:
      Apache 2.2.21, MySQL 5.5.16, PHP 5.3.8, phpMyAdmin 3.4.5, OpenSSL 1.0.0e

      I found a strange problem with the new template engine when your server is xampp.

      Steps to reproduce:

      1. Download xampp (or xampplite/USB) to your windows computer: http://www.apachefriends.org/de/xampp-windows.html#631
      2. Install phpBB from current develop branch on github: https://github.com/phpbb/phpbb3/downloads
      3. In viewtopic_body.html duplicate the ORs in the template IF by replace

        <!-- IF postrow.U_PM or postrow.U_EMAIL or postrow.U_WWW or postrow.U_MSN or postrow.U_ICQ or postrow.U_YIM or postrow.U_AIM or postrow.U_JABBER -->

        with

        <!-- IF postrow.U_PM or postrow.U_EMAIL or postrow.U_WWW or postrow.U_MSN or postrow.U_ICQ or postrow.U_YIM or postrow.U_AIM or postrow.U_JABBER or postrow.U_EMAIL or postrow.U_WWW or postrow.U_MSN or postrow.U_ICQ or postrow.U_YIM or postrow.U_AIM or postrow.U_JABBER -->

      4. Visit the viewtopic.php

      As a result your xampp crashes. (After investigation I found out, that it crashes after 8 ORs or more)

      NOTE: If you use the same modification (Step 3.) on develop-olympus it displayes the page just fine, which is the reason why I am reporting this!

        1. 3.1_vs_3.0_regex.diff
          7 kB
        2. cache files.zip
          22 kB
        3. compare30to31.diff
          74 kB
        4. test.diff
          12 kB

            nickvergessen Joas Schilling
            nickvergessen Joas Schilling
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: