Conflict with WPML?
-
I added WPML to my site and I’ve noticed that a translated page that uses a FormAssembly shortcode doesn’t work. It just outputs “404 Oops, something went wrong. Page Not Found (404) – Did you enter the address correctly? If this error message is not helpful, please let us know. We’ll try to get back to you with a better answer” in red text. I’m using the same shortcode as the English version. The shortcode is stored in an Advanced Custom Fields WYSIWYG field, for what it’s worth. Everything else in the field displays fine, just not the shortcode. To make sure it’s not an ACF issue, I copied the shortcode to the main content editor (I’m using the classic editor) in a test translated page with the default template, and the result is the same. I made the same page in English and it worked.
-
Nope. I had a look at the plugin source code. It’s passing the current query string to the remote FormAssembly URL. So, if the only shortcode attribute is a form ID and there is a “lang” parameter in the current URL because of WPML, the plugin attempts to load something like https://app.formassembly.com/rest/forms/view/the_id?lang=ko. It turns out if you request a URL like this, it redirects and puts the value of “lang” in the path, so it ends up being like https://app.formassembly.com/ko//rest/forms/view/the_id, and this gives a 404.
The topic ‘Conflict with WPML?’ is closed to new replies.
