[ http://issues.apache.org/jira/browse/OFBIZ-111?page=comments#action_12459238 ] Chris Howe commented on OFBIZ-111: ----------------------------------
All of the <@ofbizContentUrl> are setup relative the root. This is necessary so that images can be stored in places other than the images for a custom deployment. For instance there are occurances of both: <@ofbizContentUrl>/images and <@ofbizContentUrl>/content so, if you wish to use the images in ofbiz in an OOTB way with the images being served elsewhere, you must maintain the /images directory structure and set your ofbizContentUrl to the parent directory. This should either be 1) closed as won't fix 2) create another freemarker transform to distinguish between /images and /content 3) change <@ofbizContentUrl>/content to <@ofbizUrl>/content and drop the /images from the template file. I would opt for 3 but wouldn't want to begin this refactor without a concensus > Using hardwired /images instead of <@ofbizContentUrl> in .ftl files > ------------------------------------------------------------------- > > Key: OFBIZ-111 > URL: http://issues.apache.org/jira/browse/OFBIZ-111 > Project: OFBiz (The Open for Business Project) > Issue Type: Bug > Components: content, ecommerce, manufacturing, order, party, product > Affects Versions: SVN trunk > Reporter: Eriks Dobelis > Priority: Minor > > There are some template and script files which use hardwired links, e.g. > /images. This means that ofbizContentUrl is not taken into account and may > not work if some components (especially images) are mounted at different > locations. > For ftl files <@ofbizContentUrl> should be used. I have no good idea what to > do with javascript and css files. > This is a list of files created by grep (grepping "\"/images" ) from > application directory, which probably should be fixed. > content/webapp/content/images/composite.js > ecommerce/webapp/ecommerce/shoppinglist/editShoppingList.ftl > ecommerce/webapp/ecommerce/cart/showcart.ftl > ecommerce/webapp/ecommerce/includes/header.ftl > ecommerce/webapp/ecommerce/order/splitship.ftl > manufacturing/webapp/manufacturing/routing/EditRoutingTaskAssoc.ftl > manufacturing/webapp/manufacturing/jobshopmgt/CreateProductionRun.ftl > manufacturing/webapp/manufacturing/bom/EditProductBom.ftl > order/webapp/ordermgr/entry/cart/showcartitems.ftl > order/webapp/ordermgr/entry/cart/showcart.ftl > order/webapp/ordermgr/entry/catalog/productsummary.ftl > order/webapp/ordermgr/entry/catalog/productdetail.ftl > order/webapp/ordermgr/entry/catalog/configproductdetail.ftl > order/webapp/ordermgr/order/appendorderitem.ftl > party/webapp/partymgr/party/EditPartyRelationships.ftl > product/webapp/facility/returns/receiveReturn.ftl > product/webapp/facility/facility/FindFacilityLocation.ftl > product/webapp/facility/facility/EditFacilityGroups.ftl > product/webapp/facility/shipment/QuickShipOrder.ftl > product/webapp/facility/shipment/FindShipment.ftl > product/webapp/facility/group/EditFacilityGroupMembers.ftl > product/webapp/facility/group/EditFacilityGroupRollup.ftl > product/webapp/facility/inventory/receiveInventory.ftl > product/webapp/facility/inventory/TransferInventoryItem.ftl > product/webapp/facility/inventory/EditInventoryItem.ftl > product/webapp/catalog/product/EditProductQuickAdmin.ftl > product/webapp/catalog/product/ApplyFeaturesFromCategory.ftl > product/webapp/catalog/product/EditProductAssoc.ftl > product/webapp/catalog/product/EditProductFeatures.ftl > product/webapp/catalog/product/EditProductFacilityLocations.ftl > product/webapp/catalog/find/keywordsearch.ftl > product/webapp/catalog/promo/EditProductPromoStores.ftl > product/webapp/catalog/store/EditProductStorePromos.ftl > product/webapp/catalog/store/EditProductStoreSurveys.ftl > product/webapp/catalog/category/EditCategoryProducts.ftl > product/webapp/catalog/category/EditCategoryParties.ftl > product/webapp/catalog/category/EditCategoryRollup.ftl > product/webapp/catalog/category/EditCategoryProdCatalogs.ftl > product/webapp/catalog/category/EditCategoryFeatureCats.ftl -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
