Eric Roby wrote:
When these doc objects get messed with on ClientStorage-2, the absolute_url Metadata property in the Catalog always points to ClientStorage-2 (on all ClientStorages). So when someone kicksoff a search on ClientStorage-1 (www.bla.bla.gov) the result set returns a list that points to objects on ClientStorage-2. I can go into the catalog on ClientStorage-1 and re-build the indexes and everything is as it should be (with respect to the result set pointing to objects on ClientStorage-1) but as soon as any doc is messed with, the absolute_url for that doc will (again) point to the object on ClientStorage-2.
hi, you don't need to store the absolute_url in the meta-data of a ZCatalog. For your situation this should work: <dtml-in yourQuery> <dtml-with "yourCatalog.getobject(data_record_id_)"> now you can play with the absolute_url (and all other properties) of the cataloged item like this: <dtml-var absolute_url> </dtml-with> </dtml-in>... greetings, maik.