WordPress.org

1. gian-ava
   Member
   Posted 1 year ago #

   The Permalink Editor worked great for what I needed for my website.
   Only problem is that since is a 2 languages (EN, FR) website with qTranslate installed, the "customized" permalinks for the secondary language (FR) return a 404 page.

   I really need to fix this because I can't have the French version of those pages broken.

   Thanks in advance to anybody who will help me out with this.

   I can provide the URLs of the pages if needed.

2. gian-ava
   Member
   Posted 1 year ago #

   Fubra,

   Maybe this can be interested to make the plugin compatible with qTranslate:
   http://www.qianqin.de/qtranslate/forum/viewtopic.php?f=3&t=294

   Thanks for considering it and to let me know.
   ;-)

3. Fubra
   Member
   Posted 1 year ago #

   Hi,

   The quick solution would be to use query mode (?lang=en) as the URL Modification Mode instead of Pre-Path Mode, this worked in my development environment.

   This can be found on the Language Management (qTranslate Configuration) settings page, under Advanced Settings.

   Hopefully a more elegant solution could be found, however this would require more investigation into the way qTranslate deals with prepended URLs.

   - Steve

4. gian-ava
   Member
   Posted 1 year ago #

   Thanks a lot for the reply, Fubra, I appreciate.

   However, changing to query mode (?lang=en) is not ideal for me, because I already have all my online site working with the subfolder option (site.com/fr/page), and that would mean I should create all the rewrite rules for people who bookmarked the pages.

   Is there any other way?
   Did you look at the link on the qtranslate forum about Plugins?
   http://www.qianqin.de/qtranslate/forum/viewtopic.php?f=3&t=294

   Would this help?

   Thanks…

5. gian-ava
   Member
   Posted 1 year ago #

   So frustrating that you can't have both, custom permalinks with "Permalinks Editor" AND multilanguage site.

   WordPress really pisses me off when you get stuck like this for simple, basic things…

6. Fubra
   Member
   Posted 1 year ago #

   Hiya,

   I have found some time this afternoon to look into a more substantial solution, which looks to have solved the problem.

   It does however require further testing and for some further thought into how to integrate the fixes as they are very specific to the qTranslate plugin.

   Having incompatibilities across plugins can be quite common, as it's difficult to test each and every combination, although there is more often than not a solution to be found.

   I shall continue with the testing on Monday and intend to release an update to solve the compatibility with qTranslate early next week.

   - Steve

7. gian-ava
   Member
   Posted 1 year ago #

   Thanks a lot, Steve. I will look forward for the fix and will donate something, since you're an exemplary plugin author, and your plugin is very useful.

8. Fubra
   Member
   Posted 1 year ago #

   Version 0.2.1 has just been committed, which should include fixes for qTranslate with per path urls enabled.

   I encourage you to download this version once it becomes available and test to see if this solves the problem you were having.

   Thanks!

9. gian-ava
   Member
   Posted 1 year ago #

   Fubra, the new version works perfectly with qTranslate now. Thanks a lot, you're great!

   As I told you, I'll donate, because this is effective support. Thanks again.
   ;-)

10. gian-ava
    Member
    Posted 1 year ago #

    Sorry, Steve, with the new version of the plugin I encontered another problem.

    Languages are fine now, but it looks like Custom Post Types in single view return a "Not Found Page".

    I tried to save the Permalinks options to force a ruibuild of permalinks, but nothing.

    I had to deactivate the plugin again, cause I need those Custom Types on, of course.
    I'll wait for your reply…
    Thanks.

11. Fubra
    Member
    Posted 1 year ago #

    Hi,

    Custom post types is one thing that I hadn't really tested with, so thanks for highlighting the problem.

    There was an issue with the way that the destination page / post was being looked up which has now been modified. (Using an array of available post types did the trick rather than 'any', which I wrongly assumed would be fine.)

    I have committed the changes to the development version, however have not tagged it as a stable release yet.

    Would you be willing to test this version on your install and see if it solves the issue before I release it as 0.2.3?

    The development version .zip file doesn't appear to reflect these changes yet, however you can replace index.php with the following:

    http://plugins.svn.wordpress.org/permalink-editor/trunk/index.php

    Thanks,

    - Steve

12. Fubra
    Member
    Posted 1 year ago #

    Looks like the .zip file is now updated and is available here:

    http://wordpress.org/extend/plugins/permalink-editor/download/

    The 'Development Version' can be found at the bottom of the list.

13. gian-ava
    Member
    Posted 1 year ago #

    Hi Fubra, I tested the Development version and I still got the same problem with Post Types.

    The website is this: http://manonuda.com
    The post types that doesn't work are in the agenda section.

    I will deactivate the plugin again, so it will work as soon as the plugin's off.

    Thanks for leeting me know about further updates.
    Cheers.
    ;-)

Topic Closed

This topic has been closed to new replies.