slapbox

“Your best bet is to investigate the underlying PHP errors that get triggered during the cache purging”

@johnbillion thanks for your great work! Unfortunately there is no underlying PHP error when this occurs – I have checked the logs very carefully. There is only the Nginx error. Unless you mean that a simple deprecation message is an error in this context?

Still doesn’t work on PHP8.1 (errors out, not just deprecation notices,) though it’s not clear why. There’s no error message I can find anywhere.

Edit: It’s actually caused by QueryMonitor: https://github.com/rtCamp/nginx-helper/issues/255

• This reply was modified 1 year, 10 months ago by slapbox.
• This reply was modified 1 year, 10 months ago by slapbox.

(I apologize for the formatting, I can’t seem to make it work with me)

I looked at the differences between the latest and the vulnerable version prior and I assume the line we need to add is this one?

// Limit to only alphanumeric characters, including unicode and spaces.
$new_search = preg_replace( '/[^\pL^\pN\pZ]/', ' ', $new_search );

So in 2.10.x it would look something like this?

function edd_ajax_download_search() {
    global $wpdb;

    $search   = esc_sql( sanitize_text_field( $_GET['s'] ) );


    // Limit to only alphanumeric characters, including unicode and spaces.
    $search = preg_replace( '/[^\pL^\pN\pZ]/', ' ', $search );

• This reply was modified 1 year, 10 months ago by slapbox.

Thanks for your reply @dpinson. Interestingly everything seems to work properly today when I re-enabled PHP 8.1 to test this. If I run into any more trouble, I’ll update this issue.

Thanks again.

I think it’s not. I haven’t received any reply from them for a month now. Unfortunate.

Is this plugin still supported? I’m guessing not.

Thanks so much for the tip!

Friendly bump! I know it hasn’t been long, but I see topics haven’t been replied to in the past one month or so – is there a more preferred venue for these questions/discussions?

Thanks for reading!

Any update on this?

For anyone facing this in the future – even if you have a crontab job to trigger wp-cron.php on the staging site – it seems like the first invocation must be from manually triggering it in the browser. Before that, our crontab job didn’t get the WP cron jobs to run, but after manually triggering wp-cron.php once, it seems to run as expected afterward.

I wonder if this behavior is unexpected @renehermi?

Thanks again very much for the great plugin!

Any comment from the dev team about the intended behavior?

Turns out the cron jobs just needed more time to process because of a backlog.

Nope, jobs really don’t run! I don’t know what it could be!

And it turns out this is all wrong and user error, as usually is the case; so ignore this issue. Thank you again!

• This reply was modified 2 years, 4 months ago by slapbox.