Dani Llewellyn

Hi @girdy74, it looks like the path to the javascript is wonky. I set the path to include /js/ when it should be /scripts/. The fix is coming in 2.1.0.

awesome! I’m really glad it’s working for you now 🙂

(I’ll mark this thread as resolved, but come back if something else goes awry or you would like me to help any further)

Can you expand a bit on that? I’m not sure what you are referring to. A screenshot of your site showing the problem might help me.

I’m sure my lack of understanding is my fault, and I’m sorry I can’t help directly in this reply :-(.

Can you share the shortcode you’re using to exclude posts? It should be similar to:

[a-z-listing display="posts" post-type="page" exclude-posts="5,6,7"]

Versions 2.0.5 and 2.0.6 didn’t include any changes to the code that excludes posts, so I’m not sure why it would stop working for you….

You’re right – good catch. There’s a limitation with taxonomies against pages.

I can alleviate that, partly, by updating the plugin to use get_pages on a more limited basis – currently it uses get_pages for any listing that requests pages as the post type. I’ve worked up some code which I’ll put into a new version 2.1.0 in the coming week, but there will still be an issue if the plugin thinks it needs to show child and grandchild pages of a specific post.

Hi,

I’ve promoted the multi-column mode, with some changes, to be the default output.

The CSS has changed, however, so the old template won’t display correctly any more, as you found out..

If you haven’t modified the template when you copied it into your theme, you can just delete the file and everything should work out of the box now. Alternatively, if you have modified the template you’ll need to compare to the default template at wp-content/plugins/a-z-listing/templates/a-z-listing.php and merge your custom code into a copy of this file in your theme like you did with the old multi-column template.

I’m working on a 2.1.0 version which will add two new filters for overriding the index letters and titles of items. Rather than trying to memorise or copy my implementation of the heavily nested array structure, you will be able to instead hook the filters a_z_listing_pre_index_item_title and a_z_listing_item_index_letter.

Their implementation will be as follows:

add_filter( 'a_z_listing_pre_index_item_title', 'my_override_titles', 10, 3 );
function my_override_titles( $title, $item, $type ) {
    // $title is the title of the item as used for the index
    // set $title to your preferred format. This will then be indexed by the
    // default extraction - i.e. the first letter of the new title will be
    // the index letter used for this item

    // delete Mr and Mrs from the start of titles (presume they're names):
    $title = preg_replace( '^((Mr)|(Mrs))\s+', '', $title );

    return $title;
}

add_filter( 'a_z_listing_item_index_letter', 'my_override_index_letter', 10, 3 );
function my_override_index_letter( $letters, $item, $type ) {
    // $letters is an array of letters to use for the item in the index
    // any item can be indexed under any number of letters

    if ( 15 === $item->ID ) {
        // let's index this item under P and Z.
        $letters = array( 'P', 'Z' );
    }

    return $letters;
}

• This reply was modified 7 years, 8 months ago by Dani Llewellyn. Reason: added example of overriding $title
• This reply was modified 7 years, 8 months ago by Steven Stern (sterndata).

I’ve just seen it, thank you very much 🙂