“No items found” is not necessarily an error

  • Resolved stefangawronski

    (@stefangawronski)


    5 years, 7 months ago

    “No items found” is not necessarily an error. For instance, I manage a website for multiple researchers. Each researcher has a web page that lists their forthcoming publications (year=”0000”) followed by their publications for the current year and for the previous 4 years. Researchers may legitimately have no forthcoming publications or no publications for one or more years. This situation results in the following error message: “There was a Zotpress error: No items found”. However, returning no items does not amount to an error here. Simply returning no results or returning “No items found” without stating that this is a Zotpress error would be more appropriate in this context.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Katie

    (@kseaborn)

    True. I’ll update this in 7.1.3.

    Thread Starter stefangawronski

    (@stefangawronski)

    I installed 7.1.3 and still get the message “There was a Zotpress error: No items found.”

    Plugin Author Katie

    (@kseaborn)

    Can you give me an example of a shortcode?

    Thread Starter stefangawronski

    (@stefangawronski)

    [zotpress collection=”4HZ75VS5″ year=”2015″]

    Thread Starter stefangawronski

    (@stefangawronski)

    I tried another browser and it was fine. So then I cleared the history in Chrome and that fixed it. Sorry – I should have tried that first. Thanks for your prompt resolution of this issue!

    Plugin Author Katie

    (@kseaborn)

    Oh! I suppose in this case the browser cached the old version of Zotpress? I hadn’t thought of that … thanks for sharing. Hopefully this will help others, too.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘“No items found” is not necessarily an error’ is closed to new replies.