[Plugin: Genesis Featured Widget Amplified] Filters (or translation) for input text fields

  • Hello,
    I am running a WPML powered website and I am using your powerful plugin to generate a customized list of posts. However with the current version, it seems not possible to translate some texts, specifically the “Link Text” for category archive links. I think the same happens also for the “More text” used for posts.
    Would it be possible to let those strings be WPML-ready, or at least provide some filter hooks to interact with them somehow?
    I saw there’s a hook called gfwa_category_more but it’s not enough, since there’s no way to dinamically alter the current widget instance to show the translated text.
    Thank you.

    https://www.ads-software.com/extend/plugins/genesis-featured-widget-amplified/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Nick the Geek

    (@nick_thegeek)

    Marco,

    The issue is that the strings for the defaults are translatable but once the settings are saved, which happens when the widget is moved to the sidebar, the English string is saved to the database as part of the widget settings.

    The only solution would be to use the Widget Logic plugin to allow a different instance of the plugin for each language.

    Thread Starter Marco Chiesi

    (@marcochiesi)

    Hi Nick,
    thanks for your reply. I already thought about creating multiple widgets and showing them conditionally using Widget Logic or similar plugins. I also had already implemented this solution in the past, but for the site I am currently working on, this is not as simple, since there are 3 widgets and 5 different languages, so it would end with having a total of 15 widgets, which would be hard to maintain.
    The WPML plugin allows to translate also dynamic texts, not only default texts usually translated with .po/.mo files. You can find full documentation about how to support WPML in other plugins here). It’s quite simple, the only need is to add a few calls to WPML functions. Anyway I’m not asking you to change your plugin to be natively WPML-compatible, even if I think this would be much widely appreciated. It would be sufficient if you can provide a few filter hooks to manipulate widget instances. In particular filters that are executed when saving the data in the backend, and before showing the data in the frontend.
    Thank you.

    Plugin Author Nick the Geek

    (@nick_thegeek)

    Marco,

    I’ll look into a filter to change the $instance variable for the next version. I’m planning on adding some other filters to allow dynamic changes.

    I’ve also got a translation problem for the more text – this time with qtranslate.

    The qtranslate quick tags do not seem to work with it as they do for other plugins.

    Any suggestions very welcome as I think this is a wonderful plugin.

    Plugin Author Nick the Geek

    (@nick_thegeek)

    mljo,

    It is the same issue. You can setup multiple instances of the plugin. Otherwise it will be something I am looking into for the next version.

    Thank you – have played around with Widget Logic but this doesn’t do the trick with qtranslate. Am in a bit of a fix as this is needed quite urgently by client – er, like now ;). Any other options for me?

    Plugin Author Nick the Geek

    (@nick_thegeek)

    I’m not aware of another solution. I haven’t tried using qTraslate with widget logic, but it should be possible. You may need to ask the qTranslate developers how to using conditional logic to identify the active language.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘[Plugin: Genesis Featured Widget Amplified] Filters (or translation) for input text fields’ is closed to new replies.