Dirk --

We (and by that I mean "you") should probably modify one of the servlet filters to stash this into request scope rather than assume that commonheader will do this. That's the direction we should be taking for 'global' JSTL variables. That way, template authors can't mess things up (inadvertently or otherwise).

Andrew


On May 2, 2008, at 4:03 PM, Dirk Frederickx wrote:

Terry,

The format string is read from the prefs variable.
But, in order to get this to work, the prefs variable must be set first.
Check you commonheader.jsp whether it contains following stuff:

<%
  Preferences.setupPreferences(pageContext);
%>

This will put the "prefs" variable in the pageContext, with all
user-prefs read either from the user cookie or from the
jspwiki.properties.

Good luck,
   dirk

On Fri, May 2, 2008 at 9:53 PM, Terry Steichen <[EMAIL PROTECTED]> wrote:
I'm trying to integrate my application which was based on 2.4.104 into
2.6.2

I got most of the stuff working, but I'm getting an error which seem to
stem from the use of this tag (in PageActionsBottom.jsp):

      <wiki:PageDate format='${prefs["DateFormat"]}' />


I'm assuming that the 'prefs' notation refers to a default that has to
be set in the jspwiki.properties, but I'm not sure just what this
notation is supposed to do (though I find it scattered throughout the
newer version of JSP's).

Could someone explain just what this kind of notation is and how it's
used?

PS: I added "jspwiki.defaultprefs.template.dateformat =dd-MMM-yyyy
HH:mm" to jspwiki.properties, but that didn't appear to help.

PSS: I'm keeping track of the changes and adjustments I've had to make,
so will document this when I'm all (successfully) done.







Reply via email to