Hi,
I have now another problem with the translation.
I changed couple of texts in french, then deploy, but in the online solution the old texts are visible instead of the new ones. I restarted the server, deploy again, but still the old texts. I changed them in the database directly and it worked. After some time, I had to deploy again, due to some fixes in the app. Guess what? The older texts reappeared!!! So right now I don’t know if I should be ![:cry:]( "Crying or Very sad")
or ![:?]( "Confused")
or ![:x]( "Mad")
or better ![:lol:]( "Laughing")
after all, we are all humans! ![:wink:]( "Wink")
Yeah, maybe this is better!
Anyway, please tell me what can I do to fix it, because I don’t want to have an sql script to run in the messages table each time after I deploy! Or shall I create another case? ![:)]( "Smile")
When you pushed the new release out did you export (and import) it WITH i18n ?
That last bit is always optional (not enabled by default).
Yes of course I did! I always import together with i18n even if I don’t change anything there and I always check that checkbox, when export and when import!
you say that the old text reappeared, that means that even the new export had the old text, or the text in db
were changed by someone else;
can you open your export with an application that can open zip files, and check in the /export/i18n_data properties
files for you new text, does it appears there ? or is it the old text there, but in the workspace you have the new one ?
Hi,
Only I have access to the database, so no one else could change it. And anyway it was a short time until the next deploy.
I just looked in the export file as you said (I didn’t knew it’s actually a zip file, that’s nice), and the text is the new one, that appears in the developer! Actually I looked in both exports: the first one, after which I change the texts in the database with the new values because they were not imported correctly, and in the last one which revert my change in the database to the old texts, although in the i18n files, the translation is the new one!
So I’m really sure I did it the import in the correct way!
Thanks,
Bogdan.
the strange thing is then, from where is the old text got into the db, if it’s not in
the export and no one touched the db
is this still happening with your export ? if so, you may create a case with the solution,
so we can check what is going on during the import
Yes, I don’t know where it gets the text from. Does servoy keeps a log with all the changes on the server? For example, I saw that you can set a previous imported solution as the current one.
I’ll try once more to import a new generated solution and let you know.
Thanks!
there is no history kept for i18n values
udrescu_bogdan:
Yes, I don’t know where it gets the text from. Does servoy keeps a log with all the changes on the server? For example, I saw that you can set a previous imported solution as the current one.
I’ll try once more to import a new generated solution and let you know.
Thanks!
When deploy on the server, in case in the i18n_data folder there is also a second i18n file but with .txt extension instead of .properties, do you read also that file?
you mean there is also a i18n properties file with .txt extension, that is actually containing the old value ?
that may explain the problem
Yes, it was! But why do you read that one?
ah, ok, so that explains it all.
the importer does not expect to have other files then properties in the *.servoy file,
but the exporter just put all that it finds in the workspace in the /messages folder …
so, until we fix this, you could avoid to save other files in the /messages, but the correct
properties files
OK, so the importer ignores the extension or something like this … Anyway thanks! I wouldn’t figure it out if I haven’t discussed with you ![:)]( "Smile")
