itnmario

It happened on our websites also, after upgrading to WC 7.6.0.

In our case, there was an issue with the existing Antispam plugin. Try to deactivate your antispam plugin and see if the issue goes away.

In that case I would recommend to install a different antispam plugin. You should not leave your website without.

Good luck!

Hi @markwaregr,

thank you for your prompt reply.

I suspected this, the same problem has affected other plugins, but I thought the community needed to know.

A plugin removal triggers vulnerability warnings from security plugins and it is right that everyone has the appropriate elements to evaluate whether to keep a plugin or remove it based on the removal reason.

I will definitely keep your plugin installed and wait for the new version.

Good luck with your upgrade!

Hi,
I have just found the solution for this. In the “Query type” option tool tip is indicated to use “Product only” when filtering categories and including variations.

Using this setting solved my problem. I don’t remember to have changed anything, is it possible that this is a new behaviour after an updgrade?

Just publishing this note in case it could help others.

Regards

Hello @sweets2017,

check if in Shipping > Shipping Options, Debug mode is enabled.

Shipping debug mode shows matching shipping zones and should act exactly as you described.

Let me know if this helps.

Thank you Jim, exactly what I was looking for.

Dequeuing pods-select2 scripts on tribe events admins pages solve the problem.

Anyone interested can follow the link provided by Jim.

Hi, would you please confirm that this feature is available in your premium plugin working in the same way?

Please write an example code or provide a link to your documentation. I would like to see if it fits my requirements. In this case I would be happy to buy your premium version.

Ciao

Are you now using objects instead arrays to pass meta caps?

No… (I checked myself…. ?? )

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

I developed it… it is one custom theme for one client…

I have got the same issue…. I am also using WPML with CF7

Hi @takayukister and thanks for your answer!

I have found the problem. The theme was using a filter to permit the authors to access flamingo.

remove_filter( 'map_meta_cap', 'flamingo_map_meta_cap' );
add_filter( 'map_meta_cap', 'mycustom_flamingo_map_meta_cap', 9, 4 );

function mycustom_flamingo_map_meta_cap( $caps, $cap, $user_id, $args ) {
    $meta_caps = array(
        'flamingo_edit_contacts' => 'publish_posts',
        'flamingo_edit_contact' => 'publish_posts',
        'flamingo_delete_contact' => 'publish_posts',
        'flamingo_edit_inbound_messages' => 'publish_posts',
        'flamingo_delete_inbound_message' => 'publish_posts',
        'flamingo_delete_inbound_messages' => 'publish_posts',
        'flamingo_spam_inbound_message' => 'publish_posts',
        'flamingo_unspam_inbound_message' => 'publish_posts' );

    $caps = array_diff( $caps, array_keys( $meta_caps ) );

    if ( isset( $meta_caps[$cap] ) )
        $caps[] = $meta_caps[$cap];

    return $caps;
}

I suppose the new version break the compability to this script. I would really appreciate your help to achive the same goal with the 1.6 version of Flamingo.

Thank You!

Shame on me!!! I really missed this one… sorry

It is all clear now… Thank you very much for the link…

Same problem… CF7 version 4.3 and Really Simple CAPTCHA version 1.8.0.1.

Tried on several WordPress installation and on a clean installation I have just made for debug purpose.

The button is not showing up in the form tag generator toolbar.

Any info?

I am getting the same fatal error when using the widget as shortcode in a page.

The widget works if you put the same shortcode in a post (as mentioned earlier by other members).

I did not try badke’s fix since my work-around was to change the sign-up link to point to a new post with the sign up widget.

I hope this may help someone while still waiting for an update by the developer.

Hi,

unfurtunately the widget saves the new fields [before] and [after] using the function wp_filter_post_kses making the use of double quotes impossible.

Waiting for the official fix, if you are familiar with PHP, you can edit the Update method of the Recent_Posts_Widget_Extended Class in wp-content\plugins\recent-posts-widget-extended\classes\widget.php (line 126 and 127) to skip the use of the filter:

change

$instance['before'] = wp_filter_post_kses( $new_instance['before'] );
$instance['after'] = wp_filter_post_kses($new_instance['after'] );

to

$instance['before'] = $new_instance['before'] ;
$instance['after']  = $new_instance['after'] ;

For security reason you can also filter the fields with a proper different filter function.

Let me know if it works for you….