You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have reports of translators when pressing save and next block that it sometimes takes them back to the front page of rosetta and the translations for that block are lost.
I'm wondering how does rosetta deal with multiple translators working at once? They are in different languages so not updating the same .po.
We have set it to 100 strings per page, but they report if they try submit too many at once it sometimes doesn't save.
The text was updated successfully, but these errors were encountered:
I'm getting the same reports, which has apparently happened multiple times. I haven't witnessed it, but the sequence is the same: saving a page's worth of translations takes the user to the main Rosetta landing page where one selects a language to translate into.
In my case, we're displaying (and consequently losing!) 50 messages per page.
@oppianmatt – please update this thread if you notice this behavior persisting after upgrading to version 0.8. The way caching was employed and session magic was used radically changed, and I suspect that your symptoms will disappear. If not, it would be good to know!
We have reports of translators when pressing save and next block that it sometimes takes them back to the front page of rosetta and the translations for that block are lost.
I'm wondering how does rosetta deal with multiple translators working at once? They are in different languages so not updating the same .po.
We have set it to 100 strings per page, but they report if they try submit too many at once it sometimes doesn't save.
The text was updated successfully, but these errors were encountered: