WordPress.org

Forums

Post Permalink could not be changed any longer with WordPress 3.5 (9 posts)

  1. redcrab1277
    Member
    Posted 3 years ago #

    Hi All,

    just updated my WordPress to 3.5 and almost everything works fine! Great Job.

    One issue I found is within the Posts view I could not any longer change the permalink URL with the Edit button. Nothing happens.

    Is there any workaround in place?

    Cheers,
    Ben

  2. George Stephanis
    Code Monkey
    Posted 3 years ago #

    Could you please go through the steps listed on

    http://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors

    and report back what causes the issue?

    Also, can I get a link to your site to test something non-invasively?

  3. redcrab1277
    Member
    Posted 3 years ago #

    The issue is not browser related...did not work with firefox nor IE.

    With Firebug I could see the following error:

    TypeError: editPermalink is not a function

    Link to my side: http://www.ausbildung-energieberater.de

  4. George Stephanis
    Code Monkey
    Posted 3 years ago #

    Okay, it looks like

    http://www.ausbildung-energieberater.de/wordpress/wp-admin/load-styles.php?c=1&dir=ltr&load=admin-bar,buttons,media-views,wp-admin&ver=3.5

    is whitescreening out when I try to load it (those are the scripts that would normally be on the new/edit post screen)

    Can you please check your server error logs? Or turn on WP_DEBUG in your wp-config file via

    define('WP_DEBUG', true);

    (just change the existing false to true)

    -- and then load that URL I linked and paste me the result? It should have some error messages.

  5. George Stephanis
    Code Monkey
    Posted 3 years ago #

    Wait, no, scratch that.

    Add

    define('SCRIPT_DEBUG', true);

    to your wp-config file, does that fix it?

  6. redcrab1277
    Member
    Posted 3 years ago #

    I will check it wait..

  7. redcrab1277
    Member
    Posted 3 years ago #

    yes it fix it......

  8. redcrab1277
    Member
    Posted 3 years ago #

    what do I need to do now? leave it in the SCRIPT_DEBUG state?

  9. George Stephanis
    Code Monkey
    Posted 3 years ago #

    For the moment. This is not an uncommon occurrence, and we believe is a plugin conflict (some plugins leave greasy fingerprints behind even after they're deactivated).

    Hoping to have a permafix in the next day or two. Keep your ears to the ground and follow make.wordpress.org/core if you want to keep closer in the loop.

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.