function onLoad()
{
SetCookie(“CheckAcceptCookies”, “confirmed”, 999);
var sNode = GetCookie(“CheckAcceptCookies”);
if(sNode != “confirmed”)
location.href = ‘AcceptCookies.aspx’;
}

This assumes you have your own set/get cookie functions.

————————————————————————————————————-

AcceptCookies.aspx source:

Please click to continue

function onClickConfirm()
{
javascript:history.go(-1);
return false;
}

————————————————————————————————————-

AcceptCookies.aspx.vb is empty.

I struggled with the same issue. I created a sample P3P that worked for me.

http://www.spamcollect.com/archives/33

Hope it helps someone.

The web interface for this platform employs the use of third-party cookies. I did find a way to enable P3P functionality in Firefox, which I have posted here:

http://arfore.com/2010/10/25/enable-p3p-support-in-firefox/

Unfortunately no such solution exists for Safari.

Andy

So, my take for anyone to shoot down is this:–

@register.inclusion_tag(“html-to-include.html”, takes_context=True)
def my_include_tag(context, myparam):
return template.RequestContext(context['request'], {
“inclusion_param”:myparam,
})

I now have my MEDIAL_URL back in the included template

However, I think this is a good, and common, example as people’s email address changes over time, and that doesn’t mean the Account should have to change. A similar example is how you can adjust your Twitter screen_name (which is your login/username), but the rest of the Account is unchanged.

Something that isn’t mentioned in this post is that if you do allow someone to change this value (e.g., change their email on the Account), you have to explicitly remove the old email from Unique – that is, if you want it to be able to to be used again in the future.

I think I would use this solution for mutable data, which is not part of the primary (since primary keys should not be mutable anyhow).

{% yourtag request.user %}

… or, and maybe this is new since the original post, you can access the context in the “render” routine of the template.Node:

class yourNode(template.Node):
def render(self, context):
user = context.request.user

http://docs.djangoproject.com/en/1.2/howto/custom-template-tags/#passing-template-variables-to-the-tag

A caveat of this is that if your a.put() fails, you’ve lost your unique value unless you take some other compensating action (e.g., removing the unique value from the Unique model).

home._room

I suppose?

Thanks for the tip! It *is* absolutely worth to mention that
django.core.context_processors.request
is in your TEMPLATE_CONTEXT_PROCESSORS in settings.py!

+1 on that.

Retrieve given id/key name: 12 ms * results
Query: 17.5 ms + 13.5 ms * results
Inserts/Updates/Deletes: ~3000 ms + ~350 ms * entities

In other words, do requests in parallel, sure, but be careful to issue inserts/updates/deletes in batches.