views:

15

answers:

1

I have a portfolio application that lists projects and their detail pages. Every project generally has the same information (gallery, about etc. ), but sometimes the user might want to add extra information for a particularly large project, maybe an extra page about the funding of that page for example.

Would it be possible to create an overwritten flatpages model within my portfolio app that forces any flatpages created within that application to always begin with /portfolio/project-name/flat-page. I could then simply pass the links to those flatpages associated with the project to the template so any flatpage the user generates will automatically be linked to from the project page.

EDIT

I have it somewhat working now

So I overwrite the FlatPage model in my portfolio app as described:

from django.contrib.flatpages.models import FlatPage
from project import Project
from django.db import models
from django.contrib.sites.models import Site

class ProjectFlatPage(FlatPage):
    prefix = models.CharField(max_length=100)
    project = models.ForeignKey(Project)

which allows me to associate this flatpage with a particular project,

Then I overwrite the save method to write all the extra information when a user saves (needs to be tidied up):

def save(self, force_insert=False, force_update=False):
    self.url = u"%s%s/" % (self.project.get_absolute_url(),self.prefix)
    self.enable_comments = False
    self.registration_required = False
    self.template_name = 'project/project_flatpage.html'
super(FlatPage, self).save(force_insert, force_update)

and I scaleback the admin to just allow the important stuff:

class ProjectFlatPageForm(forms.ModelForm):
    prefix = forms.RegexField(label=_("Prefix"), max_length=100, regex=r'^[a-z0-9-]+$'),

    class Meta:
        model = ProjectFlatPage

class ProjectnFlatPageAdmin(admin.ModelAdmin):
    form = ProjectFlatPageForm

so now the user can add a flat page inside my app and associate it with a particular project.

In the admin, they just enter a slug for the page and it automatically gets appended through the save() method like: /projects/project-name/flat-page-name/

The remaining problem is on the template end. I can access the normal flatpage information through the given template tags {{ flatpage.title }} and {{ flatpage.content }} put I have no access to the extra fields of the inherited model (i.e. the project field)

Is there anyway around this?

EDIT2

Having thought about it, the easiest way is to write a template tag to find the projectFlatPage associated with the flatpage and get access to it from there. A bit like overwritting the default flatpages template tags

+1  A: 

of course. just write your own flatpage-model, for example

from django.contrib.flatpages.models import FlatPage

class MyFlatPage(FlatPage):
    prefix = models.CharField(max_length=100, editable=False
    url = models.CharField(_('URL'), max_length=100, db_index=True, editable=False)

then add a proper MyFlatPageAdmin to your admin.py file (if you want to, you can import the flatpageadmin from django.contrib.flatpages.admin and inherit from it). after all, you're using the flatpage-model, but overwrite the urls-field. now add a signal, which concats the prefix and a automatically generated url suffix to the url (like the object id). you can now add the custom flatpage like

flatpage = MyFlatPage(prefix='/portfolio/my-super-project/')

everything clear now?

edit 1

as you can read in the documentation, every flatpage should be a projectflatpage and vice versa.

jmoritz