• Resolved swinggraphics

    (@swinggraphics)


    This permalink vs slug issue is really going to stop me from using the plugin:

    It would be very helpful if the default slug could still be edited on the full Edit Post/Page while the plugin is active so that if/when the plugin is disabled, we don’t suddenly have a ton of 404s.

    Even better would be if both got edited at the same time. Both would still be visible, and the update would happen simultaneously while you type. It could use whatever is after the last “/” as the slug.

    Similarly, it would be very helpful to be able to set the custom permalink in Quick Edit.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Sami Ahmed Siddiqui

    (@sasiddiqui)

    @swinggraphics Sorry but we doesn’t have any kind of this request to make editable both fields(Default + Custom) Permalinks at time nor we have planned to do that.

    Why you want this thing? Doesn’t you want to use the Plugin and why?

    Regards,
    Sami

    Thread Starter swinggraphics

    (@swinggraphics)

    Let’s say I have 5 pages that I want to set up custom permalinks for—adding or removing a “/” in their URI. If the plugin is disabled, every single permalink that was edited while the plugin was active will be a 404, whether or not it was truly “custom”. Basically, once this plugin is installed, you can never disable it, or your site and/or search engine rankings will break.

    Plugin Author Sami Ahmed Siddiqui

    (@sasiddiqui)

    @swinggraphics Either you can use trailing slash with all the URLs or none of the URLs in default WP Structure.

    If you want remove so, you need this plugin to be activated Otherwise Permalinks doesn’t work.

    Regards,
    Sami

    Thread Starter swinggraphics

    (@swinggraphics)

    A trailing slash doesn’t factor into it in any way. This is the problem:

    1. Publish a new page. Let’s say the permalink is “/new-page”.
    2. Activate Custom Permalinks
    3. Change the permalink of that page to “/an-updated-page”.
    4. Disable Custom Permalinks
    5. site.com/an-updated-page will be 404 even though the format of the “custom” permalink is not special and did not require the Custom Permalink plugin.

    The CP plugin is basically just interfering with default functionality in many/most cases. It can never be disabled without breaking a lost of URLs, even if those URLs did not need CP and conform to the standard WP format.

    Plugin Author Sami Ahmed Siddiqui

    (@sasiddiqui)

    OK. Marking your point and would provide some basic functionality which helps you to make the permalinks workable after disabling the plugin.

    This Functionality would be provided in the future release. There is no date for it now.

    Regards,
    Sami

    I agree that this is a serious issue that needs some attention. The plugin hijacks the “real” permalink field on the post edit page, causing any edits to the permalink to be saved in a custom table rather than modifying the actual permalink slug of the post, which is a completely unnecessary step when the modifications to the post slug follow the permalink structure for the site.

    The better solution would be to keep the standard permalink field and have a separate field for the custom permalink.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Don’t remove slug from edit page’ is closed to new replies.