Hello,
So if I understand you want a stabilized 4.0.3
edition of Jahia? Mmmh looks exactly like a
concept of patches and service packs and that is
why we released a 4.0.4, a 4.0.5 or a 4.0.6! So
you prefer trying spending time backporting some
piece of code in the kernel rather than just
applying a service pack? Please note that the
Jahia engines are a quite complex piece of
architecture. So modifying something somewhere
may perfectly break other features. So we clearly
do not encourage you to "fork" an old and
deprecated Jahia release. This will then become
harder to maintain and to evolve. So why could
you not simply patch your Jahia server (includung
that the Jahia service packs are provided free of
charge!) if this bug was already corrected?
Stéphane
At 14:25 06/07/2005, you wrote:
Serge,
I have developed a site with a later version
(4.0.5) and had no problems. Unfortunately we
are unable to upgrade this site. I was looking
for pointers as to where this may be occurring
and perhaps able to dig a little into the jsp side of the code...
Regards
Serge Huber wrote:
Did you try this with the latest stable release of Jahia ?
Regards,
Serge Huber.
CodeMonkey wrote:
I am running Jahia 4.0.3 build 5580
In an existing container I have defined three new fields, namely:
<content:declareField
name='<%="redirectContributorLinkId" + id%>'
title="Contributed by link ID"
titleKey="redirectContributorLinkId"
bundleKey="<%=resBundleID%>" type="SmallText" />
<content:declareField
name='<%="redirectLinkId" + id%>'
title="Redirect link ID"
titleKey="redirectLinkId" bundleKey="<%=resBundleID%>" type="SmallText" />
<content:declareField
name='<%="redirectSourceLinkId" + id%>'
title="Redirect source link ID"
titleKey="redirectSourceLinkId"
bundleKey="<%=resBundleID%>" type="SmallText" />
When I try to update an existing container with new values for these fields:
1. If I click on Apply after updating the
field, the field changes from a html input to
text which says 'Value:' without the updated
value appearing (this is no longer an html
input field and cannot be edited). The value
is not stored. As an aside, any other fields
below this field in the update pane also
prints out 'Value:' but appended to this is the actaul stored
2. If I click on OK the field does not get updated.
If I add a new container, I can updated/edit
these fields and they work as expected.
Also when I only add one extra field, I am
able to update/edit this field. If I
subsequently add a second field, the above behaviour is exhibited.
Any pointers to the problem?
- -- --- -----=[ scroisier at jahia dot com ]=---- --- -- -
CEO - Jahia Ltd, 45 rue de la gare, 1260 Nyon (Switzerland)
Jahia : The Java Unified Web Platform
www.jahia.org - The community and product web site
www.jahia.com - Our commercial services company
www.collaborativesource.org - The Collaborative Source Initiative
