#4081: Allow blank and null content fields for flatpages
--------------------------------------------+-------------------------------
Reporter: mrmachine | Owner: nobody
Status: new | Component: Contrib
apps
Version: SVN | Resolution:
Keywords: flatpages blank null content | Stage: Design
decision needed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
--------------------------------------------+-------------------------------
Comment (by Tai Lee <[EMAIL PROTECTED]>):
direct_to_template would required urls.py to be changed and the server
restarted each time a new page is added. Flatpages allows staff admin
users to create and delete pages without changing urls.py or restarting
the server. Where's the harm in allowing blank content? How is that even
backwards incompatible? As long as null=False stays, no existing sites
should break by adding blank=True...?
--
Ticket URL: <http://code.djangoproject.com/ticket/4081#comment:4>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---