Improved handling of Wordpress content

[Chase Tingley]

Wordpress content is HTML, but it also includes a custom syntax called shortcodes. The inline codefinder works for many shortcode cases, but there are some that it struggles with.

Since Wordpress refuses to go away, it would be good to have a canned solution for it, either as a custom HTML configuration or (if necessary) a dedicated filter. I will look at these options and figure out which is best.

[Chase Tingley]

Attaching WPML sample files from Yves. These are WPML exports, which means they are wordpress content (including shortcodes) inside CDATA inside XLIFF. Note that handling these files as-is is best accomplished by implementing this enhancement AND issue #688.

[Chase Tingley]

It sounds like this happens when WPML isn't either properly configured or doesn't support a given theme/plugin: https://wpml.org/documentation/support/maintaining-the-fusion-builder-avada-compatibility-with-wpml/

Here's an example of a wpml-config.xml file with mappings for a bunch of stuff: https://github.com/OnTheGoSystems/wpml-config/blob/master/avada/wpml-config.xml