fiskhandlarn

rather than having us adding custom code, is it possible what wordfence could remedy this by adding something like did_action('plugins_loaded') before trying to use stuff not yet ready in the wp_redirect_status filter? https://github.com/Yoast/wordpress-seo/issues/16918#issuecomment-832643112

I added this in wp-config.php:

define( 'automatic_updater_disabled', true );

I haven’t checked if the issue in this thread has since been fixed in a new version.

Thanks for the thorough and quick answer! I now understand that there are more complications for changing this behaviour than I first thought. I will try a migration helper plugin instead of my homebrewn regexp script.

• This reply was modified 6 years, 5 months ago by fiskhandlarn.

Right now, if I keep the value for social_image_fb_url intact in the database dump, the remote server will still output social_image_fb_url (with my local domain) as the og:image url instead of using the url derived (with wp_get_attachment_url for example) from social_image_fb_id. The only way to migrate and keep all settings and get the correct og:image is to change \"social_image_fb_url\";s:68 to another string length.

• This reply was modified 6 years, 5 months ago by fiskhandlarn.

Opened an issue on github instead: https://github.com/bugsnag/bugsnag-wordpress/issues/27

FYI, when I rewrite bugsnag.php with this as the first line in the constructor:

        add_action('init', array($this, 'activateBugsnag'));

and change activateBugsnag() to public, the error handlers are indeed disabled, but I get the same warning as above:

Warning: strpos(): Empty needle in plugins\bugsnag\bugsnag-php\Error.php on line 386

• This reply was modified 6 years, 7 months ago by fiskhandlarn.
• This reply was modified 6 years, 7 months ago by fiskhandlarn.

@mphilippe: do you have the same problem as me or @studiobovenkamer? because the answer by @pronl was for @studiobovenkamer’s issue.

Anyhow, here is my temporary fix for the original problem until the plugin is fixed:

if ( class_exists('ITSEC_WordPress_Tweaks') ) {
    add_action('init', function () {
        // better-wp-security tries to look for jquery in registered scripts
        // (which we've already removed in wp_enqueue_scripts),
        // disable that:
        remove_action( 'wp_print_scripts', array( ITSEC_WordPress_Tweaks::get_instance(), 'store_jquery_version' ) );
    });
}

• This reply was modified 7 years, 5 months ago by fiskhandlarn.

This seems to resolved as of 1.6.5.2. Or maybe it was an issue introduced by WooCommerce which has now also been updated. Anyhow, this issue can now be marked as solved. ??

• This reply was modified 7 years, 11 months ago by fiskhandlarn.

Sorry, this problem is in version 1.6.5.1, not 1.6.3 (which I read in readme.txt).

The problem seems to lie in RedirectsFrontEnd::parseRequest() always setting page_id:
$wp->query_vars['page_id'] = $page[0]->ID;

Fix works, thanks!

Same here, I changed line 40 in limit-post-titles.js from:
if(this.getLength() < 1){
to:
if(this.getLength() < 0){

(and made the corresponding change in limit-post-titles.min.js as well).

Same here, running WP 4.4.2. Regardless of WP version, the last parameter in the add_settings_section() calls should be a string, which they aren’t:

required-fields.php, line 74:
add_settings_section('rf_save_draft_section', 'Save Drafts', 'rf_save_draft_text', rf_save_draft_text);

I made these changes in plugin version 7 to stop the notices:
https://www.diffchecker.com/p6oltapz

The plugin seems to be working after the changes, but I haven’t tested all the features.

Fixed in the latest update, thank you!