This morning I was attempting to build a template tag: {% link_to
[page] [link text] %} so our content writers can use that syntax to put
links in their text to refer to other pages in our website. The idea
being that the template tag can call get_absolute_url (or whatever the
new undocumented version of this is [1]) and the link will be created
and can change later in one place rather than scouring the database for
absolute links.
But, while trying to get this to work I realized that this doesn't work
for content coming from the database. I can imagine what would need to
happen is a double parse/render of the template -- once to parse and
get the dynamic content, and a second time to parse/render the text
from the dynamic content. Obviously Django doesn't want to go down
this road.
So is there a solution to allow template tags to be in the content of a
database and parsed/rendered later? Is there a solution to this that
isn't template tags? Filters (which I haven't explored much yet)?
Thanks,
Rob
[1] http://code.djangoproject.com/ticket/672
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
