Handling Punctuation

Select the following option in the settings page:

  • Ignore specified characters, like quotes, when sorting the index

Now, before you save the settings, look near the bottom of the page.  A new setting has appeared (you might have to scroll down to see it) where you can specify which characters the plugin should ignore when sorting the index.  (Note: this only applies when sorting headings, not subheadings or descriptions.)

By default, single and double quotes and included, so there is no need to add anything here.

If you scroll through the index below, you will see that the item beginning with the double quotes (“The Dante Club”) is no longer at the bottom of the index but is situated where it should be, slap bang in the middle of the “The”s.  The quotation marks are still included in the title, since they are in the title of the post, but they no longer affect the item’s position in the index.

View the index »


No comments yet to

  • Hi everybody,

    I agree with all of you: this is a very Great Plugin! Thanks to Mike .

    Now I need your help (Mike or anybody who could) .

    1- I create an author index on my site . It seem working very well . But how I can group items with the same heading under one main entry without selecting subheadings ? I mean each author name appear only once and when we click on it we’ll see all his post. Please take a look on my page

    2- I have another site (same server, same hosting) but the author index page on this site can’t be read (please click on this link for reading the error message)

    Many thanks in advance

    LW

  • 2- I have another site (same server, same hosting) but the author index page on this site can’t be read (please click on this link for reading the error message)
    Sorry ! I don’t know why the above link is not working .

  • GREAT plugin, thank you!!

    @curtis klope, thanks so much for the tweak, i was experiencing the same issue and was so not looking forward to diving into the code, so was thrilled to find a quick solution!

    i think it is a bug and your fix should be rolled into the next release…