Andrei
Forum Replies Created
-
Hello there,
Thanks for reaching out!
Unfortunately, changing the default language (the language the content is written in), will invalidate all the translations and for good reasons:
TranslatePress database design does not support this
re-writing the content in a different language will never be an exact match with the previously translated strings. Meaning just part of the translation will be recognized.
If you actually change the default language (something that’s perfectly fine on a brand new site without content), you’ll need to change all the content you’ve written to the new language and then translate again all the information. There is no proper way to automate this as translations are directional.
We understand this is not the best user experience and we’ll try to make it clearer in the future so the decision to pick a default language will be better discussed at the beginning of the project.You can change the first shown language (not the default language in which the content is written in) by simply going to TranslatePress Settings -> Enable Subdirectory for Default Language, then reorder the languages by drag and drop.
Best Regards
Hello there,
Thanks for reaching out to us about your issue!
Try and exclude the original from translation. Add a css class or target a parent of it in Advanced TranslatePress Settings.
Let me know if this shows any improvement to your issue.
Regards
Hello there,
My colleague did address your issue on the ticket that you mentioned and is currently investigating it.
We have been experiencing a large number of opened tickets in the last few weeks so please bare with us for the time being.
Let me know if you have any other questions.
Regards
Hello there,
Thanks for reaching out to us!
We deeply apologize for the delayed response.
There has been a great load on our support team in the past few days, but such a long reply time is very uncommon.
The SQL errors detected can occur for various reasons including missing tables, missing permissions for the SQL user to create tables or perform other operations, problems after a site migration or changes to SQL server configuration.
What you can do in this situation:
A.
Go to Settings -> TranslatePress -> General tab and Save Settings. This will regenerate the tables using your current SQL settings.
Check if no more errors occur while browsing your website in a translated language. Look at the timestamps of the errors to make sure you are not seeing the old errors. Only the most recent 5 errors are displayed.B.
If your problem isn’t solved, try the following steps:1. Create a backup of your database
2. Create a copy of each translation table where you encounter errors. You can copy the table within the same database (trp_dictionary_en_us_es_es_COPY for example) — perform this step only if you want to keep the current translations
3. Remove the trouble tables by executing the DROP function on them
4. Go to Settings -> TranslatePress -> General tab and Save Settings. This will regenerate the tables using your current SQL server.
5. Copy the relevant content from the duplicated tables (trp_dictionary_en_us_es_es_COPY for example) in the newly generated table (trp_dictionary_en_us_es_es) — perform this step only if you want to keep the current translations
6. Test it to see if everything is working. If something went wrong, you can restore the backup that you’ve made at the first step.
Check if no more errors occur while browsing your website in a translated language. Look at the timestamps of the errors to make sure you are not seeing the old errors. Only the most recent 5 errors are displayed.
C.
If your problem still isn’t solved, try asking your hosting about your errors. The most common issue is missing permissions for the SQL user, such as the Create Tables permission.Let me know if any of this help with your issue!
Kind Regards
Salut,
Imi pare rau pentru perioada lunga de timp pe care a trebuit sa o astepti.
Te rog sa deschizi un ticket aici mentionand aceasta conversatie ca sa putem analiza aceasta problema mai in amanunt.
Iti multumim pentru rabdarea acordata de pana acum!
Toate cele bune
Hey there,
I’m sorry for the long waiting time that you encountered.
Please feel free anytime to open another ticket here mentioning this conversation so we can have a better look at your problem at hand.
Looking forward to it!
Kind Regards
Hello there,
Thanks for reaching out to us!
Similar strings are stored as the same. The only thing you could do is create translation blocks with a different context. Basically wrap your text with
<span class=”translation-block”><span context=”event”>Unsere Räumlichkeiten</span></span>
<span class=”translation-block”><span context=”party”>Unsere Räumlichkeiten</span></span>This will allow you to have different context for the same string.
Kind Regards
Hello there,
Thanks for reaching out to us!
Here you have an example of some code meant to change the arabic font of a website. Go to Appearance –> Customize –> Additional CSS and add this code:
@import url('https://fonts.google.com/specimen/Almarai?subset=arabic#standard-styles'); body.translatepress-ar { //Use your language code from TP Settings --> General tab font-family:Almarai !important; }Please make sure that you delete the //comments before saving.
Best Regards
Hello there,
Thanks for reaching out to us about your issue!
Since this looks a lot like a conflict with some other code, the first/next recommended step is the conflict test (ideally in a staging environment):
*Briefly* disable all other plugins and enable the default Twenty Twenty theme. Please also disable all add-ons. If this fixes the problem, as it probably will, enable everything one by one, checking each time to see when the problem returns.
Please let us know when you find the conflict so that we can take a look and see what we can do about it.
Kind Regards,
Hello there,
Thanks for reaching out to us!
The structure that you are using is called Almost Pretty Permalinks(https://wordpress.org/support/article/using-permalinks/) which is not supported by our plugin and we don’t have support for this.
Try using full links and have another try.
Kind Regards
Hello there,
Thank you for reaching us!
You might have a bug or conflict with your current theme / plugins.
Can you please visit TranslatePress -> Settings -> Advanced
Then, enable these features 1 by 1 in this order and try to see if it makes a difference. Disable them back if it makes no difference. Also please disable or clear the cache if you have any.
1. Fix spaces between HTML attributes
2. Fix broken HTML
3. Fix missing dynamic content
4. Disable dynamic translation
5. Disable post container tags for post title
6. Disable post container tags for post content
7. Enable this plugin that disables execution of text widget shortcodes https://translatepress.com/download/1151172/Thank you for your patience so far.
Looking forward to your reply!
Kind Regards
Hey there,
If you want to manually translate those specific pages without having an automatic translation for them, your best approach would be to first translate those desired pages manually and only after that turn on automatic translation.
We assign a status to each translated string(not translated, manually translated, automatically translated) and manual translations have priority over automatically translations. If your strings are already manually translated when you turn on automatic translation they won’t suffer any changes.
Thank you for your patience so far!
Kind Regards
Hey there,
I was not successful in replicating this, would you mind sending the steps that you made in order to encounter this problem? Some screenshots would be greatly appreciated.
Kind Regards
Greetings,
Please feel free to open a ticket here , mentioning this conversation, so we can have a better look at your issue.
Kind Regards
Hey there,
Thanks for reaching out to us!
I tried to replicate the issue that you mentioned with no luck.
Would you mind sending me a link to where you encounter this problem? If not maybe some screenshots so I can better understand the issue at hand?
Looking forward to your reply.
Kind Regards