Skip to content Skip to sidebar

Home › Support › English Support › [Resolved] Custom gutenberg block - Let's Info Up

[Resolved] Custom gutenberg block - Let's Info Up

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client was unable to edit text using the Advanced Translation Editor after updating it. The issue seemed to be related to outdated plugins or custom work that was not compatible with the latest WordPress updates.

Solution:
1. We escalated the issue to our second-tier support for further investigation.
2. We identified JavaScript errors and deprecated functions related to the client's theme and plugins.
3. We recommended the client contact the theme provider, "codetipi", to request an update for the theme and associated plugins.
4. We provided a workaround by adding custom XML configuration to register the problematic blocks:

<wpml-config><br />  <gutenberg-blocks><br />    <gutenberg-block type="lets-info-up/block-info" translate="1"><br />        <key name="blocks"><br />            <key name="*"><br />                <key name="content" /><br />                <key name="title" /><br />            </key><br />        </key><br />    </gutenberg-block><br />  </gutenberg-blocks><br /></wpml-config>

5. We instructed the client to apply a small edit to the existing content to allow WPML to detect and refresh the elements for translation.

If you're experiencing a similar issue, we recommend trying the provided workaround. However, this solution might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket with us.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: 

This topic contains 4 replies, has 2 voices.

Last updated by samY-2 1 year, 3 months ago.

Assisted by: Ilyes.

Author Posts
May 2, 2024 at 3:35 pm

samY-2

Hi, I'm having an issue with translations. after updating the advanced translation editor, I'm unable to edit. my side text. please check the attached.
May 2, 2024 at 4:08 pm
May 3, 2024 at 3:45 pm #15591973

Ilyes
Supporter

Languages: English (English ) French (Français ) Arabic (العربية )

Timezone: Pacific/Easter (GMT-06:00)

Hello,

I have escalated the issue to our 2nd tier as it looks like there are various issues:

Uncaught TypeError: tinyMCE.addI18n(...) is not a function at VM422 post.php:16:3

deprecated.min.js?ve…84915c5e8ae38964c:2 Declaring non-string block descriptions is deprecated since version 6.2.

deprecated.min.js?ve…84915c5e8ae38964c:2 select( 'core/edit-site' ).__experimentalGetPreviewDeviceType is deprecated since version 6.5 and will be removed in version 6.7. Please use select( 'core/editor' ).getDeviceType instead.

deprecated.min.js?ve…84915c5e8ae38964c:2 `position` prop in wp.components.Dropdown is deprecated since version 6.2. Please use `popoverProps.placement` prop instead. Note: Note that the `position` prop will override any values passed through the `popoverProps.placement` prop.

deprecated.min.js?ve…84915c5e8ae38964c:2 Using custom components as toolbar controls is deprecated since version 5.6. Please use ToolbarItem, ToolbarButton or ToolbarDropdownMenu components instead. See: https://developer.wordpress.org/block-editor/components/toolbar-button/#inside-blockcontrols

9611.vendors.chunk.js:1 [DEFAULT]: WARN : Using DEFAULT root logger

WordPress Developer ResourcesToolbarButton – Block Editor Handbook | Developer.WordPress.orgToolbarButton can be used to add actions to a toolbar, usually inside a Toolbar or ToolbarGroup when used to create general interfaces. If…

In this case this looks like custom work to me, or it is that this plugin has not been updated for a long time and is not in development anymore.

It looks like those plugins are added when purchasing a theme like this one for example Zeen | Newspaper Magazine News Blog WordPress Theme + WooCommerce by codetipi (themeforest.net)

Then you might have created a custom theme but kept using these plugins. They are outdated for a long time.

I recommend contacting "codetipi" as they state that their theme are WPML compatible and those plugins seems to be shipped with their themes to ask them to update their theme.

In the meantime, the 2nd tier are looking for a workaround for this case,

Best,
May 4, 2024 at 2:09 pm #15593507

samY-2

Do you mean the let's info up plugin is now merged with the Zeen theme?

May 4, 2024 at 4:23 pm #15593642

Ilyes
Supporter

Languages: English (English ) French (Français ) Arabic (العربية )

Timezone: Pacific/Easter (GMT-06:00)

Hello,

I have got a workaround to register these blocks from Lets Info up, we had to add this XML code your your custom XML configuration: 

<wpml-config>
  <gutenberg-blocks>
    <gutenberg-block type="lets-info-up/block-info" translate="1">
        <key name="blocks">
            <key name="*">
                <key name="content" />
                <key name="title" />
            </key>
        </key>
    </gutenberg-block>
  </gutenberg-blocks>
</wpml-config>

Now I made a test page and I was able to see the content under the translation editor : hidden link

Here is the test page : hidden link

To apply this change on the existing content, simply apply a small edit to the content, this should be enough for WPML to detect it and refresh the elements to include it in the translation,

Best,
May 6, 2024 at 4:22 am #15594945

samY-2

Hi!

Great,

Could you please guide me where I need to apply changes exactly
May 6, 2024 at 4:28 am #15594947

samY-2

Hi Ilyes,

Thank you for your wonderful support, I really appreciate that.