excellent so far
I was invited to leave review. I have not used it a lot yet, but so far seems to be a very good complement for TranslatePress.
great …. that could be even greater
I use both the free and the paid version, depending on the project.The super great: – it compensates(corrects) the main translation plugin that gets every year more expensive. And their new internal translation so-called service is even more expensive. – there is a *brilliant* idea of using the translation in the frontend with free tools, to fill the backend DB. – the split of function between the free and the paid is acceptable, not making the free unusable.But there is also a feeling of "could do much more" for little effort (compared to what was done already): – **the slugs are not translated (would not be much complicated to incorporate the string in the translation table and manage the characters of slugs)**. This is very annoying, as this is what is submitted first to search engines, and later creates a 404 or needs a 30x. – in the paid version: too many clicks for nothing (when there is no choice, do not ask for clicking; NIKE=just do it! like selecting the language, merging, saving …) – it could automate all translations registered in the backend in one time, either by opening several pages/windows at the same time -one per language-, or one after the other with javascript miracles (what they do already) Tip for other users: do as me, a little PHP with AI coding –> a little shortcode that prints all the contents and custom fields of the latest "X" CPT/posts, in *one* post … so when I translate that 1 page, I translate 30 to 50 post contents in ONE time … then suppress that post with this shortcode, but translation of the 50 pages is in the DB. Edit: even greater with all the latest 1.8+ updates. Changed here to 5 stars (but I still regret the no slug translation)
has been working great for me
I have been using it for a while and works great and makes my work easier.
has been working great for me
I have been using it for a while and works great and makes my work easier.
great …. that could be even greater
I use both the free and the paid version, depending on the project.The super great: – it compensates(corrects) the main translation plugin that gets every year more expensive. And their new internal translation so-called service is even more expensive. – there is a *brilliant* idea of using the translation in the frontend with free tools, to fill the backend DB. – the split of function between the free and the paid is acceptable, not making the free unusable.But there is also a feeling of "could do much more" for little effort (compared to what was done already): – **the slugs are not translated (would not be much complicated to incorporate the string in the translation table and manage the characters of slugs)**. This is very annoying, as this is what is submitted first to search engines, and later creates a 404 or needs a 30x. – in the paid version: too many clicks for nothing (when there is no choice, do not ask for clicking; NIKE=just do it! like selecting the language, merging, saving …) – it could automate all translations registered in the backend in one time, either by opening several pages/windows at the same time -one per language-, or one after the other with javascript miracles (what they do already) Tip for other users: do as me, a little PHP with AI coding –> a little shortcode that prints all the contents and custom fields of the latest "X" CPT/posts, in *one* post … so when I translate that 1 page, I translate 30 to 50 post contents in ONE time … then suppress that post with this shortcode, but translation of the 50 pages is in the DB. Edit: even greater with all the latest 1.8+ updates. Changed here to 5 stars (but I still regret the no slug translation)
great …. that could be even greater
I use both the free and the paid version, depending on the project.The super great: – it compensates(corrects) the main translation plugin that gets every year more expensive. And their new internal translation so-called service is even more expensive. – there is a *brilliant* idea of using the translation in the frontend with free tools, to fill the backend DB. – the split of function between the free and the paid is acceptable, not making the free unusable.But there is also a feeling of “could do much more” for little effort (compared to what was done already): – **the slugs are not translated (would not be much complicated to incorporate the string in the translation table and manage the characters of slugs)**. This is very annoying, as this is what is submitted first to search engines, and later creates a 404 or needs a 30x. – in the paid version: too many clicks for nothing (when there is no choice, do not ask for clicking; NIKE=just do it! like selecting the language, merging, saving …) – it could automate all translations registered in the backend in one time, either by opening several pages/windows at the same time -one per language-, or one after the other with javascript miracles (what they do already) Tip for other users: do as me, a little PHP with AI coding –> a little shortcode that prints all the contents and custom fields of the latest “X” CPT/posts, in *one* post … so when I translate that 1 page, I translate 30 to 50 post contents in ONE time … then suppress that post with this shortcode, but translation of the 50 pages is in the DB. Edit: even greater with all the latest 1.8+ updates. Changed here to 5 stars (but I still regret the no slug translation)
has been working great for me
I have been using it for a while and works great and makes my work easier.
great …. that could be even greater
I use both the free and the paid version, depending on the project.The super great: – it compensates(corrects) the main translation plugin that gets every year more expensive. And their new internal translation so-called service is even more expensive. – there is a *brilliant* idea of using the translation in the frontend with free tools, to fill the backend DB. – the split of function between the free and the paid is acceptable, not making the free unusable.But there is also a feeling of "could do much more" for little effort (compared to what was done already): – **the slugs are not translated (would not be much complicated to incorporate the string in the translation table and manage the characters of slugs)**. This is very annoying, as this is what is submitted first to search engines, and later creates a 404 or needs a 30x. – in the paid version: too many clicks for nothing (when there is no choice, do not ask for clicking; NIKE=just do it! like selecting the language, merging, saving …) – it could automate all translations registered in the backend in one time, either by opening several pages/windows at the same time -one per language-, or one after the other with javascript miracles (what they do already) Tip for other users: do as me, a little PHP with AI coding –> a little shortcode that prints all the contents and custom fields of the latest "X" CPT/posts, in *one* post … so when I translate that 1 page, I translate 30 to 50 post contents in ONE time … then suppress that post with this shortcode, but translation of the 50 pages is in the DB. Edit: even greater with all the latest 1.8+ updates. Changed here to 5 stars (but I still regret the no slug translation)
great …. that could be even greater
I use both the free and the paid version, depending on the project.The super great: – it compensates(corrects) the main translation plugin that gets every year more expensive. And their new internal translation so-called service is even more expensive. – there is a *brilliant* idea of using the translation in the frontend with free tools, to fill the backend DB. – the split of function between the free and the paid is acceptable, not making the free unusable.But there is also a feeling of “could do much more” for little effort (compared to what was done already): – **the slugs are not translated (would not be much complicated to incorporate the string in the translation table and manage the characters of slugs)**. This is very annoying, as this is what is submitted first to search engines, and later creates a 404 or needs a 30x. – in the paid version: too many clicks for nothing (when there is no choice, do not ask for clicking; NIKE=just do it! like selecting the language, merging, saving …) – it could automate all translations registered in the backend in one time, either by opening several pages/windows at the same time -one per language-, or one after the other with javascript miracles (what they do already) Tip for other users: do as me, a little PHP with AI coding –> a little shortcode that prints all the contents and custom fields of the latest “X” CPT/posts, in *one* post … so when I translate that 1 page, I translate 30 to 50 post contents in ONE time … then suppress that post with this shortcode, but translation of the 50 pages is in the DB. Edit: even greater with all the latest 1.8+ updates. Changed here to 5 stars (but I still regret the no slug translation)
Does not work
Scam
gint2333
April 7, 2026
|
2 replies
Funciona bem.
Me incomodou o alerta para fazer uma avaliação porque gerou erros no meu painel e eu não consegui de forma alguma clicar na opção de não avaliar.
Alex Carneiro
November 5, 2025
|
1 reply
great …. that could be even greater
I use both the free and the paid version, depending on the project.The super great: – it compensates(corrects) the main translation plugin that gets every year more expensive. And their new internal translation so-called service is even more expensive. – there is a *brilliant* idea of using the translation in the frontend with free tools, to fill the backend DB. – the split of function between the free and the paid is acceptable, not making the free unusable.But there is also a feeling of “could do much more” for little effort (compared to what was done already): – **the slugs are not translated (would not be much complicated to incorporate the string in the translation table and manage the characters of slugs)**. This is very annoying, as this is what is submitted first to search engines, and later creates a 404 or needs a 30x. – in the paid version: too many clicks for nothing (when there is no choice, do not ask for clicking; NIKE=just do it! like selecting the language, merging, saving …) – it could automate all translations registered in the backend in one time, either by opening several pages/windows at the same time -one per language-, or one after the other with javascript miracles (what they do already) Tip for other users: do as me, a little PHP with AI coding –> a little shortcode that prints all the contents and custom fields of the latest “X” CPT/posts, in *one* post … so when I translate that 1 page, I translate 30 to 50 post contents in ONE time … then suppress that post with this shortcode, but translation of the 50 pages is in the DB.
fff654
December 8, 2025
|
1 reply
