-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Raw merge of qtranslate-slug 1.1.18 as qtranslate-xt module #1060
Conversation
Initial merge with minimal modifications to both qtranslate-xt core and qtranslate-slug to incorporate the latter as a module. Module can be enabled through a checkbox in qtranslate-xt advanced settings. Heavy code cleanup and harmonization yet to be performed. Settings page also to be incorporated in qtranslate-xt page
a1b4dbf
to
b1bf3aa
Compare
Need more time to check and polish, but it's in the plan to integrate this. It will be a major release. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice job!! Looks good overall!
A few remarks with a few changes to come before merge.
We should transition fully from plugin to module. It is still in an intermediate state. But the idea is to merge and continue refactoring this on master.
array( | ||
'id' => 'slugs', | ||
'name' => 'Slugs', | ||
'plugin' => true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should rather enable that if the user checks "enable experimental slugs", so the other way around.
But I see why it is easier like this for now. The module has still the legacy code of the plugin, so the init sequence should be refactored.
For the last updates and post-merge cleanup see #671. |
Hello maybe this is not the correct place to post this error, let me know if I should open a new thread... Anyway... I noticed an issue with Russian language, if the slugs are in Cyrillic (like the titles), front-end links in Russian language give 404 error. If I rewrite the slugs in Latin characters (for example apartamenty instead of апартаменты), there are no issues. Anyone else noticed this bug? |
@bagaweb opening a new issue would be better for proper follow-up and visibility. |
Based on original plugin README, this seems to be a known issue. |
Ok but this issue was about taxonomies and custom post types, not about pages. On an another project which is using QTXT & QTS 1.18, pages work fine even with Cyrillic slugs. |
Initial merge with minimal modifications to both qtranslate-xt core and qtranslate-slug to incorporate the latter as a module.
Module can be enabled through a checkbox in qtranslate-xt advanced settings.
Heavy code cleanup and harmonization yet to be performed.
Settings page also to be incorporated in qtranslate-xt page