I have a weird problem with flatpages. Everything works fine if I have
DEBUG=True in the settings.py. However, when I change DEBUG=False
flatpages gives error:
---
Traceback (most recent call last):
File
"/opt/local/lib/python2.4/site-packages/django/core/servers/basehttp.py",
li
Guillermo Fernandez Castellanos wrote:
> There is an option, the APPEND_SLASH in CommonMiddleware, that will
> rewrite URLs that lack a trailing slash to be redirected to the same
> URL with a trailing slash, unless the last component in the path
> contains a period.
>
http://www.djangoproje
Cheers,
I don't know if this has to do with the flatpages framework, but
Django is sensitive to the trailing slash. I think some browsers add
the trailing slash automagically, and this may be the case of yours.
There is an option, the APPEND_SLASH in CommonMiddleware, that will
rewrite
I set up a flatpage for my local homebrew club to target the index
page. To do this I set the URL for the flatpage to be "/".
Today I got a few reports that when users visited my site by typing
"www.cascade-brewers.com" they got nothing. But if the added the
trailing slash "www.cascade-brewers.
Score! That was exactly the problem!
I opened up the DB, and the site_id was 5, though my site_id in
settings was 1.
I guess I went wrong when I was mucking around with the sites section
in the admin. Instead of editing example.com to match my current
domain, I kept adding new ones, and the site
Have you checked to make sure that the 'SITE_ID" variable in settings.py
matches the ID column in the django_flatpage
table for the specified URL ?
- CL
[EMAIL PROTECTED] wrote:
>I read the documentation on the flatpages, included the middleware,
>added the app, sync'd t
Are you 100% sure that the URL you created in the db has both the
leading and trailing slashes? That screwed me up the first time I
tried using flatpages.
And FYI, this is how I have my MIDDLEWARE_CLASSES defined:
MIDDLEWARE_CLASSES = (
'django.middleware.common.CommonMiddl
I made it last, and it didn't seem to help. Here's the settings:
MIDDLEWARE_CLASSES = (
'django.middleware.common.CommonMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.middlewar
On 24 Aug 2006, at 21:49, [EMAIL PROTECTED] wrote:
> I read the documentation on the flatpages, included the middleware,
> added the app, sync'd the database, and made an entry using the admin.
It sound like you've put the flatpages middleware in the wrong place,
it should b
I read the documentation on the flatpages, included the middleware,
added the app, sync'd the database, and made an entry using the admin.
Every time I try to view the newly created flatpage, I get a 404 error.
I thought it might be because I have debug=true, but changing that
didn't
Adrian Holovaty wrote:
> Are you sure you added
> 'django.contrib.flatpages.middleware.FlatpageFallbackMiddleware' to
> your MIDDLEWARE_CLASSES setting? That's the part that actually
> *serves* the flatpages.
Thanks for the reply Adrian. Yes, I did add this. I was u
On 8/2/06, Edmund <[EMAIL PROTECTED]> wrote:
> Newbie question here... I installed Flatpages as per the docs. Then, I
> created a flatpage via the admin interface, and also checked that the
> SITE_IDs shown matched that in my settings.py.
>
> But, I get a 404. On tracing t
Newbie question here... I installed Flatpages as per the docs. Then, I
created a flatpage via the admin interface, and also checked that the
SITE_IDs shown matched that in my settings.py.
But, I get a 404. On tracing through the 404, I see that it is being
raised in ~/django_src/django/shortcuts
Great, glad to help out!!
--~--~-~--~~~---~--~~
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
tomass wrote:
> In the Flatpages list in the admin interface by default I see "FlatPage
> object" instead of, for instance, the title or URL field.
>
It happened to my app too :-) It seems the most recent django calls
__str__ now, whereas it us
On 5/11/06, tomass <[EMAIL PROTECTED]> wrote:
> In the Flatpages list in the admin interface by default I see "FlatPage
> object" instead of, for instance, the title or URL field.
>
> Ditto with Sites.
>
> Is this supposed to be this way? I realize I could create
In the Flatpages list in the admin interface by default I see "FlatPage
object" instead of, for instance, the title or URL field.
Ditto with Sites.
Is this supposed to be this way? I realize I could create a wrapper
around the object and use a def __repr__(self) to take care of this
I encountered problem that similar to ticket#1296 with the latest dev
revision?
my flatpages is only working when DEBUG=True. Currently, I'm using
revision 2864.
I try to look at the flatpages middleware, but cant find anything
suspicious :)
Anyone have the same problem or resolution?
T
Ok found the answer myself. I added at the bottom of content block:
{% if flatpage.enable_comments %}
{% load comments %}
{% free_comment_form for flatpages.flatpages flatpage.id %}
etc ...
--~--~-~--~~~---~--~~
You received this message because you are subscri
Hello guys !
Could anyone please tell me why I don't see comments bellow the page
when I click on "enable comments" in admin for a flat page ?
Should it be enabled by adding:
{% load comments %}
{% free_comment_form for . %}
to the flatpages/d
Thanks Adrain for your support
i am wondering is that means that i have to create another folder for
flatpages
in /usr/lib/python2.4/site-packages/Django-0.91-py2.4.egg/django/contrib/
and call it in my application
NB.all my change is just in this
file
/usr/lib/python2.4/site-packages/Django
On 3/22/06, Mary Adel <[EMAIL PROTECTED]> wrote:
> I am working with flatpages and they are amazing for me and i customized
> them for my first needs then i am developing another site now that has
> another needs and i need to customize flatpages but in different way so
> how
On 3/22/06, Mary Adel <[EMAIL PROTECTED]> wrote:
> I am working with flatpages and they are amazing for me and i customized
> them for my first needs then i am developing another site now that has
> another needs and i need to customize flatpages but in different way so
> how
>
> Dear All ,
> I am working with flatpages and they are amazing for me and i customized
> them for my first needs then i am developing another site now that has
> another needs and i need to customize flatpages but in different way so
> how this could be done
may we ask wh
Dear All ,
I am working with flatpages and they are amazing for me and i customized
them for my first needs then i am developing another site now that has
another needs and i need to customize flatpages but in different way so
how this could be done
Thanks,
Mary
On Wednesday 22 February 2006 08:22, Mary Adel wrote:
> how to call in flatpage a content i have saved in the database
> ex i saved the path of the css and java script in the database and i
> need to call it in my flatpage so how i could do this
The best way is probably to create a templatetag th
really this path will be constant to all flatpages and all what i need
is how i could get the path from the database and put it in the template
is their a way for that
On Tue, 2006-02-21 at 20:02 -0500, Tom Tobin wrote:
> On 2/22/06, Mary Adel <[EMAIL PROTECTED]> wrote:
> >
>
-by-flatpage basis, you might be
better off making your own version of Flatpages with fields for the
CSS/JS locations; you could then pass those into the template as
appropriate.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Goog
how to call in flatpage a content i have saved in the database
ex i saved the path of the css and java script in the database and i
need to call it in my flatpage so how i could do this
--~--~-~--~~~---~--~~
You received this message because you are subscribed
On 11/11/05, Maniac <[EMAIL PROTECTED]> wrote:
> Looks like there are no links to these docs from the documentation index
> (http://www.djangoproject.com/documentation/).
>
> I would look for them in the 'Available subframeworks' section.
Thanks, Maniac. I've added those links.
Adrian
--
Adrian
Adrian Holovaty wrote:
* The flatpages app: http://www.djangoproject.com/documentation/flatpages/
* The redirects app: http://www.djangoproject.com/documentation/redirects/
Looks like there are no links to these docs from the documentation index
(http://www.djangoproject.com
All,
As of a code update today, flatpages and redirects, two features that
have been installed with Django by default but had not been
documented, are now optional add-ons. This is a backwards-incompatible
change, so all Django users are advised to follow the instructions in
the "Sepa
On 10/31/05, Alice <[EMAIL PROTECTED]> wrote:
> Is it better to have a flatfile with no 'content' and an associated
> template with the actual content or to put the content in the 'content'
> box?
>
> Is the 'content' box just for small pages that don't deserve their own
> actual file?
It's alway
just a question about style:
Is it better to have a flatfile with no 'content' and an associated
template with the actual content or to put the content in the 'content'
box?
Is the 'content' box just for small pages that don't deserve their own
actual file?
I get hung up on these things - curre
301 - 334 of 334 matches
Mail list logo
