Hi Mike,
I’ve tried this as you have suggested and the problem does in fact go away with the modified version of wpgform-post-type.php
That is interesting, thanks for checking this out so quickly. I am still not convinced that Google Forms is doing anything wrong. This is the chunk of code which is commented out.
if (0):
// Post type is registered, do some hygiene on any that exist in the database.
// Insert the "wpgform" shortcode for that post into the post content. This
// ensures the form will be displayed properly when viewed through the CPT URL.
$args = array('post_type' => WPGFORM_CPT_FORM, 'posts_per_page' => -1) ;
// unhook this function so it doesn't update the meta data incorrectly
remove_action('save_post_' . WPGFORM_CPT_FORM, 'wpgform_save_meta_box_data');
$loop = new WP_Query($args);
while ($loop->have_posts()) :
$loop->the_post() ;
wp_update_post(array('ID' => get_the_ID(),
'post_content' => sprintf('[wpgform id=\'%d\']', get_the_ID()))) ;
endwhile ;
// re-hook this function
add_action('save_post_' . WPGFORM_CPT_FORM, 'wpgform_save_meta_box_data');
endif;
It runs as part of the init hook when the Google Forms post type is registered. I may have another test to try shortly, would you be open to additional testing?
Hi
Changes also work to me! Thanks!
If you want to do more tests, you can count on me.
Thanks for the additional confirmation. I have also commented on the WordPress SEO GitHub thread.
I need to think about where else I can do this hygiene step. It can’t happen at plugin activation because the plugin activation hook doesn’t fire during a plugin update.
Beta version of v0.66 in my Dropbox which should fix WordPress SEO conflict. I’ll get this posted on my web site shortly.
Let me know if there are any problems.
The v0.66 beta build now on my web site with some background.
Hi
I try the version publish at http://michaelwalsh.org/blog/2014/04/google-forms-v0-66-beta-2-available/
It’s s google-forms-v0-66-beta-2.
Works fine, Thanks!
But,
I took a big scare, because WordPress lost permalinks cache (in the production version :S)
I fixed it by selecting another option permalinks and then back to my permalinks option.
With the last 0.67 version everything is working fine.
Thanks for your fast and amazing support.