[Zope-Coders] Creating a "default" error_log object

[Toby Dickenson]

On Thursday 18 Jul 2002 4:22 pm, Chris McDonough wrote:

> I propose this:
>
> - first of all, get rid of Data.fs.in.  It's dead, Jim.  The
>   application init code does it all anyway.
>
> - Second of all, create all "deletable" default objects only when
>   populating a brand new database.  Change default initialization to
>   write a  single flag out to signify that the deletable default
>   elements have been created (the whole lot of them, sessions,
> examples,
>   standard "methodish" objects, etc).  This flag signifies a
> terminal
>   state for deletable default object creation -- once it is written,
>   Zope initialization will never attempt to create future
>   default objects within this database, even when a user upgrades to
>   the latest Zope version.

It only needs a seperate flag if the creation is automatic. If creation n=
eeded=20
a specific management action, then I dont think it is a problem that you=20
_can_ create yet another 'Examples' folder after deleting the first - so =
long=20
as you are not forced to.

> - Add a method with a well-known name on the application object to
>   "upgrade" to the latest default object scheme.  Document this
>   method.

Maybe a "Standard Fixtures" page in control panel with sections that
say things like:

* This database already has a browser_id_manager object.

* This database doesnt have an Examples folder.    [add one now]

* This database doesnt have a standard_template.pt object. A new
  database created today would have one, and we strongly recommend
  that you fix this now                              [fix it now]=20


Hmmm, maybe the main control panel page needs a warning if you are missin=
g an=20
important standard object like standard_template.pt