Skip to:
Content

BuddyPress.org

Changes between Initial Version and Version 1 of Ticket #9221, comment 7


Ignore:
Timestamp:
07/31/2024 11:26:23 AM (2 years ago)
Author:
emaralive

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #9221, comment 7

    initial v1  
    1212However, when I utilize either "**wp shell**" or "**psy shell**" (WP CLI) and run the offending line (original 164) this triggers the errors (PHP 7.4.33 & 8.0.30), which I did first without having to load up a website via a web browser, thus confirming there was an issue. Otherwise, I would have discovered this bug much earlier, like during the testing of various BP 12.0.0 releases; or, at least, I would think this would have been the case.
    1313
    14 If this is behavior for some (what I'm experiencing [linux debian based situation]) and not for others, does that explain a reason why this has not been detected since the release of BP 12.0.0? Or, it has occurred and nobody bothered to report it or what?. Perhaps, the sites that are using the **legacy** template haven't upgraded to greater than or equal to BP 12. Or, they have upgraded and no user has used **!@mention**. I know of a site that uses the **legacy** template and I've used **!@mention** and nobody has reported an issue for this situation nor have I experienced this issue on this site, I believe the site admin has not upgraded BP past 12 and could still be at the original BP version when the site was created (around 2019).
     14If this is behavior for some (what I'm experiencing [linux debian based situation]) and not for others, does that explain a reason why this has not been detected since the release of BP 12.0.0? Or, it has occurred and nobody bothered to report it or what?. Perhaps, the sites that are using the **legacy** template haven't upgraded to greater than or equal to BP 12. Or, they have upgraded and no user has used **@mention**. I know of a site that uses the **legacy** template and I've used **@mention** and nobody has reported an issue for this situation nor have I experienced this issue on this site, I believe the site admin has not upgraded BP past 12 and could still be at the original BP version when the site was created (around 2019).
    1515
    16 Moving along, I just tested on my other server (linux centos based) and I get the error on one of the sites after I switched the template pack to legacy, after posting **!@mention** and refreshing the sitewide activity page. I then:
     16Moving along, I just tested on my other server (linux centos based) and I get the error on one of the sites after I switched the template pack to legacy, after posting **@mention** and refreshing the sitewide activity page. I then:
    1717
    1818* Rolled back to 11.4.2 - issue does not exist