WPML Translation Settings of custom fields hamper proper translation

Via my WPML Contractor profile I was approached by a Dutch developer building a site for a leader in waterproof (bathroom) media products.

The problem this developer encountered was that in the backend the content seemed all translatable, but in the frontend not all content was showing.

My experience tells me that in almost all cases this points to a problem with the WPML translation settings of custom fields.

After receiving the backend login, my suspicions were confirmed: all custom fields were set to “Not translatable”.

My suggestion was to give the client the chance to adjust the settings, but after a few trials and errors he was more comfortable with me doing the job on his behalf.

And once I had adjusted the settings, the client expressed his happiness.

Thanks for your assistance with correcting the translation settings and your rapid work.