erichie

I’m sorry to hear that you had a bad experience with our plugin.

Could you give me more information about what exactly you did to make this happen with steps to reproduce? I’ve never seen anything like this happen and I would love to figure out what happened so we can prevent it from happening to anyone else.

Thanks!

What does the gallery shortcode look like in your source post?

@lauralauralaura,

You can activate Media translation in the Polylang settings. This should mean your images get copied over to your translated posts.

@ibasher

After some testing on our end we are not able to reproduce this issue. When translating custom fields, only the translated field appears on the translated post, which is the correct functionality.

Could you provide some more details about the configuration of your site?

Do you have any other plugins that may be copying over the source custom field to your translated post or may be interacting with it in some way?

Okay that makes sense. The translated post should not have the source meta. We will look into why this may be happening.

@ibasher

When you say there are duplicates of the custom meta fields do you mean in the database or that on the translated post both the source and translation appear?

@fermekon

Thanks for letting us know about this. We will look into it.

@el-asador-aleman

Thanks for bringing this to our attention. We do support bulk actions for custom post types and taxonomies but we will look into this further to see if adding them in your theme may be affecting this in some way.

I seem to be able to translate custom post types and custom taxonomies just fine.

Have you enabled the translation of your custom taxonomies both in the Polylang settings and the Lingotek Manage -> Content Type Configuration page?

Are you manually adding custom post types and taxonomies or are you using a plugin to do that?

What are your settings on the Lingotek Defaults page?

Thanks for reporting this. A fix will be going out in our next release.

@taulen

We had released some code that wasn’t compatible with older versions of PHP which was causing the error you saw.

Version 1.2.8 of our plugin which we just released should resolve these issues and everything should work great now!

Let us know if there are any other issues.

As a heads up to everyone who has been having this issue.

We have fixed the issues with Machine Translation and your content shouldn’t get in the stuck state anymore. Your content should go through the translation process smoothly. If you are still having issues do not hesitate to reach out and contact Lingotek Support.

As a heads up to everyone who has been having this issue.

We have fixed the issues with Machine Translation and your content shouldn’t get in the stuck state anymore. Your content should go through the translation process smoothly. If you are still having issues do not hesitate to reach out and contact Lingotek Support.

As a heads up to everyone who has been having this issue.

We have fixed the issues with Machine Translation and your content shouldn’t get in the stuck state anymore. Your content should go through the translation process smoothly. If you are still having issues do not hesitate to reach out and contact Lingotek Support.

We have fixed the issues with Machine Translation and your content shouldn’t get in the stuck state anymore. Your content should go through the translation process smoothly. If you are still having issues do not hesitate to reach out and contact Lingotek Support.