I've read the help and doc as well and I could not understand what it says. :-( As a result, I had to get the real doc from the code.
My comment on the bug with "Template Path Prefix" was already explained. Regarding a catalog's "Content Path Prefix" field, it also exhibits the same flaw. That of blindly prepending this field. This field is generally used to specify the product images to be shown in the ecommerce component. When this field is empty, the generated image tag in ecommerce is shown below (note that it is using "image" webapp context): /images/products/ENCHILADAS/small.png If you were to specify "/zzz" for "Content Path Prefix", the resulting url for the generated image tag is shown below (note that it is using "zzz" webapp context): /zzz/images/products/ENCHILADAS/small.png As you can see. "Content Path Prefix" specifies a "zzz" webapp context with a subdirectory "image". I doubt this was the intent of the field. The question is, where exactly are you supposed to place this field value? Wai -- View this message in context: http://ofbiz.135035.n4.nabble.com/Proposal-to-remove-catalog-s-Template-Path-Prefix-field-from-user-interface-tp4633296p4633448.html Sent from the OFBiz - User mailing list archive at Nabble.com.
