Cannot get preview: TemplateSyntaxError

Got it!

Change the "%" in "{% change_form_object_tools %}", to "{}", so that it looks like this: "{{ change_form_object_tools }}".

Hope this fixes the problem for you, it did for me. :)

honestly, for what these classes cost this sucks

I had the same problem. I solved it by copying and pasting the change_form.html from the django folder installed on my computer. Lib\site-packages\django\contrib\admin\templates\admin\change_form.html.

Hi Bas,

The reason for this is that you're using change_form.html from a modern version of Django, but the video and workspace is using 1.8.1. In the old version of Django, the {% object_tools %} block had some hard-coded HTML, but newer versions refer to a tag. If the rest of your Django version is old, that tag won't exist, hence the error.

There are two ways to address this. The simplest way is to just to use the same version of Django as the video (this is basically your only option if you are using Workspaces):

Since Django uses git for version control, we just need to find the commit for the 1.8.1 release. The Django devs make this really easy for us since they tag every commit that corresponds to a release version.

If you go to the project's repo, you'll see in the middle of the page, in a grey box, a link that says something like "206 releases". Click that and it'll take you to the Releases list.

Scroll to the bottom of the page and click Next until you get to the page with the 1.8.1 release (May 1, 2015).

Right underneath that, you'll see a link to a commit: 3d128dc.

Click it and you'll be at the commit summary page. Then click Browse files on the right in the blue box.

You will now find yourself browsing the Django project exactly as it was for version 1.8.1. Any file you open in here will be the 1.8.1 version, which you can copy-paste into your own project and have it work exactly like the video. For example, change_form.html.

The second option (probably better if you are following along on your own machine) is to use the current version of Django across the board. You might have to fix a few minor version-related issues as you progress through the course, but you're going to end up confronting these issues at some point anyway. And by using current-gen Django, you're more able to use your existing portfolio as a reference for future projects.

Hope that helps,

Alex

Hi Wesley Trayer ,

I noticed that, so that's why I gave recommendations for users both in Workspaces and on their own computers. It was from Workspaces (as of today) that I got the relevant Django version (1.8.1), so the instructions should work exactly as described for Workspace users.

Moreover, if the Workspace version ever changes, the solution above will still work, the only difference will be to browse for the Django tag on GitHub that matches whatever version is in Workspaces (you can quickly check by looking at settings.py) instead of 1.8.1.

Cheers,

Alex