Wai created OFBIZ-4931:
--------------------------

             Summary: Proposal to remove catalog's "Template Path Prefix"
                 Key: OFBIZ-4931
                 URL: https://issues.apache.org/jira/browse/OFBIZ-4931
             Project: OFBiz
          Issue Type: Bug
          Components: product
    Affects Versions: SVN trunk
            Reporter: Wai


In reference to the posting, 
http://ofbiz.135035.n4.nabble.com/Proposal-to-remove-catalog-s-quot-Template-Path-Prefix-quot-field-from-user-interface-td4633296.html

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 resulting in a file path format that would 
cause an exception.

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.  Hence, cause an exception.

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. Hence cause an 
exception.

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 and assoc code to reduce the confusion.



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to