Make Post type used by sublanguage appear in menu

Hello,

Just 2 things:
First I am working on a new version where I will probably drop these post types and store everything in post meta, in order to improve compatibility and optimize resources (less database queries). So allowing these post types in dashboard may not be a long term solution.

Secondly, there is actually no way to do this by filters, you need to edit the source code. If it’s okay, here is how you can do this:

In sublanguage/sublanguage.php, line 1510, set 'show_in_menu' => true,

Then in sublanguage/include/admin-post.php, you need to remove all code between lines 68 and 89.

Just out of curiosity, may I ask you why you want to do this?

Hi Maxime
Thanks a lot for your answer.
To answer why..
I used qtranslatex in many sites, but for new projects I look for a solution that allow to separate everything in a “clean way”, optimized for great SEO with slugs by languages etc., not intrusive and light… And your plugin is exactly what ? wish.
Also since each translation is a post itself, it is helpful to take all advantages of posts to have easy access and administration by language, for instance export all post in english from specific category.

When do u intend to launch next version ? So translations wont be considered as indépendant posts ? It will be closer to qtranslate solution then with only one post for all translations, isn’t it? What with slugs? What will happen to current translations with your plugin, how to migrate? Should ? wait and see?
Thank u

I thing an important thing for a multilanguage solution is to be able to handle language inheritance. In Sublanguage, you can define what is translatable and what is not. For example, in a product post type, you want the title and the description to be translatable but not the price, nor the feature image.

If you don’t care about this language inheritance, you may try Polylang, which is free and popular. It separates clearly translations in different posts.

In sublanguage, translations are more interconnected. Technically translations are separated in different posts, but they are not independant, they are actually dependant of their “main” language post.

And this is not going to change in the next (major) version. The overall interface will not change, and I plan the migration to be just as trivial for users as any plugin update. The only change that (hopefully) will be perceptible is the gain in performance and speed. It won’t be closer to q/xTranslate than it is now, and slugs are going to work exactly the same. I just advise users against customizing the admin interface of the plugin right now. This update should be launched around the begin of 2017.

Thank you very much for your answer.
Indeed, I checked on my own and it seems that polylang is what I am looking for.
And as you said your solution is great also for product post type, I think in particular about a real estate one that I have.
thanks again.