STOP translating EVERYTHING
-
So, after some days of debugging I found out why the second language page is always very slower. Apart from object cache having great problems, that I fixed. Now i found out this plugin is seriously badly written. How can you not give us the option to stop bloating the database with every possible string generated by the server? My dictionary and original strings tables are over 100MB while the (almost) only needed gettext table is 2MB. The dictionary and the original strings tables are like 80% full of links and 10% of useless strings that are never going to be translated by anyone. (Who even translates links and why would you bloat all our databases for this dumb feature in the first place). At least give us the option to stop generating hundreds of strings every minute. I had tried to delete all links and useless strings in the database, and later found out that almost all came back after a simple clearing and preloading of cache. At least give us a hook or a developer option. I have put all possible strings and links regexes in the current options and nothing works.
-
I have tried putting domains like https://www.google/*, my site, even https://* or whatever, tried /wp-content/ to stop generating infinite image links (like who even translates image url?) and doesnt work at all. A simple option to stop filling the dictionary and originalstrings table would be very good.
- Stop new translations
- Dont translate links
- Dont translate images
- Cleanup database from useless content.
At least the 1 is mandatory and shall be implemented soon, at least give us a hook or tell us the function in which all these strings are generated.
Also, a good addition would be to stop looking at dictionaries and original strings enormous tables on page generation time, that searches all this enourmous dictionary table and loads the translation that matches. This makes each page slower without good reason. Why wouldnt this plugin be simpler since 90% of people that use it, do it just to translate gettext strings, and use the language switcher. I just want only these and not a hundred more useless features that make every page slower.
Can the developers answer this topic? I have told you I have tested all possible advanced options, have gone through all documentation and searched all google, and at the same time I had automatic translation on? I am saying every string generated by site and even server (even open:atom urls are generated and i only use atom on filezilla) goes to original_strings and dictionary table and they have bloated completely the database with 95% of them being useless urls and image urls, this has nothing to do with translation apis, and of course i have it disabled.
I know about this data-no-transaltion thing, I didnt really understand if it was a joke or something, of course I am not going to put data-no-transaltion in all thousand urls or image urls that the site has, it may break things, hurt seo or whatever.
As mentioned in the documentation, the external links are detected for the possibility of changing the URL in a different language. We had a lot of users requesting this in the past, as well as image translation, so those were implemented.
So you ruined your plugin speed and didnt even think about an option of opting out of these, for the 0.1% of usage of translation, which is for images and external urls?
Another possibility is to have duplicate entries in your database which might affect your loading speed. You can use the Remove duplicate rows option from TP Settings –> Advanced tab to clear them and you should see improvements.
I have used this on staging site, several times, and it always has problems. It starts and never actually ends, of course I am not going to use it on production site. Also, i dont mind deleting all useless strings from database, I mind having them generated again after 10 minutes or something, as it has already happened.
The increased loading speed may be due to a lot of JS content. We have a listener for Javascript strings that when it detects a text change on the page (say a particular JS script adds a notice), we query the server for a translation. This ajax call is also fast as it doesn’t go through the normal WordPress ajax, however, it can be run intensively when there is a lot of traffic to your website. The good part is that you can disable this functionality from TranslatePress -> Settings -> Advanced tab.
I have told you many times, I am talking about TTFB or the time the server is generating the html document to send to the browser, on uncached pages, which is a lot due to the translatepress plugin. This has nothing to do with my javascript files and I have optimized them in any case. About the script you say, is it only for detecting changes on strings, or is it needed for fetching already translated strings from trp tables? Is it trp-translate-dom-changes.js? Update: This option disables dynamic tranlsation completely, even translated strings dont work. I just want to disable bloating the database.
Now, regarding your suggestions for improvement, our dev team will review them. However, the way WordPress environment works make it pretty difficult to separate different type of content, for example, to not detect a string at all if it has a link behind it. This may lead to wrong detection of the desired content which will cause other problems that are difficult to control. Okay, just create an option not to generate any new translation string at all. I have finished (as well as the 95% of users of this plugin) all translation and dont need all this slow functionality to run on each page, just give me the option to stop generating ALL types of new strings. If I want to continue translating, I can disable it, so simple.
To sum up, you are unable to fix anything, just tell me the file this string generation happens.
- The topic ‘STOP translating EVERYTHING’ is closed to new replies.
