• Resolved wpgerd

    (@wpgerd)


    After you update to Simple History 5.29.0 WordPress keeps saying that there is a Simple History Translate update.

Viewing 15 replies - 1 through 15 (of 19 total)
  • Plugin Author Pär Thernström

    (@eskapism)

    HI @wpgerd !

    Can you share a screenshot of the issue or explain the issue in more detail? What happens if you go to the updates screen and update all translations?

    Thread Starter wpgerd

    (@wpgerd)

    Hi Pär Thernström,
    if I update all translation, for a short moment, all updates are actual. But if I go back to “Aktualisierungs-Seite” the same translation file should update. There is a circle.

    Hope this helps to explain
    Gerd

    I appear to have the same/similar problem

    WP Updates page shows “New translations are available.”

    After hitting the Update Translations button I see:

    “Updating translations for Simple History (es_ES)…

    Translation updated successfully.”

    But the WP Updates page still shows “New translations are available.”

    Mike

    I have the same issue. 5 sites that can not get the translations. I get prompted to install translations, both thru ManageWP and in admin. I like a clean admin without any red dots…

    Sample: https://ibb.co/tpBT4zQ3

    Removing your plugin and re-installing it does not help. I still have to add translations.

    Best regards,
    Johan

    Plugin Author Pär Thernström

    (@eskapism)

    Thanks for the updates. Seems to be an issue with some specific locales. Not sure if it’s related to Simple History specific or with plugins generally. I can not see this behavior for my locale or for any plugins that I have. Will keep an eye here for more replies and also test a bit more on my local installs…

    Thread Starter wpgerd

    (@wpgerd)

    There was a similar issue here: https://wordpress.org/support/topic/4-13-4-translations-update-bug/

    But deleting the transients in my case wasn’t the solution ;-(

    Strange!

    I’ve changed nothing – but today, the translation worked fine…

    ¯\_(ツ)_/¯

    Thread Starter wpgerd

    (@wpgerd)

    Congratulations! Here’s the same thread with the translation updates on page 30……

    rlkz

    (@rlkz)

    Hi there,

    We have the same issue (Translations ES). It was causing havoc with WPTC trying to get backups going (100plus diffs daily).

    Remove Simple History completely, and there is no Translation Update available). Add Simple History back, and there is a Translations Update available. When you update (translations ES for Simple History), it doesn’t seem to indicate it was actually updated, and continues to show as an update. Simple History logs show a loop of it being installed for that plugin alone, over and over and over.

    Odd issue we have not seen on any other site we maintain. More than happy to provide additional logs/site info if needed.

    Thanks

    Plugin Author Pär Thernström

    (@eskapism)

    Ok, I have done some more research and I can confirm this is an issue with the Spanish translation.
    After switching my user to use Spanish (es_ES) I was suggested the same update again and again. This happened even with the plugin deactivated, so it is not a bug in Simple History.

    Instead it looks like a WordPress-core issue with how translation updates are handled. After some research I found Trac ticket #65429 which seems to be related to this issue. The ticket is still open and there is a patch that has not yet been merged.

    What seems to be happening, for the curious: WordPress decides a translation update is “available” by comparing the date wordpress.org advertises for a language pack against the date stored inside the file you download. For Simple History’s Spanish (es_ES) pack right now those two don’t match:

    • wordpress.org advertises it as updated 2026-06-02
    • but the actual .po file inside the download still reads 2026-02-16

    So WordPress installs it, sees the file as “older” than advertised, and offers it again — which seems to be the loop you’re all seeing. That also fits why “Update successful” is immediately followed by “available again”, and why reinstalling the plugin doesn’t help (the language files live in wp-content/languages/, separate from the plugin).

    I don’t know how to rebuild the language pack on the server side. I’ll see if I can figure it out, otherwise I hope the ticket gets some attention and a fix soon. In the meantime, if you switch your user to a different language (e.g. English) the update should stop being offered, and you can still use the plugin as normal in Spanish — just without the latest translation updates until this is resolved.

    Thread Starter wpgerd

    (@wpgerd)

    I’m not sure if I understood correctly. Wouldn’t it also be possible to update the Spanish (Spain) language file? It’s currently only 26% translated: https://translate.wordpress.org/projects/wp-plugins/simple-history/. If more strings were translated here, a new language file would be uploaded. Unfortunately, I don’t speak Spanish.

    Temporary workaround: Download the simple-history-es_ES.po file from wp-content/languages/, edit it using POedit or another PO editor (in POedit, the first four entries have small errors like an extra space). Save the changes, recompile it into a WordPress translation file (.mo), and upload both files to the same location.

    Temporary download link for a zip with both files already updated (will autoexpire in 7 days)
    https://storage.to/uwV5RL2SK

    • This reply was modified 2 months, 3 weeks ago by zemog.
    • This reply was modified 2 months, 3 weeks ago by zemog.

    Glad I found this thread. I am also already on this for some time and could not find a solution yet. Obviously it’s not only happening to me.

    @zemog your download links are already expired

    Hi, I’ve updated and completed the Spanish translations to see if the update solves the problem. They are awaiting approval. Also, I’ve pinged the Spanish translations Slack channel to try to acelerate the solution.

    Plugin Author Pär Thernström

    (@eskapism)

    Thanks @pauloc! Crossing my fingers that they are approved soon and that that fixes this issue 🤞.

Viewing 15 replies - 1 through 15 (of 19 total)

You must be logged in to reply to this topic.