[django-blocks] #56: What am i doing wrong?

[Pablo Abou Adal]

I installed the last version (no more db ninjas needed, thank you) and
almost everything runs smooth.

My problem is: when i add something throug 127.0.0.1/admin on
development server, nothing changes in the homepage (i did try
restarting the server) except for the log, located at the left column.
No new static pages, no new feeds, no new news... but i insisto, those
do appear as "latest changes" in the left column...

I think this is not an issue, but something i'm just missing, if
not... i could fill in a ticket, at your discretion.


Thanks in advance


Pablo

--
You received this message because you are subscribed to the Google Groups "django-blocks" group.
To post to this group, send email to django...@googlegroups.com.
To unsubscribe from this group, send email to django-block...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-blocks?hl=en.

[kimus]

did you check the Publishing Options of the content? You need to
publish the content.

[Solubet]

If i save the (say static page) as already Published, still nothing appears on homepage (except for the log in left column).

If i try to publish it from the main list (after the creation of the page) I get this error:

403 Forbidden

CSRF verification failed. Request aborted.

Help

Reason given for failure:

    CSRF token missing or incorrect.
    

In general, this can occur when there is a genuine Cross Site Request Forgery, or when Django's CSRF mechanism has not been used correctly. For POST forms, you need to ensure:

• The view function uses RequestContext for the template, instead of Context.
• In the template, there is a {% csrf_token %} template tag inside each POST form that targets an internal URL.
• If you are not using CsrfViewMiddleware, then you must use csrf_protect on any views that use the csrf_token template tag, as well as those that accept the POST data.

You're seeing the help section of this page because you have DEBUG = True in your Django settings file. Change that to False, and only the initial error message will be displayed.

You can customize this page using the CSRF_FAILURE_VIEW setting.

[kimus]

the 403 error was because you tryied to publish the content in the
list actions intead of the detail form (collapse the Publish Options).
The error caused by the CRSF and I fixed that (please update).

If the static page is published then you should be able to go to it
easily (see the link on top of the detail form 'view on site'). A
static page depends on the URL that was assigned to it. If it's other
type of content (agenda, news article, etc) to see it on the HOME you
need to PROMOTE it :-) (for that you need to go again to Publish
Options and you will see a promote option).

For feeds you need to run ./manage.py aggregate in a cron job (or
manually for testing)

On May 23, 4:35 pm, Solubet <solu...@gmail.com> wrote:
> If i save the (say static page) as already Published, still nothing appears
> on homepage (except for the log in left column).
>
> If i try to publish it from the main list (after the creation of the page) I
> get this error:
>
> 403 Forbidden
>
> CSRF verification failed. Request aborted.
> Help
>
> Reason given for failure:
>
>     CSRF token missing or incorrect.
>
> In general, this can occur when there is a genuine Cross Site Request
> Forgery, or when Django's CSRF

> mechanism<http://docs.djangoproject.com/en/dev/ref/contrib/csrf/#ref-contrib-csrf>has

> not been used correctly. For POST forms, you need to ensure:
>

>    - The view function uses
> RequestContext<http://docs.djangoproject.com/en/dev/ref/templates/api/#subclassing-c...>for

> the template, instead of
>    Context.

>    - In the template, there is a {% csrf_token %} template tag inside each

>    POST form that targets an internal URL.

>    - If you are not using CsrfViewMiddleware, then you must use
> csrf_protecton any views that use the

>    csrf_token template tag, as well as those that accept the POST data.
>
> You're seeing the help section of this page because you have DEBUG = True in
> your Django settings file. Change that to False, and only the initial error
> message will be displayed.
>
> You can customize this page using the CSRF_FAILURE_VIEW setting.
>

> On 23 May 2010 12:07, kimus <kimus.linu...@gmail.com> wrote:
>
>
>
> > did you check the Publishing Options of the content? You need to
> > publish the content.
>
> > On May 23, 3:41 pm, Pablo Abou Adal <solu...@gmail.com> wrote:
> > > I installed the last version (no more db ninjas needed, thank you) and
> > > almost everything runs smooth.
>
> > > My problem is: when i add something throug 127.0.0.1/admin on
> > > development server, nothing changes in the homepage (i did try
> > > restarting the server) except for the log, located at the left column.
> > > No new static pages, no new feeds, no new news... but i insisto, those
> > > do appear as "latest changes" in the left column...
>
> > > I think this is not an issue, but something i'm just missing, if
> > > not... i could fill in a ticket, at your discretion.
>
> > > Thanks in advance
>
> > > Pablo
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > "django-blocks" group.
> > > To post to this group, send email to django...@googlegroups.com.
> > > To unsubscribe from this group, send email to

> > django-block...@googlegroups.com<django-blocks%2Bunsu...@googlegroups.com>
> > .

> > > For more options, visit this group athttp://
> > groups.google.com/group/django-blocks?hl=en.
>

> > --
> > You received this message because you are subscribed to the Google Groups
> > "django-blocks" group.
> > To post to this group, send email to django...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > django-block...@googlegroups.com<django-blocks%2Bunsu...@googlegroups.com>
> > .