Translate - on demand translation of user content

IanM

Syirrus how well does this play with SEO? Do the cached translation turn into SEO juice as in if a post is in English and then cached and translated into Spanish for example, can Google see the Spanish translation of the post?

There's currently no integration with SEO directly

Syirrus Also, does this translate Primary and secondary tags?

No, this extension focuses on the translation of user content only. Localizd by @glowingblue is the only extension I'm aware of to offer tag translations

Syirrus

IanM Thank you for responding to my questions 🙂. In your opinion, is your plug pretty stable? It looks like an awesome plugin I'm thinking about picking up.

IanM

Syirrus yes, on the whole the extension is pretty stable and is in use on a few production sites.

There is currently an issue with increased latency when the DeepL driver is in use, which I plan to release an update to address soon. The current workaround is to use either the Google Translate or Google Cloud Translate drivers, which do not cause this issue.

Syirrus

IanM Thank you very much again.

Syirrus

kebindong IanM

I just picked up this extension and it’s great! It’s very clean and seamlessly works as well so far with my limited testing. It’s there, but you don’t notice it unless you need it. Thank and well done for sure!!!

I wish it had tag translation support and translation support for Titles, but it’s more important to translate the comments and posts.

Thank you again for this awesome extension!

Syirrus

IanM

How much would it cost to implement a few additional features into your translate plugin?

The ability to translate the subject.
The ability to hide and show translation(s) (already cached in the DB) below the post for SERP?
Bonus: the ability to localize tags.

Syirrus

IanM Has the bug for the DeepL latency issue been addressed? Just curious.

kebindong

IanM Im not lucky, I missed this promotion.. hope this deal come again in Christmas..

Syirrus

I noticed there is a tag based permission issue when it comes to NOT being able to grant or restrict access based on "tags" access to the translate plugin based on tag.

You cannot click on or rather set any permissions based on tags.

IMAGE

IanM

Syirrus I noticed there is a tag based permission issue when it comes to NOT being able to grant or restrict access based on "tags" access to the translate plugin based on tag.

You cannot click on or rather set any permissions based on tags.

This is correct. The permissions to translate content is forum wide, rather than scoped for tags.

Syirrus The ability to translate the subject.

I am planning to introduce this feature soon 🙂

Syirrus The ability to hide and show translation(s) (already cached in the DB) below the post for SERP?

I'm not sure I understand what you mean here?

Syirrus Bonus: the ability to localize tags.

Translation of tag display names is out of scope for this extension. Localizd by @glowingblue offers this functionality if you need it

Syirrus

IanM

IanM This is correct. The permissions to translate content is forum wide, rather than scoped for tags.

I understand.

IanM The ability to translate the subject.

Right on! That would be awesome if it's a easy change.

IanM The ability to hide and show translation(s) (already cached in the DB) below the post for SERP?

I was thinking something that showed the following:

TITLE There is the original text in English.

TRANSLATED TITLE Here would be the text in another language

TRANSLATED TITLE And yet more text in another language

These boxes (not coding text boxes) would be collapsable in CSS (collapsed by default) with the subject being translated title. So you wouldn't see the translated text below.

If someone wanted to see the translations, they could click translated "title" and see the whole translation. This would also make it so these translations would be picked up by Google.

Does that make sense?

IanM Translation of tag display names is out of scope for this extension. Localizd by @glowingblue offers this functionality if you need it

Yes, the price for that extension is prohibited, making it not an option for my project.

Syirrus

kebindong It's not only for admins. Depending on the permissions and user language localization normal users can translate posts.

kebindong

Syirrus Thank you.
for testing, I set permissions of View translation in current locale to Everyone, and View translation in any forum locale to Members. and log in a testing role in my same device. But the testing role cannot see the translate dropdown menu in post. and my admin role can use it only. Im not sure which parts wrong.

Can I see your site if you dont mind..

thanks

Syirrus

kebindong Were you able to solve this? My forum site is still in testing and I'm not quite ready to share just yet. Do you have the user locale set when the log in, because if the users locale is set to the language the text is in, you won't see the translate button.

kebindong

Syirrus thank you, I go test the users locale

Syirrus

@IanM
I'm unable to update to 1.6.3 (minor update) because of the translate package.
I get the following error:


  Problem 1
    - Root composer.json requires ianm/translate ^0.2.1, found ianm/translate[0.2.1] in the lock file but not in remote repositories, make sure you avoid updating this package to keep the one from the lock file.```

Is there a way to resolve this?

IanM

Syirrus the error here usually means that your Extiverse token has expired, or Extiverse cannot be reached for some reason..

Syirrus

IanM Thank you, updating my token did the trick.

kebindong

IanM Hi, only Admin role can see the translate drop down menu in my site, even I already set permissions "View translation in any forum locale" and "View translation in current locale" to all everyone. Do you know how to fix that.
Thanks.

IanM

Syirrus Has the bug for the DeepL latency issue been addressed? Just curious.

Apologies, no I've not addressed that yet. Normal service from me is now back, so I'll tackle this ASAP

kebindong Hi, only Admin role can see the translate drop down menu in my site, even I already set permissions "View translation in any forum locale" and "View translation in current locale" to all everyone. Do you know how to fix that.
Thanks.

Usually this happens if the detection command has not been completed. Did you run php flarum translate:detect and allow it to complete?

kebindong

IanM Hi, as last time it didn't work well in my site, and I re-subscribed your extension again on this month.
**My site is : flarum 1.7.2; PHP 8.1; Queue driver: redis; Session driver: redis; Languages: English and Simple Chinese **

But there is still a problem about the permission I think;

IanM Did you run php flarum translate:detect and allow it to complete?
Firstly, I run detect command twice until it detected all posts in my site.

secondly, about permissions I set:

View translation in current locale: Everyone
View translation in any forum locale: Members
Force a re-translate of a cached translation: Admin

It works okie if I use Admin, I can click language button on right corner of a post to translate .
For other groups, it works ok for "PostMeta PostTranslation--meta", it can display "This post is in..." if post use different languages. But the other groups cant see the "language translation button" on right corner.

Update......
It works on new posts..

I think the " php flarum translate:detect" really didn't complete in my .. But when I run the cli again, it shows:

/var/www/flarum# php flarum translate:detect
Detecting languages of posts un-identified language using driver 'google-free' No posts to process

« Previous Page Next Page »