Solved! Blank template

so it was a very very stupid reason that was causing my blank template renders.

I had a series of comments before my html that was closed with

<!– blah blah blah –//>

which strangely worked offline locally, but obviously wasn’t loading online through django. Removing the // solved the entire issue.


Extending a base.html

Further digging into the templates of my website, I’ve tried setting up a base.html and using it to extend throughout the rest of my website. Seem to have a problem getting Django to find it though, because right now it says

base.html template does not exist

although it’s parked right next to all my other htmls in my templates/wagweb folder. hmm… reminds me of when static files were not loaded. Something is differently pointing wrongly!

Errors in Wagtail templates

AttributeError at /admin/pages/2/

type object 'BlogIndexPage' has no attribute 'related_links'
Exception Type: AttributeError
Exception Value:
type object 'BlogIndexPage' has no attribute 'related_links'

Hmm… something must be off with my templates. I get this error when I try to access my main page from explorer.

When I click ‘View Live’ on my main page from the dashboard I then get:

TemplateDoesNotExist at /test/



Request Method: GET
Request URL: http://username.co/test/

TEST is a virtual env directory I found in my cpanel after hosting helped with the installation of lxml in python2.7. It’s strange though, that the request URL is pointing to the TEST virtualenv which is in python2.6

Furthermore, when I try to Save Draft or Publish a Blog_Index_Page I get a wagtail error without traceback:

Picture 9


Ain’t no flock of birds.

So if we’ve been following spapas’ tutorial on how to set-up Wagtail, we will also know how to do a syncdb and migrate

Now that my Wagtail dashboard is finally up, I can move on to the next step in the tutorial. Adding a blog page.

Bump! Migration draws up Not Synced (use migrations) on my wagtails and taggit. But running the usual manage.py migrate returns

— nothing to migrate


1. Use schemamigrate

2. Wait patiently for changes to catch up?


This means I’d use South to handle the migration. Like in this answer by running

python manage.py schemamigration --initial wagweb

This returns:

The error was: table "wagweb_blogpage" already exists
 ! Error found during real run of migration! Aborting.
! Since you have a database that does not support running
 ! schema-altering statements in transactions, we have had 
 ! to leave it in an interim state between migrations.


This means I shouldn’t be using South for migration in this format since Wagtail is already handling that.

Despite this error, I have now refreshed my Wagtail dashboard again and notice that my blogpage template is indeed in!

Maybe I should use solution #2.