Hmmm. That prevents an immediate crash, but may cause other problems.
Here is a better fix: change lines 45,46 to:
if settings.APPEND_SLASH:
if (len(old_url[1]) > 0):
if (old_url[1][-1] != '/' and ('.' not in
old_url[1].split('/')[-1]):
new_url[1] = new_url
Thanks for the assurances.
BTW, here is the suggested fix for the crash that I experienced:
Line 45 of django/middleware/common.py, change:
if settings.APPEND_SLASH and ...
to:
if settings.APPEND_SLASH and (len(old_url[1]) > 0) and ...
Without that guard statement the very next c
Resolved. See the ticket mentioned above.
I tried on another box and had the same problems, so I filed a ticket:
http://code.djangoproject.com/ticket/692
Thanks guys! I don't know what caused the problem before, because I
tried Sean's suggestion of importing all my model modules, and that
seemed to fix it. But then I read the rest of the replies which
inspired me to try to reproduce the original problem by just loading
one module, and it seems that
On 10/24/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> When I update the post using the admin interface, the history tells me that
> the
> 'pub_date' has been changed, even though I did not change it, and it still
> looks
> the same in the admin interface. Is this a rounding error connecte
On 10/24/05, Howard, Rock <[EMAIL PROTECTED]> wrote:
> 1) The url '' leads to a 404 error. Is that expected? It is unclear from
> the docs what to expect for this case.
It's to be expected if your URLconf doesn't have anything that handles
that URL. Check the urls.py file (the URLconf), which map
On 10/24/05, ashutux <[EMAIL PROTECTED]> wrote:
> I am not able to use admin as a normal app in my project.
> If "admin" is now separated from middleware to "app" level, I should
> have been able to move that app into any of my projects.
> But there is some problem concerning the display of templa
On 10/24/05, stava <[EMAIL PROTECTED]> wrote:
> Does anyone now how the auth_messages table is used?
>
> Presumably for sending messages to the user(s).
> But how?
Authentication docs (which will include documentation on the messages)
are coming soon. The work-in-progress version, which doesn't y
That was it. Thanks. However, there is a new wrinkle. When I update the post
using the admin interface, the history tells me that the 'pub_date' has been
changed, even though I did not change it, and it still looks the same in the
admin interface. Is this a rounding error connected to the de
I have installed django on dreamhost using fcgi. The posted instructions
needed updating due to the improved handlings of settings.py, but I
think I nailed the changes as the admin app comes up fine. My questions:
1) The url '' leads to a 404 error. Is that expected? It is unclear from
the docs
CheckboxSelectMultipleField doesn't work for me. Did anyone got it to
work? I saw some bug report on it, but I wasn't sure if it was already
fixed and I'm missing something.
Thanks,
Armin
Yes! It's absolutely correct and I'm able to reproduce it as you
guessed. If I click on a page while it's sent from server I got exactly
that error message.
Thank you for the answer.
Emanuele
If I define a model with foreign keys, use MySQL/MyISAM as a backend,
and delete a referenced object, does django implement a "cascade on
delete" to clean up child objects, or do I need to manually clean up
the child objects?
Thanks,
Casey
Hi,
I am not able to use admin as a normal app in my project.
If "admin" is now separated from middleware to "app" level, I should
have been able to move that app into any of my projects.
But there is some problem concerning the display of templatetags or
stylesheets that is preventing me to chan
Hi,
I am not able to use admin as a normal app in my project.
If "admin" is now separated from middleware to "app" level, I should
have been able to move that app into any of my projects.
But there is some problem concerning the display of templatetags or
stylesheets that is preventing me to chan
Does anyone now how the auth_messages table is used?
Presumably for sending messages to the user(s).
But how?
R
/LarS
2005/10/24, Carlo C8E Miron <[EMAIL PROTECTED]>:
> A quick investigation
>
> 5)15:05:20 [EMAIL PROTECTED]:~/src/django/svn/django/trunk/django
> 0$ grep -R "class[^(]*:" $(find . -name "*.py")|grep -v \.svn|wc -l
> 100
>
> seems to reveal that there are only 100 old style classes on [1006].
A lit
2005/10/17, Adrian Holovaty <[EMAIL PROTECTED]>:
>
> On 10/17/05, Shaleh <[EMAIL PROTECTED]> wrote:
> > Why is that? Moving forward the Python people expect all classes to be
> > defined as "new-style". Support for old-style is there simply to allow
> > for backwards compatibility.
>
> Because we
On 10/24/05, Emanuele <[EMAIL PROTECTED]> wrote:
>
> Hi,
> sometimes in my logs ("django-admin.py runserver ..." logs, to be
> precise) I got the following error message without any apparent reason.
> It doesn't give any real problem to users but I'm not able to
> understand what causes it.
I'm j
Hi,
sometimes in my logs ("django-admin.py runserver ..." logs, to be
precise) I got the following error message without any apparent reason.
It doesn't give any real problem to users but I'm not able to
understand what causes it.
--
...
[24/Oct/
[EMAIL PROTECTED] wrote:
> I have a weblog app (definition of the Post object below). Everything looks
> OK, but when I go to add or edit a post, the admin app will not let me. I
> make my changes (or fill in the fields for a new post). The server reports
> that it is POSTing the HTML:
>
> [
I have a weblog app (definition of the Post object below). Everything looks
OK, but when I go to add or edit a post, the admin app will not let me. I make
my changes (or fill in the fields for a new post). The server reports that it
is POSTing the HTML:
[24/Oct/2005 06:23:01] "POST /admin/we
23 matches
Mail list logo
