It seems funny to propose removing a feature which you don't understand, or 
even deprecating it without a replacement.

-David


On Jun 10, 2012, at 2:36, Jacques Le Roux <[email protected]> wrote:

> I did not check but from the date you gave it's an old feature from the pre 
> ASF era
> This has maybe been introduced with the Content component and never finished.
> 
> Then we could get rid of it, at least from the UI indeed
> 
> Opinions?
> 
> Jacques
> 
> From: "Wai" <[email protected]>
>> Does anyone know how a catalog's "Template Path Prefix" field is used from
>> http://demo-trunk.ofbiz.apache.org/catalog/control/EditProdCatalog?prodCatalogId=DemoCatalog
>> It seems that the code blindly prepends the "Template Path Prefix" value to
>> the category's "Detail Screen" field.
>> 
>> Hence, if a catalog's "Template Path Prefix" is "zzz" and a category's
>> "Detail Screen" is "somedetailscreen", the resulting screen that ofbiz looks
>> for is "/zzzsomedetailscreen".  Which ofbiz would not be able to locate
>> based on the format of the screen location.
>> 
>> If a catalog's "Template Path Prefix" is "zzz" and a category's "Detail
>> Screen" is
>> "component://ecommerce/widget/CatalogScreens.xml#somedetailscreen", the
>> resulting screen that ofbiz looks for is
>> "/zzzcomponent://ecommerce/widget/CatalogScreens.xml#somedetailscreen".
>> Which ofbiz would not be able to located due to the improper format.
>> 
>> Since this code never worked since 2006 when it was first placed into the
>> svn repository.  I don't think anyone has made use of it since.
>> 
>> I propose to remove the catalog's "Template Path Prefix" field from the
>> catalog's user interface to reduce the confusion.
>> 
>> Could someone in the community give some insight to this field.
>> 
>> Thanks,
>> Wai
>> 
>> 
>> --
>> View this message in context: 
>> http://ofbiz.135035.n4.nabble.com/Proposal-to-remove-catalog-s-Template-Path-Prefix-field-from-user-interface-tp4633296.html
>> Sent from the OFBiz - User mailing list archive at Nabble.com. 

Reply via email to