Default settings for FeinCMS
All of these can be overridden by specifying them in the standard settings.py file.
Allow random gunk after a valid page?
Makes the page handling mechanism try to find a cms page with that path if it encounters a page not found situation. This allows for nice customised cms-styled error pages. Do not go overboard, this should be as simple and as error resistant as possible, so refrain from deeply nested error pages or advanced content types.
app_label.model_name as per django.db.models.get_model. defaults to page.Page
Show frontend-editing button?
avoid jQuery conflicts – scripts should use feincms.jQuery instead of $
When uploading files to the media library, replacing an existing entry, try to save the new file under the old file name in order to keep the media file path (and thus the media url) constant. Experimental, this might not work with all storage backends.
Thumbnail function for suitable mediafiles. Only receives the media file and should return a thumbnail URL (or nothing).
Local path to newly uploaded media files
Prevent changing template within admin for pages which have been allocated a Template with singleton=True – template field will become read-only for singleton pages.
Prevent admin page deletion for pages which have been allocated a Template with singleton=True
Prefix for thumbnails. Set this to something non-empty to separate thumbs from uploads. The value should end with a slash, but this is not enforced.
If True, users will be allowed to ignore HTML warnings (errors are always blocked):
Name of the tidy function - anything which takes (html) and returns (html, errors, warnings) can be used:
If True, HTML will be run through a tidy function before saving:
If True, displays form validation errors so the user can see how their HTML has been changed:
How to switch languages. * 'STANDARD': The page a user navigates to sets the site’s language
and overwrites whatever was set before.
Include ancestors in filtered tree editor lists
Enable checking of object level permissions. Note that if this option is enabled, you must plug in an authentication backend that actually does implement object level permissions or no page will be editable.
When enabled, the page module is automatically registered with Django’s default admin site (this is activated by default).