Colir

In fact, i forget why i’m asking this…, all work as natural way…sorry & thank you

After investigating, i think the the simpler and cleaner solution would be to include the var “wpcf7” in an hidden field (with a hook filter) in the forms rather than a global window object with wp_localize_script.

In fact, the blocking element is in the “api-fetch.js”

const {
	root,
	namespace = 'contact-form-7/v1',
} = wpcf7.api;

It could be great if this doesn’t use the global object, or can be filtered.

Thank you

Wow! You are efficient!

Actually I had to remove the optimization for all the posts of a particular type.
I used the “autoptimize_filter_noptimize” filter to do this.

However, the new filter you have set up is very welcome

Thank you

For those who meet or will meet the concern,
here is a solution that is a little dirty, but works.

Put this in admin/class-inbound-messages-list-table.php in any column you want (i put this in the column_subject)

if( $item->channel == ''){
			$form_slug = $item->fields['form_name'];
			$form = get_post_by_slug($form_slug,'wpcf7_contact_form');
			$forn_name = $form->post_title;
			$channel_id = wpcf7_flamingo_add_channel($form_slug, $forn_name); // on crée le term
			$post_meta = get_post_meta( $form->ID,'_flamingo', true );
			
			if ( ! isset( $post_meta['channel'] )
			or $post_meta['channel'] !== $channel_id ) {
				$post_meta = empty( $post_meta ) ? array() : (array) $post_meta;
				$post_meta = array_merge( $post_meta, array(
					'channel' => $channel_id,
				) );

				update_post_meta( $form->ID, '_flamingo', $post_meta ); // asing correct erm id to Form
			}

			$channel = get_term( $post_meta['channel'], Flamingo_Inbound_Message::channel_taxonomy);

			if ( term_exists($item->fields['form_name'], Flamingo_Inbound_Message::channel_taxonomy ) ) {
				wp_set_object_terms( $item->id, $item->fields['form_name'], Flamingo_Inbound_Message::channel_taxonomy );
			}
		}

Then you have to use the pagination to browse all the messages.

I didn’t want to disclose it publically…
Could you tell me what to look for you ?

Perfect !
Thank you

Thank you.
I’ll try this next week.

Hi, really sorry for this radio silence!

The problem gone away with an update.

Thanks you.

Hi @jamesosborne
I send the site health information to the private form.
I can’t tell you if this append after some update…

Thank you very much

You’re right i’ve made a mistake.
here is the full code

$submission = WPCF7_Submission::get_instance();
$contact_form = $submission->get_contact_form();
$form_id = $contact_form->id();
$data = $submission->get_posted_data();
$lists_to_subscribe = array();
		
foreach($options_list as $option){
   if (!empty($option["cf7_list_id"])) {			
       if (array_key_exists($form_id, $option["cf7_list_id"]) && $option["cf7_list_id"][$form_id] == "on") {
         $lists_to_subscribe[] = $option;
	}
   }
}

Hello.
I can confirm that the plugin doesn’t work anymore since the 5.2 update of ContactForm7.
This problem is due to the change in the submission class on the get_posted_data method.

You can read more here
https://www.ads-software.com/support/topic/beware-before-update-to-5-2/

I’m doing a new topic to give us a workaround.

That it’s !
Thank you! All is said!

Hi @jeroenrotty.
This is not a Facebook limitation, this happen on Yoast.
It’s a good think that Yoast have this behavior: i just want to know how this limitations are determined.

Thank you for your response.
Yes, I am referring to the featured image in the side panel.
I did not set up a Facebook image under the “Social” tab of the Yoast SEO metabox, I only set up an image under the SEO> Social> Facebook tab.

So the behavior described on the link is what I thought.

I can now clearly see a (good) limitation in this behavior:
If the thumbnail is very large, Yoast will fold to the default image.

Did you know about this limitation (size? Resolution? Both?)

Thank you very much

Hi, + 1
thank you very much