Hello, To respond/updtae this post, the explanation for this problem seems the right one. BUT even when i register the new CatalogPathAwareness.py in __init__, the OLD CatalogAwareness seems used for every new instance i create. ? Is there something hard coded in my ZClass (created before this change) so it doen't use the new __init__ ? ? If yes, could it be changed besause this ZClass contains A LOT of things.? ? if not is it safe to change the CatalogAwareness.py with adapting the url() ? Will i break something else ?? Any advice more than welcome. Le 14 Nov 2001, à 17:57, Didier a écrit :

All CatalogAware auto-indexing is fine when i dont use VHM, and when i have (thru Apache and VHM) my root as a folder the autocataloging get the wrong physical path : in ZCatalog/__init__.py

there is registring for the old CatalogAwareness instead of the new CatalogPathAwareness (with the getURL, getPath wich i use without anu problem in my application)

? What happens if i just change the ZCatalog/__init__

import ZCatalog, Catalog, CatalogPathAwareness, Vocabulary, ZClasses createZClassForBase( CatalogPathAwareness.CatalogAware, globals() , 'CatalogAwareBase', 'CatalogAware' )

-- Didier Georgieff Chef de projet technique SIT du Bas-Rhin tél : 03.88.76.78.35 - fax : 03.88.76.78.34 email : didier.georgieff@agriculture.gouv.fr