You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted for hreflang to use language code that is stored inside "Locale at front-end" field located inside individual Language qTranslate-X Settings page, but couldn't make it to work.
It turns out this is due to the qtranslate-slug removing the ''wp_head'' action of qTranslate-X and replacing it with it's own which is ignoring the "Locale at front-end" field. I think this is due to the #25 issue.
If I comment out the code in qTranslate-Slug that replaces ''wp_head'' action of qTranslate-X with its own, the "Locale at front-end" field works. At the same time, the URL slugs also get converted, so I'm not sure what does #25 solve or if it is even needed anymore (at least with the current version of qTranslate-X).
The text was updated successfully, but these errors were encountered:
I wanted for
hreflang
to use language code that is stored inside "Locale at front-end" field located inside individual Language qTranslate-X Settings page, but couldn't make it to work.It turns out this is due to the qtranslate-slug removing the ''wp_head'' action of qTranslate-X and replacing it with it's own which is ignoring the "Locale at front-end" field. I think this is due to the #25 issue.
If I comment out the code in qTranslate-Slug that replaces ''wp_head'' action of qTranslate-X with its own, the "Locale at front-end" field works. At the same time, the URL slugs also get converted, so I'm not sure what does #25 solve or if it is even needed anymore (at least with the current version of qTranslate-X).
The text was updated successfully, but these errors were encountered: