Support » Plugin: Sublanguage » Gutenberg and custom fields translation

  • I use ACF, Sublanguage and Gutenberg. I unchecked “Use asynchronous language switch in Gutenberg. NOT COMPATIBLE WITH METABOXES!” because I need translation of meta. All is fine if meta isn’t touched.
    All attempts to save post if it has changed meta, ruins all post translations. I check with clear install of current WP version, then I tried 5.2.2 and 5.1.1 & ACF 5.8.0 with the same results. I tried PHP 7.3, 7.2 and 5.6 just to be sure.

    Additional problem concerning this, that Gutenberg shows all the time that all is OK (Post updated. View Post), but in Network tab is response — «The block editor requires JavaScript. Please enable JavaScript in your browser settings, or try the Classic Editor plugin.»

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter Olga Gleckler


    When post is saved from Gutenberg with meta, it causes two requests — first through REST API and second to post.php (It’s why by a redirect browser is getting a whole admin page with message about JavaScript) and it’s only sending meta boxes, so no main fields are presented in request.
    I manage to prevent rewrite be second request by your hook ‘sublanguage_admin_update_post’, but for custom posts it still don’t work. Even if you have function to «register post types for Parse meta for REST» and seem to cover everything. I solved this by remove REST API for this custom post type. It shut Gutenberg down to it, but it can stay this way.

    I still will be glad to some tips, so ))

    And thank you any way!

    Plugin Author maximeschoeni



    Thank you for submitting this issue, but sorry I don’t think I can help you. Actually I’m thinking about removing Gutenberg support from this plugin. For 2 reasons:

    1. I can’t find a way to implement it nicely (the current implementation is ugly and there’s no surprise its bugged). But Gutenberg API still doesn’t look ready.

    2. Gutenberg is probably a fine editor for blogs, but I experienced it as unfit for the kind of websites I develop, especially the ones with multi-language. And I can’t see a positive evolution in the last updates. I just don’t have the resources to support a complex feature I’m not going to use myself.

    I read this your latest answer an I’m afraid of it!
    What does it mean that you don’t support Gutenberg?
    From 2021 or 2022 classic editor will not be supported by WP.
    It means that I created a website with your plugin and cannot be able to use Gutenberg anymore?
    It seems like qtranslate multi-language that some developer started to maintain for a year or two than abandoned it leaving a plenty of us with our sites without support.
    So we lost time and we have to migrate to other plugin maybe having our sites with thousand pages wasted
    Let me know your intention before I move my other two sites to your plugin.

    Plugin Author maximeschoeni


    Thanks for sharing your concerns.

    I’m no commercial and I’m not trying to sell things. I’m just sharing a plugin I’m using for the websites I’m building myself. Maybe I get hit by a car when I leave tonight and this will be the end of sublanguage. I really have no plans about what to do with gutenberg in the next few years and I can’t promise you anything. I just give you 2 advices:

    1. If you really need Gutenberg for a site you are building now, don’t use sublanguage. The user experience with sublanguage/gutenberg is currently just poor. Although I doubt it will be much better with an other multi-language plugin, at least the support probably will.

    2. Don’t fear about WP stopping support for Classic. Classic plugin currently have 5M+ active installations, its not going to stop anywhere soon. And the reason why it is so popular is because there is a problem (to make it short) with Gutenberg. And Classic support will not drop until they solve it. And when they solve it, I’ll be able to fix things in sublanguage.

    How about at least a donation link? I’ll help.

    I have used maximeschoeni excellent plugin and after testing many other systems over a month or two. For me it was the clear winner.
    I would be happy to make a donation.
    I’d also like to see if there is a way to help the future of this plugin.
    I’m not a programmer but a graphic designer, but i can see that with so organisation, this could be developed into a real commercial contender in the WP translation space.
    So i believe a great opportunity.
    maximeschoeni has done some amazing work here.
    If anybody else has an ideas on how we can create a team, roadmap, to create a sustainably future for this plugin.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Gutenberg and custom fields translation’ is closed to new replies.