Menu:

v0.8.5 changes

18.07.2008 - RSS plugin updates

The title argument is obsolete. We use the title directly from the feed.

09.07.2008 - rewriting preferences 2

With changeset 1544, 1548, 1555 and 1665-1660 we change many things around the Preferences. To use the current trunk, do these steps:

You find the new Preference Editor under "sub menu/miscellaneous"

31.05.2008 - plugin models

With changeset:1612 plugin can have his own django ORM models, see plugin models.

You must add 'PyLucid.system.PyLucidPlugins' in your settings.INSTALLED_APPS:

Python
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
# A tuple of strings designating all applications that are enabled in this
# Django installation. Each string should be a full Python path to a Python
# package that contains a Django application
INSTALLED_APPS = (
    'django.contrib.auth',
    'django.contrib.contenttypes',
    'django.contrib.sessions',
    'django.contrib.sites',
    'django.contrib.admin',
    'PyLucid',
    'PyLucid.system.PyLucidPlugins',
)

28.05.2008 - dynamic admin sub menu

Since changeset 1602 we replace the static admin sub menu with a dynamic one. Every Plugin can insert a own sub menu entry via the plugin config data.

This change should be backwards compatible, but you must reinit the plugin "admin_menu" to get the right sorting of the sections.

The back links plugin used the new preferences. So a reinit of the plugin must be done.

20.05.2008 - page_msg

With changeset 1585 we changed the page messages system, because of a broken concept described in ticket 193.

We created a new middleware for the page messages. So you must update your settings.py file and insert the new middleware 'PyLucid.middlewares.pagemessages.PageMessagesMiddleware' settings_example.py diff

You must change your template, too. But we inserted a auto update routine for this:

If you must update your template by hand:

Diff
1
2
3
4
5
6
7
8
-   {% if messages %}
-     <fieldset id="page_msg"><legend>page message</legend>
-     {% for message in messages %}
-       {{ message }}<br />
-     {% endfor %}
-     </fieldset>
-   {% endif %}
+   <!-- page_messages -->

25.03.2008 - new middlewares (updated 18.07.2008)

With changeset 1505 we implement a work-a-round for the django middleware problematic (see also ticket 87 ).

Update: with changeset 1510 & changeset 1511 we refactor the cache mechanism and added a new cache middleware.

Update2: changeset 1585: new page_msg system. Use a middleware to make page_msg lazy, see: ticket 193.

You must update the MIDDLEWARE_CLASSES part of your settings.py:

Python
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
MIDDLEWARE_CLASSES = (
    # Insert a statistic line into the generated page:
    'PyLucid.middlewares.pagestats.PageStatsMiddleware',


    'PyLucid.middlewares.pagemessages.PageMessagesMiddleware',



    # PyLucidCommonMiddleware loads the django middlewares:
    #    - 'django.contrib.sessions.middleware.SessionMiddleware'
    #    - 'django.contrib.auth.middleware.AuthenticationMiddleware'
    #    - 'django.middleware.locale.LocaleMiddleware'
    'PyLucid.middlewares.common.PyLucidCommonMiddleware',



    # Cache all anonymous cms page request, if CACHE_BACKEND worked.
    'PyLucid.middlewares.cache.CacheMiddleware',



    'django.middleware.common.CommonMiddleware',
    'django.middleware.doc.XViewMiddleware',


    # Add a human readable anchor to every html headline:
    'PyLucid.middlewares.headline_anchor.HeadlineAnchor',
)

25.03.2008 - Headline anchor

Not really a Backwards-incompatible change.

With changeset 1503 we add a new middleware called 'HeadlineAnchor'. It's inserted a anchor permalink to all html headlines. If you will use it, you must change you settings and you should edit your global Stylesheet.

You must activate the HeadlineAnchor middleware before the PageStatsMiddleware:

Python
1
2
3
4
5
6
7
8
9
...
MIDDLEWARE_CLASSES = (
    ...
    # Add a human readable anchor to every html headline:
    'PyLucid.middlewares.headline_anchor.HeadlineAnchor',

    # Insert a statistic line into the generated page:
    'PyLucid.middlewares.pagestats.PageStatsMiddleware',
)

You can add this to your global Stylesheet:

CSS
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
.anchor {
  text-decoration:none;
}
.anchor:hover {
  color:#808080;
  text-decoration:underline;
}
.anchor:hover:after {
   content:" #";
}

04.03.2008 - Page archive

For the new page archive you must go into the _install section and do this:

28.02.2008 - new unit test handling

To use the new unitests, you must insert this into your settings.py:

Python
1
2
# Unit test runner
TEST_RUNNER = 'tests.run_tests'

More information on the The PyLucid unittests documentation

27.02.2008 - new internal page handling

The new internal page handling needs some changes.

Please consider the new place for the internal page files: ./media/PyLucid/internal_page/

We change some media path information in the settings.py: settings_example.py diff
You must add this:

Python
1
2
3
PYLUCID_MEDIA_DIR = "PyLucid"
INTERNAL_PAGE_DIR = "internal_page"
CUSTOM_INTERNAL_PAGE_DIR = "custom"

13.02.2008 - new filemanager plugin

For the new filemanager plugin you need a new tuple in your settings.py:

Diff
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
Index: trunk/pylucid/PyLucid/settings_example.py
===================================================================
--- trunk/pylucid/PyLucid/settings_example.py (revision 1340)
+++ trunk/pylucid/PyLucid/settings_example.py (revision 1388)
@@ -189,4 +189,11 @@
 #     Examples-3: "http://django.media.your_domain.net/"
 ADMIN_MEDIA_PREFIX = "/django/contrib/admin/media/"
+
+# Base path for the filemanager plugin
+# You can add more path for the plugin.
+FILEMANAGER_BASEPATHS = (
+    MEDIA_ROOT,
+    #"./static/",
+)
 
 """

http://trac.pylucid.net/changeset/1388/trunk/pylucid_project/PyLucid/settings_example.py

You must install + activate the plugin "filemanager" with the "Plugin administration".
Also you must reinit the plugin "admin_menu".

See also:

04.01.2008 - main_menu plugin

We changed the main_menu plugin for W3C valid output.
You must reinit the plugin in the _install section!

Maybe you must change the Stylesheet anchor from "a .current" to "a.current" in your global CSS.

More info soon.

We added some new features in the backlinks plugin. You must reinit the plugin with the "Plugin Administration" to insert the new internal pages for the plugin output.

The new features are documented here

11.12.2007 - "INSTALL_PASS_HASH" renamed to "INSTALL_PASSWORD_HASH"

We renamed the settings.py variable "INSTALL_PASS_HASH" to "INSTALL_PASSWORD_HASH".
Because, now the name contains the word "PASSWORD" and django will hide the value from a debug traceback.
See also: http://www.djangoproject.com/documentation/settings/#debug

See also: