leslierad

@joostdevalk, Thanks for taking the time to reply,

While you do have several valid points, the main one being don’t use my plugin, that view point while you are entitled to it, will not help your ratings in the long term, unfortunately.

Playing nicely with other plugins (or at least pretending to) is surely a rating factor when one assesses a plugin for a review. (header and footer plugin – also springs to mind)

The extent of the “damage” done, in this instance is reflected in my review rating stars, along with the fact that I tried ver.3 WPSEO on launch with several non-qtranslate websites and it was full of ads and extra unwanted services, on top of that, it didn’t work and was a disaster, it seemed that it was released in alpha version that hadn’t been tested adequately.

Surely a plugin author would want their plugin to be as compatible as possible with as many other plugins as possible, trying to find solutions when they appear unattainable, working together with other developers to ensure cross compatibility, listening to user reports of issues, putting functionality before profit, after all that is what the wordpress community is meant to be about – I guess

I know there is no point going on about this, but just a real quick response to some points.

From Qtranslate-x version 3.5 onward the plugin offers a choice to “Split database file by languages” for option “Convert Database”, which allows to split .sql database file of multilingual site into separate single-language database files.

Support of one language per install would more than suffice for most users, or sell a pro plugin to enable more languages to compensate for the additional query’s.

The server back-and-forths, would probably be non-existent with your assistance as that can all be done pre-fetch on the host website.

I for one would buy several licenses for pro even for 1 language support as I’m sure many others would.

There is also a plugin to remove qtranslate, I have never tested it so can’t say if it works or not but it was recently updated https://www.ads-software.com/plugins/qtranslate-to-wpml-export/

Some more reasons:

All 20,000 active installs use ver 2.3.5 I see your stats are about 37% other versions, so if WPSEO worked with qtranslate-x the number would decrease.

You would get more new installations over time

Your rating rankings would improve as many qtranslate-x users were peeved and would be delighted if it was supported.

The list goes on and on, but anyway….. No hope of that !!

Thanks for your reply! Just an FYI your knowledge base article about qTranslate X is actually about qtranslate, many things changed with qtranslate x making that knowledge base close to being irrelevant.

Of course I have the integration plugin active, I helped the author test several features of the plugin but it currently only supports up to wpseo ver 2.3.5 https://www.ads-software.com/support/topic/help-wanted-3/

Yoast may want to have a look at the changes and/or create a similar plugin or at the very least support it, it also seems that the plugin author has stalled development hence providing opportunity.

Why Yoast should support qtranslate-x

• – has 100,000 + active installs itself excluding other flavors
• – has 20,000 + active installs of the wp-seo addon, imagine if it actually worked with wpseo latest versions
• – AIO SEO addon only has 10,000 + active installs
• – Language translation is vital to many online businesses
• Qtranslate-x is a whole lot more refined than the original qtranslate
• – People are stuck with qtranslate variants forever, there is no alternative other than removing content entirely.
• – How hard could it really be?

More
Here is the support and issues list if you really want to dig a bit deeper https://www.ads-software.com/support/plugin/wp-seo-qtranslate-x

• This reply was modified 8 years ago by leslierad. Reason: fixed
• This reply was modified 8 years ago by leslierad.
• This reply was modified 8 years ago by Samuel Wood (Otto). Reason: Really fixed. Put UL's around LI's

Sorry my rating remains the same, as I am still using sub 3 version, due to qtranslate-x incompatibilities with yoast and the refusal of co-operation so far.

Please use the support section, this is the review rection ??

Bit harsh rating when you know https://www.ads-software.com/support/profile/nicoblog the issues with wp-seo right now.

Doug, Yoast versions over 3.0 don’t work try:
https://www.ads-software.com/support/topic/language-switcher-doesnt-change-meta-content?replies=4

Also see complaints:
https://www.ads-software.com/support/view/plugin-reviews/wordpress-seo?filter=1

It may not be worth updating the plugin right now as Yoast may change it again soon.

Also see stats of version usage:
https://www.ads-software.com/plugins/wordpress-seo/stats/

Many are still using v2.35 actually more than use 3.0+

If you want to update the plugin yourself its available on github and I’m sure John will approve any positive changes you can make.

Use Yoast v2.3.5 for now, it makes no sense fixing this plugin until yoast stop making changes https://www.ads-software.com/support/topic/language-switcher-doesnt-change-meta-content?replies=3

Feel free to open a support ticket instead of a review, usually you will get better support.

Hi, you failed to mention the versions you are using but this may help:

There is currently an issue with Yoast SEO v 3.0 and upwards with
Yoast SEO & qTranslate-X

https://qtranslate-x.com/support/index.php?PHPSESSID=h7rub5u9ufll703qufgc6mnu76&topic=58.0

it does not work, several changes were made and Yoast SEO & qTranslate-X needs to be updated which may take a while as Yoast may need to change itself as there are many complaints, the solution for now is use Yoast v2.3.5 https://downloads.www.ads-software.com/plugin/wordpress-seo.2.3.5.zip which works fine, until this plugin gets updated.

Did you try:
https://www.ads-software.com/support/topic/seo-and-metadescriptions-are-mixed-in-the-two-languages-i-use?replies=15

Settings – Languages – Integration – Configuration Files

plugins/wp-seo-qtranslate-x/i18n-config.json was missing.

Deactivae Yoast SEO & qTranslate-X, then you get a message:

Plugin Yoast SEO may be integrated with multilingual plugin qTranslate-X with a help of plugin Yoast SEO & qTranslate-X.

Activate Yoast SEO & qTranslate-X again.

Then you get another message:

Option “Configuration Files” for plugin qTranslate-X has been auto-adjusted after recent changes in the site configuration.

Configuration Files are now updated with the correct files.

The blue lines are now back for the Seo and metadescriptions fields and everything works as it should.

You can also try https://www.ads-software.com/plugins/wp-seo-qtranslate-x/ with yoast seo sitemap is now built in works with slug too.

Glad, it works ?? has a look everything seems fine, the Macedonian sitemap looks scary but guess that’s all the special language characters.

Site.com was as an example if you need www or https then obviously you needed to change the example to fit your requirements, it seems that you fixed that issue though, regarding your sitemap redirects you should add all the language redirects you wish to use prior to the final sitemap.xml redirect like redirect /fr/sitemap.xml /de/sitemap.xml then last line should be the final sitemap.xml redirect the reason for that is because sitemap.xml is a match to any other language, if that makes sense, am posting this from my phone so It’s harder to explain properly, if that info doesn’t help you so long I will add more on Monday.
You can robot block too if you wish to but that’s an additional option, it will not resolve your issue, your issue with the redirects is the order in which you have written them in that they match even when the /fr/ is in the url.
Check the github post and under the heading
As it stands now my guess is that users who have used the sitemap_index.xml url previously may be best off to:
you will see an example of the order of the redirects languages /fr/ etc the last one sitemap.xml to prevent early matches there is also a robot exclude example.

It’s more than likely your meta descriptions etc are still in your database, make a backup of the db before attempting anything else, then try downgrade to older versions of both plugins. If your meta data is visible after that you could try to update again. If that doesn’t work you may require the plugin author (John’s) help,you could open a ticket on github and he could advise you best. I’m pretty sure the meta data is still intact.

If you want to add a redirect,try this format:

RedirectMatch 301 /sitemap.xml https://site.com/i18n-index-sitemap.xml
If you had language sitemaps previously you can add.

RedirectMatch 301 /de/sitemap.xml https://site.com/de/i18n-index-sitemap.xml
RedirectMatch 301 /da/sitemap.xml https://site.com/da/i18n-index-sitemap.xml

Near the top of .htaccess i.e. prior to begin wordpress at least.

Your other issue appears to be related to browser redirection based on language https://qtranslatexteam.wordpress.com/2015/02/26/browser-redirection-based-on-language/ don’t worry about that robots don’t have cookies set like browsers do, so it should be fine.