Camilo

Thanks!

I’m making my own WordPress theme (https://github.com/oncet/tini), if that’s what you mean. I don’t have a public environment yet.

Anyway, seems like this isn’t a SLB issue so I’m clossing this topic.

• This reply was modified 5 years, 8 months ago by Camilo.

Another invalid review.

OMG don’t even listen to this people. This plugin saved me a lot of time in a lot of projects, thanks for your hard work.

Sync Custom Fields is a cool feature because it saves you time from repeating the processes of setting common fields on different translations of the same post. But I think it has a small problem.

* 2 languages, English and Spanish
* And a custom field “color”
* Create a post in English with color “red”
* Create the Spanish translation (by clicking “Add new” or the “+” icon)
* Save the Spanish version without setting any color

Now both versions of the post contains no color set. What I think the user might really expect is to have both versions set to “red”. Note that I didn’t run this exactly test, in my case I was using the Attachments plugin for the custom field.

My suggestion is that when a user starts creating a translation from a post that already exists, get Polylang to load the custom fields values from the existing post and use them as default values for the new translation. Without this feature, the user will need to create both translations first and just then set the settings for the common fields.

Great! That solved my problem.

Thanks a lot for your time.

I can confirm that Polylang 1.2.1.6 fixed the issue on the custom post types. I’m marking this topic as resolved.

Thanks a lot for your time
and keep it up with the good work!

Done. I’ve sent a simplified version of the theme, hoping to help out confirm if this is a bug or not.

I wrote it myself. Is it any useful if I only share the section where the post type declaration is?

My theme is not public but I have no problem in sharing it. I’ll post the link when I finish uploading it.

Thanks a lot for your time.

I tried un-cheking and checking it back with no luck.

My post type is declared at theme level. If it’s of any use, I can share my post type declaration.

Thanks! That’s just what I needed.

Yes, I realized about that when I peeped into a database backup. I replaced it with the data from the backup and everything came back to life.

Thanks for the support!

These are the settings for cctm_data in wp_options:

a:8:{
	s:5:"flash";
	a:0:{}s:5:"locks";
	a:0:{}s:14:"post_type_defs";
	a:0:{}s:17:"custom_field_defs";
	a:0:{}s:27:"cctm_installation_timestamp";
	i:1371692093;
	s:11:"export_info";
	a:5:{
		s:5:"title";
		s:9:"CCTM Site";
		s:6:"author";
		s:20:"[email protected]";
		s:3:"url";
		s:29:"https://www.demo.com";
		s:12:"template_url";
		s:0:"";
		s:11:"description";
		s:67:"This site was created in part using the Custom Content Type Manager";
	}
	s:21:"cctm_update_timestamp";
	i:1371692093;
	s:12:"cctm_version";
	s:5:"0.9.4";
}

I just edited e-mail and url in this post for obvious reasons.

As far as I can see, it seems the cctm_version is mismatching with the installed version (0.9.7.6).

Updated to WP 3.5.1, still same problem.

Enabled debug mode using define('WP_DEBUG', true); and there are no error messages.