Support » Plugin: bbPress Messages » After update site to PHP 7.3 the plugin stopped working

  • Hello. After update site to PHP 7.3 the plugin stopped working and send me a PHP error.

    mod_fcgid: stderr: PHP Warning: preg_match(): Compilation failed: escape sequence is invalid in character class at offset 21 in /hosting/www/racingonlineclub.com/public/wp-content/plugins/bbp-messages/Inc/Core/Init.php on line 329

    mod_fcgid: stderr: PHP Warning: preg_match(): Compilation failed: escape sequence is invalid in character class at offset 21 in /hosting/www/racingonlineclub.com/public/wp-content/plugins/bbp-messages/Inc/Core/Init.php on line 166

    Any idea how I can fix it? Thank you.

    • This topic was modified 4 months, 3 weeks ago by J.Parra.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hello @jparra-1 ,

    I have the same issue, but I’m afraid all PHP 7.3 users are having this issue.
    Unfortunately this plugin seems long abandoned, all issues from the last two years are still open.

    In the event the developer sees this: you should take a look at this page.

    PHP 7.3 introduced a new version of the PCRE2 library, which introduces incompatible changes to the way regular expressions are interpreted b PHP. The plugin might have some invalid regex(s) that were compatible with PCRE but not with PCRE2.

    Should be an easy fix, please don’t let this die off. 🙂
    Thanks in advance!
    A.G.

    Thanks alegrigis for your answer. The truth is that something like that I feared, pity because it worked perfect for my goals, simple and simple.
    But I have been investigating alternatives and after ruling out some, we are currently testing “Front End PM” that seems to give us the desired service.

    Waiting for this plugin to resurface, greetings

    I think I found a bodge to fix it temporarily.

    Just browse to this file:
    /wp-content/plugins/bbp-messages/Inc/Core/Init.php
    and change all occurrences of \z with $.

    I give no warranties about this fix, so use at your own risk. 🙂

    Regards,
    A.G.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.