SteveW928

Thanks, I just don’t have enough coding experience to tackle such a project. I understand your concerns over complexity. I also understand that this is theme specific. I’d only note that from what I’ve seen, an increasing number of themes and users are going to run into such an issue.

No, unfortunately 6.0.14 did not resolve the issue. The behavior is the same as with 6.0.13. Thanks for your effort on this!

@ vinx77
I thought about that initially, when the client brought up the multilingual idea (before doing any research). I’m sure that would work, but would be quite a mess to maintain. A better solution is probably the WPML plugin. However, there is an associated cost (for most) and when I looked into it, it seemed rather complex to get going compared to qTranslate. That may have changed, and I intend to look into it again.

It seems clear that Yoast isn’t going to officially work with qTranslate, as they won’t even answer these kind of questions. It seems it does work with WPML, from what I’ve read… so I guess that must be about as official word as they are going to give us. (I have no clue why they can’t give us a better answer… there must be some kind of politics or egos involved, etc. Sigh.)

Just a note: The theme I’m using uses the WordPress ‘static page’ for the front page, which uses the theme’s custom ‘Page Builder’ to layout and construct the front page using a WordPress ‘Page.’ I’m not sure if that would make a difference.

That said, I had been using a previous version of CJT, v0.8 without any problems on this site and another using a similar theme. The other site has a number of code-blocks, though I’ve left that one at 0.8 for now. This site, I had just installed the plugin in anticipation of using it, so I wouldn’t forget. When I upgraded to v6.0.13, that is when the pagination issue began.

Hi Ahmed,

I didn’t have any code blocks, except the default one. I tried (if I did it correctly) your above steps, and it didn’t seem to make any difference with pagination.

@ Tamara-IT – Money isn’t so much the problem (at least for my situation, as my client is a non-profit… free version available), as is implementation and support. I should check back again, but last I looked, WPML seemed like a good amount of work (both implementation and ongoing). I’d love to hear I’m wrong on that!

And, since qTranslate seems like such a simple solution for low-budget or low amount of effort type applications, I’d love to know more than, ‘I won’t support it.’ And, what solutions would be recommended to best fit with Yoast.

Thanks francesco1119, good information. I’m a bit scared of that WP-i18n you mention, as it doesn’t look like much is going on with it. I’m not opposed to paying for WPML (or, rather I doubt my client is… and they probably even qualify for the free non-profit version) but it looked like a good bit of work to get going and maintain, and overkill for what they need, other than SEO compatibility. They really just need to provide an alternate language version of some of their blog posts.

qTranslate just looked so simple in comparison, and a good fit. But, if it is problematic, than we wouldn’t want to go that route either. I was really just hoping for some feedback from Joost, aside from… we won’t support it.

I do like the idea of a separate page for each language for everything, if it isn’t too hard to get going and maintain. How was your experience in that regard? Maybe I need to take another look. (I seem to recall that it looked like a good bit of coding work to implement back when I checked… and administrative work to maintain the linkage between all the versions of the same article/page.)

@ Beee –
It just seems like a more appropriate question to be asking of Joost than the qTranslate author. It doesn’t seem like qTranslate could add Yoast support, but more like Yoast would need to add some fields or a stable way in for qTranslate.

And given the popularity and need for some kind of solution that isn’t overly complex (which this would seem to be about it), it would be nice to have some kind of explanation. Is it just technically too difficult? Does Joost think there isn’t enough interest? Is qTranslate a really buggy solution? Is there a developer spat going on between these authors? etc. Does Joost recommend some other solution?

Thanks Kurt. I was a bit confused by that result, but pleased overall. I figured it was maybe just because of all the Jetpack modules (like a bunch of plugins). But, I was also thinking… Jetpack is by the WordPress people, for cryin’ out loud! ?? I’ll have to try that manual scan if I can figure that out.

Hello all, I thought I’d post my results… maybe some others could do the same, so folks have some points of comparison.

I’m on a pretty fast server, and got better results than the sample screen shots (not sure if the samples are at all typical or not). The server is a quad-core workstation class box with only a few sites on it and lots of RAM (though we’ve not optimized apache or php, etc. outside the default settings yet).

Total plugins: 21
Plugin load time: 0.296
Plugin impact: 64%
MySQL queries: 89

Interestingly, almost 60% of my plugin time is Jetpack (with the rest being pretty tiny slices). I’m using several of its modules, so I’m not sure I can easily ditch it. But, since the overall results don’t seem too bad, maybe I’m fine just leaving it alone.

On a second run, things changed to:
Total plugins: 21
Plugin load time: 0.198
Plugin impact: 49.6%
MySQL queries: 91

Jetpack about about 40%

Be sure to look back for the ‘hack’ threads. While I’m not a programmer, it didn’t actually look all that difficult. The big problem, it seems, is that the target keeps moving. Also, maybe I’m mistaken, but wouldn’t the big SEO things be the title and meta descriptions? It would seem like Joost could add a category of fields for multilingual use, and then just provide a stable path in for plugins like qTranslate. (qTranslate META already exists to create such fields, but conflicts with Yoast on my understanding.)

Maybe someone would even have to build a bridge type plugin (kind of like qTranslate META) to Yoast if the qTranslate folks didn’t do it directly, but at least if it were a stable path in, the target wouldn’t keep moving. I can certainly understand Joost not wanting to start fully supporting all sorts of various other plugins… but that doesn’t seem to be needed, at least as far as I can see.

Joost’s site (and page on WordPress) is quite helpful too:
https://yoast.com/articles/wordpress-seo/

It seems the official response is no **, but some folks seem to keep hacking some kind of integration unofficially (which seems to break with updates). This forum doesn’t have a very good search, but if you just keep paging back in time and searching the page text of WordPress SEO for titles that include qTranslate, you should find a number of threads where it is discussed. (I haven’t personally tried it yet.)

I’m probably going to implement qTranslate for one client, but I’m not sure I’m going to try to integrate it with SEO at this point. I hate to provide a solution that just keeps breaking. That said, qTranslate seems to be the only option that is reasonable for them to implement. I wish there were some decent option for this.

** Joost says he doesn’t and won’t support it, but I’ve never seen an explanation (even a brief one) and threads which ask seem to get avoided (I’ve tried a few times).

See:
https://www.ads-software.com/support/topic/plugin-wordpress-seo-by-yoast-multilingual-site-titling-in-all-languages?replies=8

@mvandemar
I’m not sure what the protocol for releasing an update is, but I’d also add that it would be a good idea to get rid of the ‘not updated in 2 years’ banner, as that will make people pass by it (I almost did). Also, some of the security plugins and services are now using plugin-age as a metric to flag problems.

But, my question I wanted to ask…
Will this also apply to XMLRPC for remote publishing? I’d really like to turn that feature on, but don’t want this to be a weak point for hackers.
Thanks!

I’m having a similar problem as well. Google seems to be just pulling something from my ‘about’ page or other various places on my site, depending on the search terms used. It doesn’t seem to be pulling the meta description anywhere I’ve seen yet (it has crawled my site). It has updated the titles and such, so I know some of what I’ve put into Yoast SEO is working. Also, the title and description are showing up as I’d expect in Bing, so this just seems to be a Google thing.