2nd language page elements named differently after translation – WPML

[JeffCl]

I am using Genesis framework with an adapted sample child theme, woocommerce and the Genesis connect plugin, and WPML.

My Shop in the default language and second language look identical and behave as expected:

http://69th-dept.com/shop/
http://69th-dept.com/?•??—/?lang=zh-hans

As do my default language category pages, for example:

http://69th-dept.com/product-category/coats/

However, when I switched to my second language for any category, the page formatting changed entirely and the main content took 100% width, while the sidebar dropped below.

Through inspection I found that my shop pages, both default and second language, and my default language category pages, have differently named elements to my second language category pages, as follows.

http://69th-dept.com/shop/
http://69th-dept.com/?•??—/?lang=zh-hans
http://69th-dept.com/product-category/coats/

all have:

<main class="content" id="genesis-content">
but

http://69th-dept.com/?•??“?目?•/大衣/?lang=zh-hans

has:

<div id="content" role="main">

I have screenshots of the problem in my inspector here here, here, and here.

I have fixed the immediate problem by including css for #content that matches .content but I am worried that if this element has been translated incorrectly, perhaps others will be too.

Is this a known problem? e.g. a known conflict between Genesis and WPML? Was the id #content used in Genesis pre html5?

WPML support are suggesting a compatibility problem with my theme or settings. Anyone have any ideas?

Jeff

http://69th-dept.com/shop

[JeffCl]

WPML Support have managed to replicate the problem in a duplicate of my site in their test environment and identified the problem as being cause by the Genesis Connect Woocommerce plugin and WPML.

The incompatibility happens when the "Genesis Connect for WooCommerce" plugin is enabled. This plugin change the tags between the original and the translated version. On the other pages (like the About page, it works correctly).

After some of my pages are translated, the 2nd version of those pages is using the older xhtml genesis markup, WPML are contacting the plugin author to see if the incompatibility can be resolved.

In the meantime my stop-gap solution of creating a #content css class seems to be working fine.

I will create another forum post with a more appropriate title to help others who may be encountering a similar problem, and post to the connect plugin's support page.

[Author]

Posts