is quite hard since there are no
errormessages at any point :(
I would be glad, if anyone could point out to any possible issue here
--
Andreas Neumeier
lovebox.ath.cx
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
&
[EMAIL PROTECTED] schrieb:
> Isn't this just a mysql libs in php vs libs in mysqldb issue?
> Died silently with a blank page until i switched to postgresql.
> Or recompile php correctly yourself.
I'm not quite sure about the meaning here: why should I compile php
_at_all_? :-)
--
Andreas
lovebo
Adrian Holovaty schrieb:
> Does the problem happen on both the Django development server and mod_python?
Actually, this didn't come to my mind before, but I tried it just now
and the development server is working
What could be the issue there?
--
Andreas
lovebox.ath.cx
--~--~-~--~
Well, thats exactly my problem :)
There is no access.log entry, no error.log entry and a blank page
outputted... Debug is set to ON
It looks like RequestContext just dies silently, but I couldn't tell
you for sure.
I also figured out, there is another installation (rev. 2893 on Ubuntu
Dapper),
I just created a new djangorpoject, with a moraless empty view, which
looks like that:
--- cut ---
from django.template import Context, RequestContext
from django.core import template_loader
from django.http import HttpResponse
def index(request):
t = template_loader.get_template('portal/index
I'm not quite sure, it may be me: Is the permission system working at
all in the magig-removal branch?
I added something like that to my model just yesterday:
---
class Meta:
permissions = (
("can_create", "Can create"),
("can_modify", "Can modify"),
("can_view", "Can view
