Ian Chapman

OK, I’ll reach out to meek support to ask why the WPML extension plugin isn’t allowing an update to happen.

Thanks for the warning about the link, however, I missed the hour time limit for editing the post. Ugh.

My apologies – I had a typo in my original post. The site is actually using v1.5.6 (not .7) of the WPML extension.

However, we are unable to upgrade to v1.5.7, despite having just recently renewed our license. We thought perhaps that might be because we needed to update the main NavXT plugin first (and that is what caused the fatal PHP error).

The plugins page says: “There is a new version of Breadcrumb NavXT WPML Extensions available.?View version 1.5.7 details.?Automatic update is unavailable for this plugin.”

The settings page shows that the license is valid. We even removed it and then re-licensed it just in case, and it still shows it is valid. But it doesn’t give us the option to upgrade the WPML extension from v1.5.6 to v1.5.7.

Thanks,
Ian

• This reply was modified 9 months, 2 weeks ago by Yui. Reason: unlink

Thank you for confirming that the original instructions were not going to work.

I’ve updated the plugin and modified the code to use the new function you mentioned. I can now report that the data is now saving for both steps of the form.

Thanks again for all your help. I’m now going to head off and submit a 5-start review!

Thanks,
Ian

Just a small note to anyone who comes across this code snippet – there is a small type in the code. The section to modify the Gravity Forms shortcode should be “gravityform”, not “gravity_form”.

        add_shortcode('gravityform', function(){
            
            echo '<div style="padding:50px 0; text-align:center; background:#f4f4f4;">Gravity Form</div>';
            
        });

Otherwise the solution is working well for me.

That would be appreciated if there is a JS solution that could eliminate the form tags, so that the form will render as expected, but without any functionality when inside the Admin.

I’ll use the workaround you provided for now, but would love to see such a feature added in the future.

Thanks,
Ian

I figured that was the reason. I just didn’t know if you had a workaround that still allowed rendering of the form. But I understand why that is not the case with the “form inside a form” issue.

We are using multiple WYSIWYG inputs, so I will have to handle it that way. But I appreciate offering both solutions.

Thanks,
Ian