On Sun, Mar 30, 2008 at 10:47 AM, Karen Tracey <[EMAIL PROTECTED]> wrote:
> Note ticket #5926 has been hanging around for a few months on this issue,
> with at least 3 people (one who provided a patch) hoping the fix would be to
> change the code to match the docs versus changing the docs to
On Sun, Mar 30, 2008 at 9:36 AM, James Bennett <[EMAIL PROTECTED]>
wrote:
>
> On Sun, Mar 30, 2008 at 8:06 AM, Carl <[EMAIL PROTECTED]> wrote:
> > I will open a ticket right away...
>
> Fixed in changeset 7388.
>
Note ticket #5926 has been hanging around for a few months on this issue,
with at
On Sun, Mar 30, 2008 at 8:06 AM, Carl <[EMAIL PROTECTED]> wrote:
> The only problem is, that those automatically created permissions have
> english descriptions and I'm building something for a german-only
> speaking user base. But i think i'll just change the descriptions
> manually in the
On Sun, Mar 30, 2008 at 8:06 AM, Carl <[EMAIL PROTECTED]> wrote:
> I will open a ticket right away...
Fixed in changeset 7388.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--~--~-~--~~~---~--~~
You received this message
Thanks again!
The only problem is, that those automatically created permissions have
english descriptions and I'm building something for a german-only
speaking user base. But i think i'll just change the descriptions
manually in the database. That's just a few lines of SQL at the end...
I will
On Sun, Mar 30, 2008 at 8:41 PM, Carl <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> and fast thanks for the super fast reply!
> Just to make sure that I understood it correctly ---> those standard
> permissions are unevitable if I use django.contrib.auth?
Yes.
> That would really be inconvinient!
Hi,
and fast thanks for the super fast reply!
Just to make sure that I understood it correctly ---> those standard
permissions are unevitable if I use django.contrib.auth?
That would really be inconvinient! And moreover, the documentation
would be misleading as it states:
"Three basic
On Sun, Mar 30, 2008 at 8:18 PM, Carl <[EMAIL PROTECTED]> wrote:
>
> Hi Djangonauts,
>
> just observed that the standard edit/update/delete-permissions get
> created for all my models without me having given them the inner class
> Admin. Anyone an idea why this happens?
Because model permissions
Hi Djangonauts,
just observed that the standard edit/update/delete-permissions get
created for all my models without me having given them the inner class
Admin. Anyone an idea why this happens?
Best regards,
Carl
--~--~-~--~~~---~--~~
You received this message
9 matches
Mail list logo
