Proposal to remove catalog's "Template Path Prefix" field from user interface

[Wai]

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

[Wai]

Hello,

Anyone knowledgeable in this area to give some insight?

Thanks

[Jacques Le Roux]

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" <[hidden email]>

> 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.

[David E. Jones-2]

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 <[hidden email]> 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" <[hidden email]>
>> 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.

[Jacques Le Roux]

I thought that if nobody uses it removing from UI will not be a big deal. Else if someone uses it, then s/he will react and, if we
are lucky, explains why it's there and what for it's used. From Wai description it's useless, and I must say I also never used it.

I must admit it was a leasy assumed reaction

Jacques

From: "David E Jones" <[hidden email]>

> 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 <[hidden email]> 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" <[hidden email]>
>>> 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.

[Jacques Le Roux]

BTW, if ever I do anything about that it will be noted in Attic page in wiki, still with the slim-down priority in mind.

Jacques

From: "Jacques Le Roux" <[hidden email]>

>I thought that if nobody uses it removing from UI will not be a big deal. Else if someone uses it, then s/he will react and, if we
>are lucky, explains why it's there and what for it's used. From Wai description it's useless, and I must say I also never used it.
>
> I must admit it was a leasy assumed reaction
>
> Jacques
>
> From: "David E Jones" <[hidden email]>
>> 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 <[hidden email]> 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" <[hidden email]>
>>>> 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.

[Mike Z]

I just looked in 11.04, and it says:

Content Path Prefix:  Define the Prefix of the content placement file .
Start up by a / and finish without /
Template Path Prefix:  Define the skeleton of the content placement file .
Start up by a / and finish without /

This MAY be useful to someone, if it was understood better.  Maybe add it
to Catalog Help?

On Sun, Jun 10, 2012 at 10:29 AM, Jacques Le Roux <
[hidden email]> wrote:

> BTW, if ever I do anything about that it will be noted in Attic page in
> wiki, still with the slim-down priority in mind.
>
> Jacques
>
> From: "Jacques Le Roux" <[hidden email]>
>
>  I thought that if nobody uses it removing from UI will not be a big deal.
>> Else if someone uses it, then s/he will react and, if we
>> are lucky, explains why it's there and what for it's used. From Wai
>> description it's useless, and I must say I also never used it.
>>
>> I must admit it was a leasy assumed reaction
>>
>> Jacques
>>
>> From: "David E Jones" <[hidden email]>
>>
>>> 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 <[hidden email]>
>>> 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" <[hidden email]>
>>>>
>>>>> 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<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<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.
>>>>>
>>>>

[Jacques Le Roux]

All is in the sentence
> if it was understood better.

I guess we could do some retro-engineering. At the moment I have to time to put in that.

No needs to say, all good wills are welcome...

Jacques


From: "Mike" <[hidden email]>

>I just looked in 11.04, and it says:
>
> Content Path Prefix:  Define the Prefix of the content placement file .
> Start up by a / and finish without /
> Template Path Prefix:  Define the skeleton of the content placement file .
> Start up by a / and finish without /
>
> This MAY be useful to someone, if it was understood better.  Maybe add it
> to Catalog Help?
>
> On Sun, Jun 10, 2012 at 10:29 AM, Jacques Le Roux <
> [hidden email]> wrote:
>
>> BTW, if ever I do anything about that it will be noted in Attic page in
>> wiki, still with the slim-down priority in mind.
>>
>> Jacques
>>
>> From: "Jacques Le Roux" <[hidden email]>
>>
>>  I thought that if nobody uses it removing from UI will not be a big deal.
>>> Else if someone uses it, then s/he will react and, if we
>>> are lucky, explains why it's there and what for it's used. From Wai
>>> description it's useless, and I must say I also never used it.
>>>
>>> I must admit it was a leasy assumed reaction
>>>
>>> Jacques
>>>
>>> From: "David E Jones" <[hidden email]>
>>>
>>>> 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 <[hidden email]>
>>>> 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" <[hidden email]>
>>>>>
>>>>>> 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<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<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.
>>>>>>
>>>>>
>

[Pierre Smits]

Jacques, Mike and Wai,

Please create a JIRA so that this issue is not forgotten. If you feel that
you can assist in improving the situation (whether removing the
functionality, improving it and/or creating the help page) please provide
your patch as well.

Regards,

Pierre

2012/6/10 Jacques Le Roux <[hidden email]>

> All is in the sentence
>
>  if it was understood better.
>>
>
> I guess we could do some retro-engineering. At the moment I have to time
> to put in that.
>
> No needs to say, all good wills are welcome...
>
> Jacques
>
>
> From: "Mike" <[hidden email]>
>
>  I just looked in 11.04, and it says:
>>
>> Content Path Prefix:  Define the Prefix of the content placement file .
>> Start up by a / and finish without /
>> Template Path Prefix:  Define the skeleton of the content placement file .
>> Start up by a / and finish without /
>>
>> This MAY be useful to someone, if it was understood better.  Maybe add it
>> to Catalog Help?
>>
>> On Sun, Jun 10, 2012 at 10:29 AM, Jacques Le Roux <
>> [hidden email]> wrote:
>>
>>  BTW, if ever I do anything about that it will be noted in Attic page in
>>> wiki, still with the slim-down priority in mind.
>>>
>>> Jacques
>>>
>>> From: "Jacques Le Roux" <[hidden email]>
>>>
>>>  I thought that if nobody uses it removing from UI will not be a big
>>> deal.
>>>
>>>> Else if someone uses it, then s/he will react and, if we
>>>> are lucky, explains why it's there and what for it's used. From Wai
>>>> description it's useless, and I must say I also never used it.
>>>>
>>>> I must admit it was a leasy assumed reaction
>>>>
>>>> Jacques
>>>>
>>>> From: "David E Jones" <[hidden email]>
>>>>
>>>>  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 <
>>>>> [hidden email]>
>>>>> 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" <[hidden email]>
>>>>>>
>>>>>>  Does anyone know how a catalog's "Template Path Prefix" field is used
>>>>>>> from
>>>>>>> http://demo-trunk.ofbiz.**apac**he.org/catalog/control/**<http://apache.org/catalog/control/**>
>>>>>>> EditProdCatalog?prodCatalogId=****DemoCatalog<http://demo-**
>>>>>>> trunk.ofbiz.apache.org/**catalog/control/**
>>>>>>> EditProdCatalog?prodCatalogId=**DemoCatalog<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<http:**//ofbiz.135035.n4.nabble.com/**
>>>>>>> Proposal-to-remove-catalog-s-**Template-Path-Prefix-field-**
>>>>>>> from-user-interface-tp4633296.**html<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.
>>>>>>>
>>>>>>>
>>>>>>
>>

[Wai]

Hello David,

I'm not sure to whom you're addressing your post.  Since I'm the originator, I'll give a reply.

A catalog's "Template Path Prefix" field is used to specify the path prefix to a particular screen widget file containing the screen to use for listing products in the ecommerce website.

The reason for this post is that the code blindly prepends the value of this field to the category's "Detail Screen" field.  Resulting in a final file path that will "always" cause an exception.  Hence this code had never worked.

As you can see from the original posting, the resulting path to the target screen to use makes no sense.

Since this code never worked since 2006. It is therefore reasonable that no one has ever used this feature.  And it is unlikely that the originator of the code could possibly have used it successfully unless he made changes to his own version of ofbiz.

That's why I proposed to have this code and associated ui be hidden or removed.  If not the code, at least hide the ui part.

I'll log a jira on this so that the community can keep track.

Wai

[Wai]

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 url 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

[Wai]

One additional comment.
"Template Path Prefix" and "Content Path Prefix" as it is implemented would not make sense in a multitenant ofbiz setup.

[Mike Z]

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 <[hidden email]> 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.
>

[Jacques Le Roux]

Thanks for the effort Mike,

Now we know what we are speaking about.  Seems You are concerned by Multitenant Wai?

Jacques


From: "Mike" <[hidden email]>

> 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 <[hidden email]> 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.
>>
>

[Wai]

@Mike

Thanks for the clarification.  The "Content Path Prefix" is clear now.  Hence, in practice, it would mean that an ofbiz owner would have to create a mount point for each NFS mount in the image component.  I agree that this feature is useful in  an ofbiz single-tenant operating mode.  But it would not be practical in a multi-tenant operating mode.

As a side note. If ofbiz is to be multi-tenant capable. I think a consideration should be taken for any feature that would conflict with this.

@Jacques

Yes, part of my concern about this issue does deal with multi-tenant support.

Thanks,
Wai

[Pierre Smits]

This should also work in a multi-tenant scenario, without being extra complicating from an OFBiz point of view. This, because of the fact that each tenant has its own data storage (db).

Of course, from a file storage mgt point of view this means that each tenant should have the means to upload the images with tools outside of the OFBiz environment. E.g FTP to their own file point location. But that is not unsolvable...

Regards,

Pierre Smits

Verstuurd vanaf mijn iPad

Op 12 jun. 2012 om 12:52 heeft Wai <[hidden email]> het volgende geschreven:

> @Mike
>
> Thanks for the clarification.  The "Content Path Prefix" is clear now.
> Hence, in practice, it would mean that an ofbiz owner would have to create a
> mount point for each NFS mount in the image component.  I agree that this
> feature is useful in  an ofbiz single-tenant operating mode.  But it would
> not be practical in a multi-tenant operating mode.
>
> As a side note. If ofbiz is to be multi-tenant capable. I think a
> consideration should be taken for any feature that would conflict with this.
>
> @Jacques
>
> Yes, part of my concern about this issue does deal with multi-tenant
> support.
>
> 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-tp4633296p4633461.html
> Sent from the OFBiz - User mailing list archive at Nabble.com.