Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support Chrystl

    (@chrystl)

    Hello

    some of the stings?

    Which strings? In String Translation tab?

    Thread Starter Kurnik

    (@kurnik)

    I won a gold medal of stupidity!

    I have clicked in Polylang -> Settings at Strings translation option below “Clean strings translation database” if you can believe. Now am I asking if there is some way to get it back? :/

    Fingers crossed! ??

    Did you update the plug-in by any chance? I spend a few days scratching my head until I discovered that apparently in version 1.7.x theme strings are not recognized anymore. Is it a bug? I don’t know, but downgrading to 1.6.5 solved the issue for me. Had to delete a few entries in the database though, otherwise site would go into WSOD.

    EDIT:

    The site is running on Nation Hotel theme, which is partly build with Option Tree.

    Thread Starter Kurnik

    (@kurnik)

    Hey d9media,

    Thanks for your response. ??

    Yes I made an update. Now running 1.7.4. I can try do downgrade that I can do but editing few entries in the database that would be like too much for me.

    You are welcome. Then I suggest the string probably got lost due to that. Exactly the same happened to me, I even thought I had flushed the strings by accident as well.

    I couldn’t really find a statement by the plug-in author on this, even though it seems to affect quite a few sites from what I read on Themebrain. Whatever has changed from 1.6.x to 1.7.x needs to be fixed so the plug-in will be compatible again to those sites in the future. Unfortunately I couldn’t find WHAT has caused the error. Perhaps Chouby could provide a rollback for those affected.

    Great plug-in though! I disabled update for Polylang for now so no more headache ??

    Thread Starter Kurnik

    (@kurnik)

    Yeah…, try to image that for me without all knowlage about the code and stuff it’s much more depressing. I just don’t know about something is going wrong or missing an I’m standing there and guessing, hehe :/

    I don’t know even if it’s ok for me to downgrade, I can’t find 1.6.5 on the net anyway though, so yeah. Let’s wait to hear from Chrystl what can he told as about our pain ??

    And yes. Polylang is still great plugin if you are ask me. I bought WPML just 3 days before I found out about Polylang and I’m stuck here with it. One lite plugin, maybe a little bit too lite but still comparing to 2415 WPML plugins and add ons. I get lost there before installing everything correctly ??

    Cheers mate and tnx again.

    Plugin Support Chrystl

    (@chrystl)

    @d9media
    Indeed there was a bug but fixed in the 1.7.4. See the changelog:

    1.7.4 (2015-05-03)

    fix: WPML strings translations not always loaded (introduced in 1.7)

    @kurnik

    “Clean strings translation database” if you can believe. Now am I asking if there is some way to get it back?

    This option allows you to clean the database of all unused strings and there isn’t a way to go back.

    Thread Starter Kurnik

    (@kurnik)

    Cool. Understand.
    Thanks for you reply Chrystl.

    @chrystl

    Thanks for pointing out the update.

    I just downloaded the new version to the production site (which is not translated yet) but sadly I need to say that still in the string translation only text from yoast and widgets is listed (total of 26), whereas on the 1.6.x version that I use on the dev site, around 80 strings are shown.

    It is the theme option strings that are not showing up anymore. The theme is build on Option Tree. But since I am not an expert in WP I can not provide you with more details about what could be the cause.

    (I won’t blame the plug-in, don’t get me wrong. It is very bad practice among many WP themes to define content in the theme options anyway.)

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘How to rebuild strings’ is closed to new replies.