I have set:
admin.site.root = ''
in settings.py and this helped. I can't right now check publishing
server (I am sick at home), but I know, that we are using mod_wsgi and
I am pretty sure, that we use Django 1.2 (at least I have username
with a dot there, which wasn't possible earlier ;-)).
Is there a better way other than setting admin.site.root myself?
2010/7/24 Gautier <ghay...@gmail.com>:
> do you still have this problem?
>
> If so, can you tell how do you publish your django application (Apache/
> mod_wsgi ...), and check that you actually use Django 1.2.
>
> And if you don't please tell it too, so that the ticket you opened can
> be closed.
>
> Cheers
>
> On Jun 23, 6:00 pm, Filip Gruszczyński <grusz...@gmail.com> wrote:
>> > before: ('^admin/(.*)',admin.site.root),
>>
>> > after: (r'^admin/', include(admin.site.urls)),
>>
>> Well, I had to change it before and about two weeks ago I changed it
>> too (this is how my urls.py looks like):
>>
>> (r'^admin/doc/', include('django.contrib.admindocs.urls')),
>> # (r'^admin/(.*)',admin.site.root),
>> (r'^admin/', include(admin.site.urls)),
>>
>> It solved some other problems (admindidn't work at all), but I still
>> have the problems with links inadminsite.
>>
>>
>>
>>
>>
>> > it work good now!!!
>>
>> > bye
>>
>> > 2010/6/23 Filip Gruszczyński <grusz...@gmail.com>
>>
>> >> After migrating to 1.2 I encountered a problem inadminpanel. My
>> >> change password ang logout links look like this:
>>
>> >>https://example.com/admin/Nonelogout/
>> >>https://example.com/admin/Nonepassword_change/
>>
>> >> I have taken a look into django source and it seems, thatroot_pathis
>> >> None (at least this variable is rendered in those urls). What I might
>> >> have forgotten to set and how can I change it to an empty string?
>>
>> >> --
>> >> Filip Gruszczyński
>>
>> >> --
>> >> You received this message because you are subscribed to the Google Groups
>> >> "Django users" group.
>> >> To post to this group, send email to django-us...@googlegroups.com.
>> >> To unsubscribe from this group, send email to
>> >> django-users+unsubscr...@googlegroups.com.
>> >> For more options, visit this group at
>> >>http://groups.google.com/group/django-users?hl=en.
>>
>> > --
>> > You received this message because you are subscribed to the Google Groups
>> > "Django users" group.
>> > To post to this group, send email to django-us...@googlegroups.com.
>> > To unsubscribe from this group, send email to
>> > django-users+unsubscr...@googlegroups.com.
>> > For more options, visit this group at
>> >http://groups.google.com/group/django-users?hl=en.
>>
>> --
>> Filip Gruszczyński
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>
--
Filip Gruszczyński
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
