devtrain weirdness

[Richard H.]

Using the training Silva instance, I deleted the service_dl_uob from the Zope root and the dl_cherry_uob object from the Staff (Silva) root. I then created two new objects in the Silva root; namely 'service_dl_training' and 'dl_cherry_training' (which both reference http://arana.beds.ac.uk/dl/training).

The Training DL instance has two available documents within it (one in Staff_site/Policies/technical and another (uploaded and made available today) within User_Guides/GroupWise (a category that was only created today)).

I then went into the 'Staff' Silva instance and tried creating a new DL Listing object. When it came to defining the object, Silva wasn't picking up the fact that there was an available document inside User_Guides/GroupWise. In fact, it seemed to only be showing those categories with available documents that were on offer prior to the GW document becoming available...

I've updated the relevant service (by manually clicking the 'update' button) and this has made no difference. I still think this suggests that there's some weird 'caching' issue somewhere... could there be some issue with 'squid' and the Silva application on arana?

[Richard H. (richard-hewison)]

I've double-checked the 'dl storage' in Zope (via the option when inside 'service_dl_training') and the two available documents from the 'training' DL are showing up in the list in Zope, so why isn't the DL Listing object allowing me to include the DL category that one of those two documents resides within?

I can't see any way of checking which DL instance a DL Listing object is referencing once it's been created. I've deleted and re-created the DL Listing object two or three times and each time I have double-checked it references the correct DL, yet we are still experiencing this problem.