preg_match(): No ending matching delimiter ‘>’ found

  • Resolved Marty

    (@bozzmedia)


    8 months, 3 weeks ago

    We are getting a lot of this error in the logs, specifically on tag archive pages.

    trace:

    in preg_match called at /home/redacted/public_html/production/wp-content/plugins/autoptimize/classes/autoptimizeUtils.php (337)
 in autoptimizeUtils::str_is_valid_regex called at /home/redacted/public_html/production/wp-content/plugins/autoptimize/classes/autoptimizeBase.php (587)
 in autoptimizeBase::replace_contents_with_marker_if_exists called at /home/redacted/public_html/production/wp-content/plugins/autoptimize/classes/autoptimizeBase.php (285)
 in autoptimizeBase::hide_comments called at /home/redacted/public_html/production/wp-content/plugins/autoptimize/classes/autoptimizeStyles.php (331)
 in autoptimizeStyles::read called at /home/redacted/public_html/production/wp-content/plugins/autoptimize/classes/autoptimizeMain.php (591)
 in autoptimizeMain::end_buffering called at ? (?)

    Not sure if this is a concern but wanted to report it.

    Thanks!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    thanks for the heads-up Marty. could you share the URL of such an archive page where this happens so I can check if anything in there could trigger this?

    frank

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    @bozzmedia any news on this, could you indeed share a URL?

    Thread Starter Marty

    (@bozzmedia)

    My apologies, I had written a full reply and forgot to post it!

    Here’s is an example:
    https://www.temporary-url.com/72CF

    As is the same root domain at /purge (I believe this is Nginx Page Helper cache clearing but I could be mistaken)

    Thanks!

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    OK, the issue seems to be with some of the <!--noptimize--><!--/noptimize--> where in 4 of the 11 cases the closing <!--/noptimize--> is <!--\/noptimize--> instead (due to it being escaped because inside inline JS). Blocks of inline JS should be entirely noptimized, you cannot exclude certain parts of one and the same JS blocks.

    hope this helps,
    frank

    Thread Starter Marty

    (@bozzmedia)

    Super helpful, thank you frank!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘preg_match(): No ending matching delimiter ‘>’ found’ is closed to new replies.