Here you find changes that require a admin intervention.
On our development history page is a list of all "visible changes" and improvements.
New updates on the pylucid comments system commit 2f2c809490b needs django-tools v0.11.0 - Please update, e.g:
The example used git readonly clone url. If you use subversion do this:
If you have git write access, use this:
You can also use Web based virtualenv package update
See also: update existing PyLucid environment
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:
more info: about static media files
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:
You must change all your templates:
The easiest way is you use:
with these values:
| Find string: | <!-- page_messages --> |
| Replace string: | {% include "pylucid/includes/page_msg.html" %} |
| Content type: | DBTemplate |
(You should select all languages and all sites)
907f47 needs django-tools v0.8.1 - Please update (howto, see above)
You have to change the url to these files:
e.g.:
To see the plugin menu point, you must reinit all plugins with:
You should reinit all plugins with: PyLucid admin menu -> PyLucid -> install plugins
It's needed that you call:
Otherwise you get page_msg errors like:
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
You must update your index.cgi file (otherwise you get the error: "ImportError: No module named cgi_server"), e.g:
important: After this you must edit the index.cgi and insert your path to PyLucid_env, see: edit .cgi file
Important: 2569 and 2572 needs some admin intervention otherwise a svn up makes your side down!
(obsolete since changes from 09.04.2010)
see also:
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!
The new JS-SHA-Login implementation 2572 has changed some JavaScript media files:
| media/PyLucid/pylucid_js_tools.js | (modified) |
| media/PyLucid/shared_sha_tools.js | (modified) |
| media/PyLucid/sha_login_input_password.js | (deleted) |
Please update your media files, if not done in svn update...
You find the files in the virtual environment, here:
Since 2577 you will see only "loading..." if media files not updated.
You must run:
to see the new menu point: PyLucid admin menu -> tools -> overwrite templates
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.
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
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.:
(see also: static media files)
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:
(Note: This SQL statement doesn't work with SQlite!)