1. Home
  2. AccessAlly
  3. Testing & Troubleshooting
  4. AccessAlly PHP bug 75148 Workaround

AccessAlly PHP bug 75148 Workaround

There is a known issue that affects all post list displays, which includes BeaverBuilder “Posts” and regular WordPress blog pages. The bug report can be found here: https://bugs.php.net/bug.php?id=75148

In particular, the PHP bug affects the function of the WordPress “found_posts” filter. When called, the following warning is given:

Warning: Parameter 2 to test_call() expected to be a reference, value given


In AccessAlly 2.2.9, we have added an option in AccessAlly General Settings → Initial Setup → Additional Features → (Advanced) Always enable “found_posts” filter.

This option is only shown if the server is running PHP 7.1 or higher, which are the only versions that are affected by the PHP bug.

We recommend NOT enabling the option unless you need the post-filtering feature.

IMPORTANT: Once enabled, please check the front end to make sure the warning message is NOT shown. The warning might look similar to the following (Parameter 2 to AccessAlly::filter_post_list() expected to be a reference):

If it is, please contact server host to disable verbose error reporting.

Alternative Solution To Hide Warning

If the server host is not able to configure the PHP to hide the warning, you can install the “Turn error off” plugin to hide the warnings.

Updated on October 26, 2020

Was this article helpful?

Related Articles


If you have any questions, we're just an email away.

We take your success seriously, and you'll always get a speedy reply from a real person during business hours.


AccessAlly is the #1 WordPress Course and Membership Solution for Industry Leaders


You'll get follow-up emails about AccessAlly and new features. Opt out anytime. Full privacy policy here.