Need help? Check out our Support site, then


Slug (permalink) looks weird

  1. I have sent this to staff directly but wondering if anyone here may have seen this already and would know.

    I am wondering why does the slug URL on this post has those weird characters.

    http://ismailimail.wordpress.com/2012/07/06/the-%e2%80%aaismaili%e2%80%ac-community-float-wins-best-overall-at-calgary-stampede/

    When I check the permalink box, I don't see anything unusual, so I am surprised to see the way this post has turned out. I wonder if this is a bug with the theme or something else I am overlooking?

    The blog I need help with is ismailimail.wordpress.com.

  2. Do you mean the percentage symbol? As far as I know it's escape code for a dash.

  3. All this ...

    %e2%80%aa

    is unnecessary.

  4. Try looking at this from W3Schools:

    http://www.w3schools.com/tags/ref_urlencode.asp

    If that doesn't help, come back and maybe someone else can help you.

  5. I'll modlook this so that staff can take a look. I suspect it's just a bit of buggy coding that they can do something about. Hang on there.

  6. sensuousinkspiller
    Member

    A few days ago when I was "previewing" a post, the URL of the post including the "+preview=true" and all that, was added to the post name, and there was gibberish in the slug. I noticed it and deleted it, it hasn't happened since, and I figured it was one of those blips that can happen.

    I wonder if something similar happened with your post?

  7. That's a bit normal, there must have been some invalid characters in the post title.

    %e2 = â

    %80 = €

    %ac = ¬

    You can edit the slug by editing the post. The slug is below the Title field.

  8. That is what I thought as well and I am aware of changing the slug below the title field, but to show you how it looks right now, here's the screen shot.

    http://ismailimail.files.wordpress.com/2012/07/slug-error.jpg

    As you can see, there are no invalid characters in the field. So I wonder what is causing this problem.

  9. Hm, that was odd. I was able to fix it by just retyping the bad portion. I'm not sure why it was broken, but please let us know if it ever happens again!

Topic Closed

This topic has been closed to new replies.

About this Topic