[Grok-dev] megrok.layout in grok1.1rc1: ConfigurationConflictError

[Souheil CHELFOUH]

Hello,

Thank you for the report.
megrok.layout is moving a lot and lately has been modified to work
with the latest grokcore.message and grokui.admin.
The version useable with grok1.1 rc1 is the 0.9.

About the warning messages, they are not due to a "dirty" package, but
to the grokcore.view grokking.
This is a known flaw that is to be changed in the forthcoming
releases. The fix already exists but is not yet applied to the trunk.

Cheers,

2010/4/6 Roger Erens <roger.erens at e-s-c.biz>:
> Hi,
>
> when I create a fresh Grok1.1rc1 project and add megrok.layout in
> setup.py to the install_requires list and running bin/buildout, I get
> a ConfigurationConflictError(conflicts) when trying to start the
> server.
>
> It seems to be solved when I change versions.cfg to have it read
> grokui.admin = 0.6.1
> instead of the default 0.3.3
>
> Is this change enough? The server runs now, but for release 1.1 some
> cleaning up seems necessary since it starts up with a lot of warnings
> about unassociated templates, see below.
>
> Another thing: is it intentional that at the top of the grok
> administration interface page there are only links to 'Applications'
> and 'Serve setup'; whereas in grokui.admin0.3.3 there was also a link
> to 'Documenation'?
>
> Cheers,
>
> Roger
>
> roger at HP-U:~/ge/yt2$ bin/paster serve parts/etc/deploy.ini
> 2010-04-06 07:53:33,073 WARNING [root] Developer mode is enabled: this
> is a security risk and should NOT be enabled on production servers.
> Developer mode can usually be turned off by setting the `devmode`
> option to `off` or by removing it from the instance configuration file
> completely.
> /home/roger/.buildout/eggs/grokcore.view-1.13.2-py2.6.egg/grokcore/view/templatereg.py:91:
> UserWarning: Found the following unassociated template(s) when
> grokking 'grokui.base.layout': statusmessages, menuviewlet, authors,
> banner, logininformation.  Define view classes inheriting from
> grok.View to enable the template(s).
>  warnings.warn(msg, UserWarning, 1)
> /home/roger/.buildout/eggs/grokcore.view-1.13.2-py2.6.egg/grokcore/view/templatereg.py:91:
> UserWarning: Found the following unassociated template(s) when
> grokking 'grokui.base.viewlets': grokuilayout.  Define view classes
> inheriting from grok.View to enable the template(s).
>  warnings.warn(msg, UserWarning, 1)
> /home/roger/.buildout/eggs/grokcore.view-1.13.2-py2.6.egg/grokcore/view/templatereg.py:91:
> UserWarning: Found the following unassociated template(s) when
> grokking 'grokui.admin.applications': rename, server.  Define view
> classes inheriting from grok.View to enable the template(s).
>  warnings.warn(msg, UserWarning, 1)
> /home/roger/.buildout/eggs/grokcore.view-1.13.2-py2.6.egg/grokcore/view/templatereg.py:91:
> UserWarning: Found the following unassociated template(s) when
> grokking 'grokui.admin.server': rename, applications.  Define view
> classes inheriting from grok.View to enable the template(s).
>  warnings.warn(msg, UserWarning, 1)
> /home/roger/.buildout/eggs/grokcore.view-1.13.2-py2.6.egg/grokcore/view/templatereg.py:91:
> UserWarning: Found the following unassociated template(s) when
> grokking 'grokui.admin.views': applications, server.  Define view
> classes inheriting from grok.View to enable the template(s).
>  warnings.warn(msg, UserWarning, 1)
> 2010-04-06 07:53:37,299 WARNING [ZODB.blob] (3103) Blob dir
> /home/roger/ge/yt2/var/blobstorage/ has insecure mode setting
> 2010-04-06 07:53:37,303 INFO [zope.app.generations] main db: evolving
> in mode EVOLVEMINIMUM
> Starting server in PID 3103.
> serving on http://127.0.0.1:8080
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> https://mail.zope.org/mailman/listinfo/grok-dev
>