mattkiosk

My interim solution has been to deploy this snippet to my functions.php:

function yoast_bug_fix() {
    echo '<script type="text/javascript">var wpseoSelect2Locale = wpseoSelect2Locale || "en";</script>';
}
add_action('admin_footer', 'yoast_bug_fix');

Not a long term solution, but hopefully helpful to someone else if they find this forum post. I’ll keep digging for a proper solution.

• This reply was modified 8 years, 1 month ago by mattkiosk.
• This reply was modified 8 years, 1 month ago by mattkiosk. Reason: Spelling, grammar/bad paste

@jfn99

Curious if you can share an example of how you setup the plugin to connect to FranConnect. I have a client that is interested in that integration and would rather use this plugin than roll my own solution.

Thanks!

@zackdn Here you go!

You’re welcome, Damien. I should note that while testing didn’t prove to find anything truly awful occurring due to the hack, it was still to dodgy for a production deployment. Instead, we ended up rolling back to the previous 3.1 version of Custom Post Types that we had lying around on out development server.

That said, I’m still curious if the plugin author or any other user has some insight into what’s broken and how to resolve.

As a temporary hack, I’ve commented out this line from the Gravity Forms: Post Updates plugin. I suspect that plugin hasn’t yet adjusted to work with the 3.1.1 changes to Custom Post Types. I’m testing now to see who adverse effects, if any, crop up and will post again if I find anything, good or bad, that occurs.

Excellent. Thank you for the help. It does answer my question. Unfortunately, it seems as though my problem is a bit wonkier than I expected.

Great work on the plugin, too. It does an amazing job.