[Resolved] WPML > String Translation (Hide Bricks or gutenberg domains)
This thread is resolved. Here is a description of the problem and solution.
Problem: You are experiencing difficulty in finding specific strings in WPML > String Translation due to the abundance of bricks-* or gutenberg-* domains. Solution: Currently, it is not possible to hide bricks-* or gutenberg-* domains directly in WPML > String Translation. To address this issue, you would need to implement custom coding. However, this solution falls outside our support scope, and we do not have a ready-made code snippet available.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also advise checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum.
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.
Thanks for contacting WPML forums support. I'll be glad to help you today.
1) I'm afraid you can't hide these domains. However, you can delete these domains if you don't want to translate these strings.
2) Could you please share your Debug information with me?
You can read a detailed explanation about it here. (http://wpml.org/faq/provide-debug-information-faster-support)
The debug info will give me a lot of information about how your site is configured.
I don't think so, because those are created whenever a new blog post is created I think, and we already translate them through the WPML Advanced editor screen, I don't need to see them all inside WPML > String translation, I would need a code snippet or something that I can turn ON so those from blog post (gutenberg) doesn't show in WPML String translation.
Since the team from the website is creating lot of blog posts every day, deleting them manually isn't a viable solution for us.
The provided snippet didn't worked, so I created a JavaScript code to hide all the builder related domains inside the select at least, make my workflow much faster
It's great to hear that you found a workaround for the issue. 🙂 Please don't hesitate to open a new ticket if you face any other issues. We are always happy to help you.
