Malcolm,
i'm seeing the same issue of my page loading twice. working on top of
something my previous colleague built. i see "background" element when i
do curl.
I dont see this in any of my HTML files. I'm sure that i'm looking at the
wrong place.
This is my curl response:
Page not f
Malcom,
Thank you for this writeup you did on debugging HTML code. I was also
showing Django Views loading twice, and it was due to an empty "href".
Only took a few minutes to fix after reading your writeup. Thanks
On Friday, November 14, 2008 5:52:15 PM UTC-8, Malcolm Tredinnick wrote:
>
>
I have encountered the same problem, and after reading the content
above, I solved the problem.
It caused by the following line in my html template:
I replaced with:
Thanks for all.
--~--~-~--~~~---~--~~
You received this message because you are subscrib
> you've used the value "#fff", that will be interpreted by the browser as
> a reference to the current page (#fff being an anchor, and not passed to
> the server). Ergo, a second request is made.
Wow, thanks. Just reading through your step by step taught me some things
I didn't know :)
> The
Malcolm Tredinnick wrote:
[...]
> (5) Checked the HTML that was returned by curl (that was why I used "-i"
> and not just "-I"), since it's now clear that the returned HTML contains
> the problem and noticed the error on the second attempt.
>
> You're using the deprecated "background" attribute o
On Fri, 2008-11-14 at 13:58 -0500, Jeff Gentry wrote:
[...]
> I'm attaching a tarball, which immitates my setup in a minimal
> fashion. At least when running on my system, the following browser
> request triggers this behavior:
>
> http://servername/test/
>
> > rendering at all. You could try
I didn't have time to check your tarball but I have a guess...
Check the HTML source on the browser and look for any empty "src" for
images or "href" for stylesheets.
If you find any, this may be the culprit of the second request, as the
browser tries to load the same view when looking for the i
> Quoting from the book of "if you hear hoofbeats, think horses, not
> zebras": This obviously isn't normal Django behaviour and since calling
> views is easily the most common operation in Django, it's safe to assume
> that any breakage here in Django would have been noticed by other
> people. Whi
On Thu, 2008-11-13 at 17:03 -0500, Jeff Gentry wrote:
>
> Another piece of info, in case it's useful here - the page does *not*
> render on the first view call, it's only after the second call that the
> page will render. I don't think it's even pulling up the template until
> the second go-aro
Another piece of info, in case it's useful here - the page does *not*
render on the first view call, it's only after the second call that the
page will render. I don't think it's even pulling up the template until
the second go-around, as a test I put some intentionally bad template code
in a te
> How have you noticed that view was triggered twice?
I noticed that the URLs were displaying twice in the devel server console
(and in HTTP logs for when running off of apache). For the former case, I
put a print statement in the view function - when loading those pages, the
print is triggered
How have you noticed that view was triggered twice?
On Fri, Nov 14, 2008 at 00:17, Jeff Gentry <[EMAIL PROTECTED]>wrote:
>
>
> Actually I lied a little bit - a completely blank file doesn't trigger
> this (I can also seem to put in a and tag), but adding
> anything else will cause the view to
Actually I lied a little bit - a completely blank file doesn't trigger
this (I can also seem to put in a and tag), but adding
anything else will cause the view to be loaded 2x.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the G
In my apps, I'm finding that my views are triggering twice. I have a
series of related apps, working off of the same settings.py file (there's
a global urls.py, which triggers off of the first string and sends to a
subdirectory w/ it's own urls.py/__init__.py/models.py/views.py/etc. With
one exc
14 matches
Mail list logo
