On 15/08/2015 10:45 AM, Ryne Everett wrote:
Thanks Ryne, unfortunately no. Nothing in the supervisor, gunicorn
or nginx logs. Are there any others?
Oh, I didn't realize this was a production environment. Do you
experience the same thing using runserver? Also, where are you getting
the "uninformative "there has been an error" or similar"?
In the middle of the space for content. The base.html menus all appear OK.
BTW, I suspected my image at first and swapped it with the same image
which appears successfully in the top menu. I copied and pasted these
lines from base.html ...
<div class="logotopleft">
<img src="{% static "img/SSDSBrandXXSmallFA.png" %}" height="51"
width="271" />
</div>
... which are inside the base.html container div
I also tried it without the <div> tags.
I appreciate your persistence. Thanks.
Mike
On Fri, Aug 14, 2015 at 8:00 PM, Mike Dewhirst <[email protected]
<mailto:[email protected]>> wrote:
On 14/08/2015 11:59 PM, Ryne Everett wrote:
  Is there a rule which says index.html cannot extend base.html?
No. That's what I do.
  It does seem to work - at least until I try and use an
<img> tag. It
  then barfs with an uninformative "there has been an error"
or similar.
I suspect a more detailed error message will be necessary to
figure out
what's going wrong. I'm assuming this message is in the logs?
Thanks Ryne, unfortunately no. Nothing in the supervisor, gunicorn
or nginx logs. Are there any others?
On Fri, Aug 14, 2015 at 9:14 AM, Mike Dewhirst
<[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>>
wrote:
  Is there a rule which says index.html cannot extend base.html?
  It does seem to work - at least until I try and use an
<img> tag. It
  then barfs with an uninformative "there has been an error"
or similar.
  The base.html blocks all render nicely - but not the content.
  Could it be that I need a plain and self-contained
index.html page
  which is not a Django template?
  Thanks
  Mike
  --
  You received this message because you are subscribed to
the Google
  Groups "Mezzanine Users" group.
  To unsubscribe from this group and stop receiving emails
from it,
  send an email to
[email protected]
<mailto:mezzanine-users%[email protected]>
  <mailto:mezzanine-users%[email protected]
<mailto:mezzanine-users%[email protected]>>.
  For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from
it, send
an email to [email protected]
<mailto:mezzanine-users%[email protected]>
<mailto:[email protected]
<mailto:mezzanine-users%[email protected]>>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected]
<mailto:mezzanine-users%[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Mezzanine
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
