DL Listing objects with no category show ALL documents

[Richard H.]

A DL Listing object that has no categories selected but is included on a web page now pulls in every single document from the entire library on to the page. Previously it would display nothing, which is exactly how we would want it to behave if it finds no selected categories.

We assume this is an unwanted side-effect of the change in the way categories are detected by the DL Listing object, but this needs to be fixed.

[Sylvain Viollon (thefunny)]

It's the behavior of 'All values'. As it's the same behavior than before, I am pretty sure: if you unselect All values and doesn't select anything else, All values is selected back, so it display everything. It's the same behavior than the fields 'FOI Topics' or 'Author Email Addresses'. So I added back that 'All values' option, which basically is there to look like those two others fields, but doesn't do much better than selecting nothing in that list.

It's updated on istos.

[Richard H. (richard-hewison)]

There was an 'All values' option before, but critically it wasn't selected by default when the DL Listing object was first created. The category list had nothing selected by default, therefore it showed nothing on the published web page.

You can see this here...

in.beds.ac.uk/isd/equipment/isd-buying-docs/edit/tab_edit

... on our currently live server (arana).

>>> On 29/07/2009 at 10:23, Sylvain Viollon <email address hidden> wrote:

> It's the behavior of 'All values'. As it's the same behavior than before, I
> am pretty sure: if you unselect All values and doesn't select anything else,
> All values is selected back, so it display everything. It's the same behavior
> than the fields 'FOI Topics' or 'Author Email Addresses'. So I added back
> that 'All values' option, which basically is there to look like those two
> others fields, but doesn't do much better than selecting nothing in that
> list.
>
> It's updated on istos.
>
> ** Changed in: documentlibrary
> Importance: Undecided => Low
>
> ** Changed in: documentlibrary
> Status: New => Fix Committed
>
> ** Changed in: documentlibrary
> Assignee: (unassigned) => Sylvain Viollon (thefunny)
>
> --
> DL Listing objects with no category show ALL documents
> https://bugs.launchpad.net/bugs/406214
> You received this bug notification because you are a direct subscriber
> of the bug.

[Kit Blake (kitblake)]

This took quite some time to work out, but it's fixed. Now when you add a listing object, nothing is actually selected. So if you preview you will see nothing. If you save, then whatever is highlighted in the select boxes gets saved.

[Richard H. (richard-hewison)]

Is this live on the test server yet? We now have 'All values' back for categories, but creating a new DL Listing still has 'All values' selected by default?

[Kit Blake (kitblake)]

Follow these steps:
- Add a listing object (do not press the save button after creating it)
- Preview (you will see nothing)
- Then if you save, whatever is highlighted in the select boxes gets saved.

[Richard H. (richard-hewison)]

Okay, I can see how that behaves. However, it's very confusing because we are faced with two different behaviours for what looks like the exact same settings in a DL Listing object:

(i) A newly created listing object has 'All values' highlighted (but 'save' has not been selected since the object was originally created) and when used on a published page, this will list nothing at all.

(ii) A listing object has 'All values' highlighted (and has been 'saved') and when used on a published page, this will list every document in the entire library.

So the objects look identical when examined in closer detail, yet their behaviour is the exact opposite to each other. One lists nothing and one lists everything.

If 'nothing is actually selected' why do we see 'All values' highlighted as if it has been selected? Why can it not be 'off' like it was in previous versions?