#3489 - More translate issues

By Adam Edington
Added 18th Jan 2018, 2:29 AM
2 views

Identifier	#3489
Issue type	Trivial issue (does not break functionality)
Title	More translate issues
Status	Completed
Handling member	Chris Graham
Addon	core_language_editing
Description	Issue clicking the little icon which uses Google Translate resulting in a 403 error on my live website (not localhost). Also, "There is more that can be translated (3,708 records)" but I'm only been shown less that 20 strings and page 3 is blank. Somewhat similarly, the search results (approximate amounts) also seem errenous in the same way, large numbers stated but nothing to show.
Steps to reproduce
Funded?	No

The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".

Rating

Unrated

Comments

By Guest posted 18th Jan 2018, 2:29 AM

By Guest posted 18th Jan 2018, 3:01 AM

Meta Keywords are not saved against a specific language, perhaps they should be if the rest of the content has been translated.

By Guest posted 18th Jan 2018, 11:57 AM

"Issue clicking the little icon which uses Google Translate resulting in a 403 error on my live website (not localhost)."

Google have stopped supporting non-AJAX translation from translate.google.com. On review, bing.com has also. Supporting other translation services would be a lot of work anyway.

So I'll have to remove this feature.

We still retain a hidden feature for those who have purchased a Google Translate key.

"Also, "There is more that can be translated (3,708 records)" but I'm only been shown less that 20 strings and page 3 is blank."

If you read the error message in full it addresses this:
There is more that can be translated (<strong>{1}</strong> {1|record|records}). We only looked up the highest priority <em>{2}</em> records that have not yet been translated or have outmoded (broken) translations.

So the message states that not everything is going to be shown then states what is shown.

"Somewhat similarly, the search results (approximate amounts) also seem errenous in the same way, large numbers stated but nothing to show."

Are we talking front-end website search? Back-end admin search? Searching language strings?
I suspect you mean front-end website search, which would be a separate issue. The prior mentioned issue has nothing to do with mis-counting, so is not related.

"Meta Keywords are not saved against a specific language, perhaps they should be if the rest of the content has been translated."

I am looking at this.

By Guest posted 18th Jan 2018, 3:29 PM

Ahh that's a shame, but it's just as easy to load the website and copy/paste translations in my opinion.

Yes, so if I wanted to translate strings (and there are 3,708 with only several shown) how do I got about finding all the others when the pagination is void of content? Am I supposed to be editing the actual ini files rather than using the backend?

The erroneous number of search results are on the front end (specifically with following the links generated by Meta Keywords), though this may be due to the MySQL thing you once mentioned where you need X amount of that search term for it to actually work correctly. Either way, it looks similar to the Translation results with additional pagination containing nothing.

By Guest posted 18th Jan 2018, 5:12 PM

"Yes, so if I wanted to translate strings (and there are 3,708 with only several shown) how do I got about finding all the others when the pagination is void of content? Am I supposed to be editing the actual ini files rather than using the backend?"

If you can't see it, you shouldn't worry about it. It could be very benign stuff like forum posts, which are entered with a low translation priority.
There's no UI for scrolling through everything because I feel anyone using such a UI would just get depressed seeing all the low-level stuff they don't care about being in the queue.