↑ info  #

Here you find changes that require a admin intervention.

On our development history page is a list of all "visible changes" and improvements.

↑ 25.08.2010 - update django-tools to v0.11  #

New updates on the pylucid comments system commit 2f2c809490b needs django-tools v0.11.0 - Please update, e.g:

1
2
3

~$ cd /PyLucid_env/bin
~/PyLucid_env/bin$ source activate
(PyLucid_env)~/PyLucid_env/bin$ pip install --upgrade --verbose --editable=git+git://github.com/jedie/django-tools.git#egg=django-tools

The example used git readonly clone url. If you use subversion do this:

1

(PyLucid_env)~/PyLucid_env/bin$ pip install --upgrade --verbose --editable=http://svn.github.com/jedie/django-tools.git#egg=django-tools

If you have git write access, use this:

1

(PyLucid_env)~/PyLucid_env/bin$ pip install --upgrade --verbose --editable=git+git@github.com:jedie/django-tools.git#egg=django-tools

You can also use Web based virtualenv package update
See also: update existing PyLucid environment

↑ 08.07.2010 - Add ColorMirror Editor  #

With commit c7f6ea0, we include CodeMirror JS Editor.

If you copied (and not symlink) the PyLucid mediafiles, you must update them. e.g. Just recopy:

1

/home/FooBar$ cp -r PyLucid_env/src/pylucid/pylucid_project/media/* /var/www/YourSite/media/

more info: about static media files

↑ 01.07.2010 - change page_msg, use django messages  #

With commit cb2c2a2, we removed our own page_msg middleware solution and used the new django messages framework.

You must update django-tools and you templates:

↑ update templates  #

You must change all your templates:

1
2

-     <!-- page_messages -->
+     {% include "pylucid/includes/page_msg.html" %}

The easiest way is you use:

• PyLucid admin menu / change content / find and replace

with these values:

(You should select all languages and all sites)

↑ 15.06.2010 - new django-tools needed.  #

907f47 needs django-tools v0.8.1 - Please update (howto, see above)

↑ 26.05.2010 - own jquery.js file removed  #

• 619086 removed the file /media/PyLucid/jquery.js (We used jquery from Django since 29.01.2010.)

You have to change the url to these files:

1
2
3
4
5

- /media/PyLucid/jquery.js
+ {{ Django_media_prefix }}js/jquery.min.js

- /media/PyLucid/pylucid_js_tools.js
+ {{ PyLucid_media_url }}pylucid_js_tools.js

e.g.:

1
2
3
4
5

- <script src="/media/PyLucid/jquery.js" onerror="JavaScript:alert('Error loading file [/media/PyLucid/jquery.js] !');" type="text/javascript" /></script>
+ <script src="{{ Django_media_prefix }}js/jquery.min.js" onerror="JavaScript:alert('Error loading file [{{ Django_media_prefix }}js/jquery.min.js] !');" type="text/javascript" /></script>

- <script src="/media/PyLucid/pylucid_js_tools.js" onerror="JavaScript:alert('Error loading file [/media/PyLucid/pylucid_js_tools.js] !');" type="text/javascript" /></script>
+ <script src="{{ PyLucid_media_url }}pylucid_js_tools.js" onerror="JavaScript:alert('Error loading file [{{ PyLucid_media_url }}pylucid_js_tools.js] !');" type="text/javascript" /></script>

↑ 25.05.2010 - New: Clone existing Design  #

• 1fbbbad...184218a add "clone design" function. More info at: Customise PyLucid workflow

To see the plugin menu point, you must reinit all plugins with:

• PyLucid admin menu -> PyLucid -> install plugins

↑ 06.05.2010 - resort the admin menu  #

• 65bda3f add PyLucid admin menu -> edit look -> switch design
• 5e9e34e - The PyLucid admin menu entries are resorted.

You should reinit all plugins with: PyLucid admin menu -> PyLucid -> install plugins

↑ 30.04.2010 - "overwrite template" renamed  #

• fb9f389 - We renamed "overwrite template" to "override template".

It's needed that you call:

• PyLucid admin menu -> PyLucid -> install plugins

Otherwise you get page_msg errors like:

• Can't resolve url u'Tools-overwrite_template' for plugin u'overwrite template'

↑ 09.04.2010 - no database info in settings.py - cgi needs python 2.5  #

↑ no database info in settings.py  #

• 2627 - remove database connection info from settings.py. The user must set this in his local_settings.py!

So the user get a real error, if he e.g. didn't activate virtualenv and runs "manage.py syncdb". Otherwise a SQlite test.db3 would be created.

With this, the database scheme must not be updates, see changes from 11.03.2010

↑ cgi needs python 2.5  #

• 2626 - Python 2.5 is needed. We removed the local cgi_server.py file and used CGIHandler from wsgiref, see: http://trac.pylucid.net/changeset/2626#file3

You must update your index.cgi file (otherwise you get the error: "ImportError: No module named cgi_server"), e.g:

1
2

/home/FooBar$ cp scripts/cgi_scripts/index.cgi /var/www/YourSite/
/home/FooBar$ chmod +x /var/www/YourSite/index.cgi

important: After this you must edit the index.cgi and insert your path to PyLucid_env, see: edit .cgi file

↑ 11.03.2010 - settings.DATABASES and new JS-SHA-Login  #

Important: 2569 and 2572 needs some admin intervention otherwise a svn up makes your side down!

↑ database settings  #

(obsolete since changes from 09.04.2010)

• You must update your database settings into the new django format, e.g.:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12

-DATABASE_ENGINE = 'sqlite3'    # 'postgresql', 'mysql', 'sqlite3' or 'ado_mssql'.
-DATABASE_NAME = 'test.db3'     # Or path to database file if using sqlite3.
-DATABASE_USER = ''             # Not used with sqlite3.
-DATABASE_PASSWORD = ''         # Not used with sqlite3.
-DATABASE_HOST = ''             # Set to empty string for localhost. Not used with sqlite3.
-DATABASE_PORT = ''             # Set to empty string for default. Not used with sqlite3.
+DATABASES = {
+    'default': {
+        'ENGINE': 'django.db.backends.sqlite3',
+        'NAME': 'test.db3'
+    }
+}

see also:

• http://docs.djangoproject.com/en/dev/ref/settings/#setting-DATABASES
• http://docs.djangoproject.com/en/dev/intro/tutorial01/#database-setup

If you use a the old settings format in your local_settings.py, you will get 'database tables doesn't exists' errors.
Because, if both settings scheme exist, Django used the new one. So it didn't used your old scheme from your local_settings.py, it used the new scheme from settings.py!

↑ login  #

The new JS-SHA-Login implementation 2572 has changed some JavaScript media files:

Please update your media files, if not done in svn update...

You find the files in the virtual environment, here:

• /home/FooBar/PyLucid_env/src/pylucid/pylucid_project/media

Since 2577 you will see only "loading..." if media files not updated.

↑ 10.03.2010 - mark first/last main menu entry  #

• 2567 - The main menu template main_menu_items.html changed, you must only recognised this, if you overwrite this template:
  Diff

  1 2 3 4 5 6 7 8 9 10 11

  Index: branches/0.9/pylucid_project/pylucid_plugins/main_menu/templates/main_menu/main_menu_items.html =================================================================== --- branches/0.9/pylucid_project/pylucid_plugins/main_menu/templates/main_menu/main_menu_items.html +++ branches/0.9/pylucid_project/pylucid_plugins/main_menu/templates/main_menu/main_menu_items.html @@ -4,5 +4,5 @@ {% if node.visible %} {% if node.current %}<strong>{% endif %} - <a href="{{ node.pagemeta.get_absolute_url }}" hreflang="{{ node.pagemeta.language.code }}" title="{{ node.pagemeta.get_title }}" class="level_{{ node.level }}{% if node.active %} active{% endif %}{% if node.current %} current{% endif %}">{{ node.pagemeta.get_name }}</a> + <a href="{{ node.pagemeta.get_absolute_url }}" hreflang="{{ node.pagemeta.language.code }}" title="{{ node.pagemeta.get_title }}" class="{{ node.css_class }}">{{ node.pagemeta.get_name }}</a> {% if node.current %}</strong>{% endif %} {% endif %}

↑ 02.03.2010 - NEW: tools / template overwrite  #

You must run:

• PyLucid admin menu -> PyLucid -> install plugins

to see the new menu point: PyLucid admin menu -> tools -> overwrite templates

↑ 01.03.2010 - Headline Anchor in admin  #

We activate the TOC/HeadLineAnchor in the django admin panel with 2553.
The static file media/PyLucid/pylucid_admin.css has been updated.
Possibly, you must copy the file into your media directory.

↑ 18.02.2010 - link to the feed page, in update journal table  #

Since 2536 you should create a 'update_journal' PluginPage. Otherwise staff members get this error message on a page witch contains the lucidTag update_journal:
{{{ Can't get a PluginPage for plugin 'update_journal', please create one. }}}
See also: user manual

↑ 29.01.2010 - Use jquery from django  #

Django contains jQuery since Django changeset 12297. So we delete our own copy of jQuery and use it from django.

You must copy jquery.min.js into your media path, if you get the JavaScript alert error:
{{{ Error loading file [/django_media/js/jquery.min.js] ! }}}
Copy django/contrib/admin/media/js/jquery.min.js into your django media path, e.g.:

1

/home/FooBar$ cp PyLucid_env/src/django/django/contrib/admin/media/js/jquery.min.js /var/www/YourSite/media/django/js/

(see also: static media files)

↑ 05.11.2009 - Changed the ManyToManyField in the design model.  #

With Changeset 2348, among other things, we changed the ManyToManyField in the design model. It seems that this is problematic in later django updates.

You must change a database column name if you get this error:
{{{ OperationalError: (1054, "Unknown column 'pylucid_design_headfiles.editablehtmlheadfile_id' in 'on clause'") }}}

Solution: Change the column name:

1

ALTER TABLE `pylucid_design_headfiles` CHANGE `pylucid.editablehtmlheadfile_id` `editablehtmlheadfile_id` INT( 11 ) NOT NULL

(Note: This SQL statement doesn't work with SQlite!)

↑ sub pages:  #

↑ See also:  #

• development history of PyLucid
• History
• How to update your old Plugins
• Roadmap