Thanks for the effort Mike,
Now we know what we are speaking about. Seems You are concerned by Multitenant
Wai?
Jacques
From: "Mike" <[email protected]>
This is a useful feature. Suppose I have multiple websites and I want to
all images in separate directories under a common shared NFS mount. The
images reside in /nfs001/images/website01 and /nfs001/images/website02,
etc..
You could set the Content Path Prefix /nfs001/images/website01 and it
would work.
Regarding Template Path Prefix, there are probably other use cases where it
would be useful.
Taking out features doesn't make sense to me, especially if there are cases
where it might be useful, and leaving it in is not causing a problem.
On Mon, Jun 11, 2012 at 2:31 PM, Wai <[email protected]> wrote:
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.
