unittest for PyLucidCommonMiddleware

[JensDiemer]

For the first time installation the two django middlewares "SessionMiddleware?" and "AuthenticationMiddleware?" must be deactivated in the settings.py (per default in the settings_example.py). Because the SessionMiddleware? access on tables how not exists by the time.

After a syncdb the session table exists and the middleware can be activated.

We should be find a better way to handle this.

To this related: We should be find a better error handling if the user request a cms page and PyLucid is not installed.

[JensDiemer]

See also ticket:84

[JensDiemer]

One idea:

Split the settings.py into something like this:

• shared settings (e.g. database accounts)
• _install section settings (without the two django middlewares)
• normal settings (with the two django middlewares)

Use different Handlers. One for the install section (with the install section settings) and one for the normal view...

[JensDiemer]

Fixed this in changeset:1505 with the new PyLucidCommonMiddleware.

But the unittest failed for this: /pylucid/browser/trunk/pylucid/tests/install_section.py see also: http://pylucid.org/phpBB2/viewtopic.php?p=1138#1138

[JensDiemer]

Replying to JensDiemer:

Fixed this in changeset:1505 with the new PyLucidCommonMiddleware. But the unittest failed for this: /pylucid/browser/trunk/pylucid/tests/install_section.py see also: http://pylucid.org/phpBB2/viewtopic.php?p=1138#1138

fixed in changeset:1641 see also: http://www.pylucid.org/phpBB2/viewtopic.php?p=1231#1231