• This is the pluging for custom lists in sidebar and footer!
    Many settings, flexible views.
    Highly recommended!

    I wish I had opportunity to use it as a [shortcode] to place it anywhere around the page.

    ALSO! It is possible to limit the length of post’s title or text to ### words (NOT SYMBOLS), which is weird. In most languages some words are very lenthy, some are real short. That results in funny looking lists sometimes and the plugin doesn’t help much. SO that’s the way to make the pluging a bit better.

    • This topic was modified 6 years, 3 months ago by brontho. Reason: forgot to mention important issue (words limit)
Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Aldo Latino

    (@aldolat)

    Hello,
    the shortcode is available as of version 3.0. It’s also mentioned in the homepage of the plugin and on GitHub you can find some examples of use of the shortcode.

    About the title shortening in characters, I had already prepared a new option that will be available in the next version of the plugin. Let me know if it’s OK for you.

    Plugin Author Aldo Latino

    (@aldolat)

    @brontho

    I just released the 4.5.0 version. Among other improvements, you will find a new option “Title length unit” under “Displaying posts” > “The title of the post” and another option “Excerpt length unit” under “Displaying posts” > “The text of the post”.
    Let me know if it’s fine for you.

    Also, have you resolved with shortcodes?

    Thread Starter brontho

    (@brontho)

    Shortcodes – yes, resolved, thank you.

    Length in characters – this updated plugin’s feature works and the user interface is very clear and logical, but the shortening itself wors with some glitches on my non-latin titles.

    SOME of the shotened titles contain (right before the elipsis) a rhombus with question mark in it, a (possibly) sign of an unrecognized symbol…
    At the same time some other shortened titles don’t have that rhombus…
    I cannot get the logic yet…
    My website is in Russian (UTF-8 charset) So, probably, the code doesn’t check integrity of non-latin characters.
    A simple logic could (after getting symbols list) delete symbols until nearest % (or whatever the sign of beginning of a non-latin symbol is in UTF)
    Another solution – checking resulting string and deleting that rhombus.

    I had to revert to “words”…

    • This reply was modified 6 years, 2 months ago by brontho.
    • This reply was modified 6 years, 2 months ago by brontho.
    Plugin Author Aldo Latino

    (@aldolat)

    Hello @brontho
    I just published the new 4.5.1 version that has been released specifically for this issue.

    Please, let me know.

    Thanks.

    Plugin Author Aldo Latino

    (@aldolat)

    Hello @brontho
    could you tell me if the new version resolves the UTF-8 issue for you, please?

    Thanks.

    Thread Starter brontho

    (@brontho)

    Hello, @aldolat
    YES! It worked and now everything is just right!
    Thank you for your terrific support.

    Plugin Author Aldo Latino

    (@aldolat)

    Hello @brontho
    I’m happy it worked as you expected!

    About the review, may I ask you to change it to 5 stars or do you prefer to maintain 3 stars?

    Plugin Author Aldo Latino

    (@aldolat)

    Hello @brontho
    I don’t want to bother you and I won’t ask it anymore.

    About the review, may I ask you to change it to 5 stars or do you prefer to maintain 3 stars?

    Thread Starter brontho

    (@brontho)

    Hello, @aldolat

    I am sorry you had to point that out… I didn’t think of it
    Sure, I rate it FIVE stars now! Fantastic plugin!

    Thank you for your great support, again. Very quick and professional.

    Plugin Author Aldo Latino

    (@aldolat)

    Thank you! 🙂

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Joy to work with, but with some drawbacks’ is closed to new replies.