This thread is over two years old and may be outdated. Please create a new thread if you need help, or email us if you have an active Premium license.

Site Origin Widgets not showing up in String Translation

Open 5 replies pluginplugin-widgets-bundlequestion
Susanne Miessner
9 years ago · Last reply by Andrew Misplon 9 years ago

I’m probably not the only version with this problem.
I am trying to translate a page that I’ve built with SO Pagebuilder.
I am using mostly standard wordpress widgets (text widget) but also the SO Hero widget on each of my pages. All the standard WordPress widgets nicely show up in my String Translation tab but the SO Hero widget is missing. Is there some way to add translation support to the SO Hero widget?

thanks in advance

This is our free support forum. Replies can take several days.

Need fast email support? Get SiteOrigin Premium

Replies

5
  1. Andrew Misplon Staff 9 years, 6 months ago

    Hi Susanne

    Thanks for posting. Page Builder only works with Polylang or WPML which both use the same duplicate/matched page method of translation. Unfortunately, Page Builder isn’t compatible with qTranslate or WP Globus which use a different method of translation. Hope that helps explain what’s going on.

  2. Susanne Miessner 9 years, 6 months ago

    Thanks Andrew,

    no this does not explain what is going on since I use WPML String translation. This is where my Site Origin widgets do not show up.

  3. Andrew Misplon Staff 9 years, 6 months ago

    We’ve done some basic functionality testing with WPML. Page Builder pages need to be translated the standard WPML way with a linked page, I don’t think it’s possible to translate Page Builder widgets with string translation. This should be a really quick process, have you created a second page and linked it?

    wpml

  4. Susanne Miessner 9 years, 6 months ago

    I have tried that. but if I use this I can only use the WPML translation interface. My translation agency is requesting to export the files to use their own translation softwares. And the options WPML is offering is .po files (string translation) or xliff-files (page translation). As explained in previous post both versions don’t work with the Site Origin widgets.

  5. Andrew Misplon Staff 9 years, 6 months ago

    Unfortunately, yes, that’s correct. The string translation method you’re attempting doesn’t currently work with Page Builder. It’s for this same reason that Polylang and WPML work with Page Builder but qTranslate and WP Globus don’t. It’s only through the linked page method (for lack of a better term) that you can translate Page Builder powered content. The reasons for this run very deep, to the core of Page Builder’s construction, so unfortunately, this unlikely to be an issue we can overcome.

Replies on this thread are closed.

Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Have a different question or issue?

Start New Thread