Re: Access to config date

Hi Tom:

In message
<CO3PR08MB79577C3EED488A0F51CB69EDCAB39@CO3PR08MB7957.namprd08.prod.
outlook.com>, Tom Ekberg writes:

>I'm am working on getting Roundup 2.1 ready to replace our Roundup

2.1 or 2.2? Granted 2.2 isn't due for three weeks but.... In addition
you can help test 9-).

>1.6+ system (a few patches were installed after 1.6 was released). We
>use the classic Zope HTML code. I did a comparison between our
>version of the classic Zope code for Roundup 1.6+ which we store in a
>'common/' directory hierarchy. I did a diff between the classic
>Roundup 2.1 code in share/roundup/templates/classic/html/ with the
>code in common/html. This is part of the diff output for
>html/user.register.html:
>
>- tal:replace="db/config/TRACKER_NAME" /></span>
>+ tal:replace="config/TRACKER_NAME" /></span>
>
>The '-' is for the Roundup 2.1 code and the '+' is our 'common'
>code. We have several pages that reference config data. Has this
>changed in Roundup 2.1?

Not that I know of.  AFAIK those are all in the context object of the
templating system. The config variable is still a part of that context
object in cgi/templating.py.

However is that line five lines from the top of the file?

If so I think your common code may have been tweaked. The prior change
to that line was in 2009. That and earlier versions of that line show
some variant of db/config/TRACKER_NAME.  It's possible the origin of
that code predates the addition of config to the context object in
revision 77920c42aeb9 (2002).

>Can I stick with ‘config/TRACKER_name, or do I change that to
>db/config/TRACKER_NAME?

I claim you should be able to stick with config/TRACKER_NAME.

--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.


_______________________________________________
Roundup-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/roundup-users