Slugs question
-
Thanks for your initiative on this new fork!
My main concern is getting the “category” slugs working for taxonomies or any taxonomy fields.
Or simply make a fix for “Qtranslate Slug” to work with qTranslate-X 😉
Are you up to that
-
Thanks a lot, Pedro and beheist!
You have a extra ?>
Which line and file, if you would have time to lookup? What made you to discover it?
I will have a lot of modifications on next release, it might be gone by now. I turned on WP_DEBUG and found a few other imperfections too – cleaning it up now.
You are right, I still did not have time to set github up, but I will certainly do this soon.
GitHub for qTranslate-X is now available:
Hi, thank you both for your work on qtranslate-x and slug.
I had 2 changes to make in the code of slug contrib from github :
File includes/class-qtranslate-slug.php line 739 in order to remove an unidefined value
if ($GLOBALS['q_config']['url_mode'] == 2) {
file includes/class-qtranslate-slug-widget.php line 49
$short_text = (isset($instance['short_text'])) ? $instance['short_text'] : '';Hi everyone!
@john Clause, i think you found the extra “?>”!
I think our new release made it compatible with yours, thanks to everyone who made it possible!
@bteboul, did you find any error in
includes/class-qtranslate-slug-widget.php line 49?This sounds great. I am so glad you got it working so quickly.
I personally did not see a reason to translate slugs before and I never bothered with that, but I now see that there is a lot of people who want this. Would it give you any SEO advantages? I do not see how, but if it would I may start using it now too 😉
I noticed a few things.
I still get this message without -X mentioned on the first install:
Qtranslate Slug: This plugin requires at least WordPress 3.3 and either mqTranslate 2.6.2.4 (or newer) or qTranslate 2.5.8 (or newer)which made me think that it does not work yet, but then I realized that qTranslate-X was off at that time. After activating it, the message disappear. I think it would be nice to put installation/activation links in that message, but it is not important.
After deactivating and reactivating I got:
The plugin generated 252 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.Probably an effect from other plugin or theme. I had WP_DEBUG on at that time. I did not troubleshoot it. It was one time message after re-activation.
@eirikv: Is this topic resolved for you now?
Thanks a lot to everyone!
Would it give you any SEO advantages?
Yes, you get to put keywords on the url in the right language.
I’ll try to fix the notice, and as for the message, i got it too, but didnt have time to fix it. thanks for the report.
Hi Pedro,
@bteboul, did you find any error in includes/class-qtranslate-slug-widget.php line 49?
Yes i did find that the value is related to a form checkbox that is not set if not checked so it warn us about the undefined value, the isset test allow us to get rid of this warning without side effect.
I did find a bug in the taxonomy backoffice, wp-admin/edit-tags.php?taxonomy=category that seems to break the taxonomy form.
Warning: call_user_func_array() expects parameter 1 to be a valid callback, function 'qtranxf
I’ll try to have a look asap and hold you inform.Thanks again
@eirikv: does the latest version work for you? All problems seem to be resolved.
Hello all,
I see this post is marked as [resolved]..
Sorry to ask. Is “qtranslate slug” and “qtranslate-x” compatible then?I see qtranslate slug does not figure on the list of compatible plugins nor has an integration plugin on the qtranslate-x github page.
Considering the classes need to be different for each plugin, I don’t understand how qtranslate slug, or any other, such as “ACF qtranslate” could be working for both qtranslate and qtranslate-x at the same time.
On the other hand, on that same github page I see that already on version 2.9.7.7 beta we find “compatibility with Qtranslate Slug” is a marked item.
Finally, when installing qtranslate-x from the wp-dashboard (Version 3.2.9), I get no messages when installing qtranslate slug. However, when installing the latest version from the Github page (Version 3.2.9.9.0), qtranslate slug now says that it requires at least WordPress 3.3 and either qTranslate-X (2.9 or newer), or mqTranslate (2.6.2.4 or newer), or qTranslate (2.5.8 or newer).
As to my personal need, I still could not figure out a way to have complete permalink paths translated, for SEO purposes.
I was enjoying the idea of using the “custom permalinks” plugin for my website, setting specific permalink paths for each product/page/post.
It would be great if qtranslate-x could allow us to set different custom permalinks for each language (integration with this plugin).
However, since this discussion is about the plugins qtranslate slug and qtranslate-x, I have tried deactivating the above plugin and by using these two plugins only, obtain the result I’m looking for, with no luck.
It is not clear to me how I could have, for example:
http://www.brasilautentico.com/product/gourmet/romantic-dinner (EN) and
http://www.brasilautentico.com/br/produto/gastronomia/jantar-romantico (BR)Any help would be greatly appreciated.
Thanks a lot!
Gabriel
did you download the latest Beta version of qTranslate X? Version 3.2.9.9.0
See my other answer to you.
Did you install the latest version of qTranslate Slug? Version 1.1.16
Did you tested it?
/product/gourmet/romantic-dinner (EN) and
/br/produto/gastronomia/jantar-romantico (BR)Product is a categorie? Gourmet is a sub-categorie?
If so, under – Post – Categories – translate your Categories
Use qTranslate Slug for both, the page name jantar-romantico and romantic-dinner
Hi Gunu,
Thank you very much for being so helpful and trying to help me.
I was able to make it work by not using the latest version of qtranslate-x from Github but the version provided by the WP Dashboard 3.2.9.
After several tests and small changes to the structure, I am being able to populate almost everything as I wanted.
The only question I still have is regarding the products, which I was intending to show as: websitename.com/shop/%prod_cat%/product-name
The exact same question has been posted here: https://wordpress.org/support/topic/woocommerce-and-category-slug-1
Once more, thank you so much for being so helpful!
The topic ‘Slugs question’ is closed to new replies.