<p>Apparently this is a bug in the latest release.  Oops!</p>

<p>The default homepage template on a fresh install is referencing an <code>entry.heading</code> that no longer exists.</p>

<p>Fixed it for the next release, but in the meantime, you can change line 23 of <code>craft/templates/index.html</code> from:</p>

<pre><code>&lt;h1&gt;{{ entry.heading }}&lt;/h1&gt;
</code></pre>

<p>to:</p>

<pre><code>&lt;h1&gt;{{ entry.title }}&lt;/h1&gt;
</code></pre>

CC BY-SA 3.0
2014-12-06T21:41:00.327Z
2014-12-06T21:41:00.327Z
Brad Bell
<p>I don't think the there is anything wrong with your Craft install. It looks like you might have removed a field from a section but it is still being referenced in your template, but because it doesn't exist for that entry anymore Craft is throwing that error.</p>

<p>Look in the template that is being rendered and there will probably be a tag like <code>{{ entry.heading }}</code> try deleting it and refreshing the page, or alternatively add a 'heading' field to the section the entry belongs to. This should solve the issue and make the error go away.</p>

CC BY-SA 3.0
2014-12-07T09:04:34.373Z
it was a new bug! tot do with this entry.heading indeed (see choosen solution..)
skipx
CC BY-SA 3.0
2014-12-07T10:47:45.460Z
Ahh nice glad it got fixed! At least you know why that error occurs if you see it again in the future :)
Alec Ritson
CC BY-SA 3.0
2014-12-06T20:54:54.067Z
2014-12-06T21:30:37.130Z
2014-12-06T21:30:37.130Z
Alec Ritson
<p>I installed Craft CMS and all seemed great! But the pages are not loading.. So bascially /admin loads but /index.php genrates an error. </p>

<p>In dutch: "Interne Serverfout Craft\EntryModel en zijn behaviors hebben geen method of closure met naam "heading"."</p>

<p>Which translated is something like: "Craft\EntryModel and its behaviours have no method or closure with the name heading"</p>

<p>Any idea what's wrong? Can be server-level..
I run it on a mac mini server, but mysql, php and apache (plus php-modules) are installed, and again, admin works nicely..
best,
Bart</p>

CC BY-SA 3.0
2014-12-07T08:13:01.933Z
Since this was identified as a bug by Brad, and fixed in the next version of Craft, we'll close this thread as a "bug report".
Lindsey D
<error-message>
admin pages loading but not site itself, strange error
# admin pages loading but not site itself, strange error

(Asked by: username_0 on 2014-12-06)

I installed Craft CMS and all seemed great! But the pages are not loading.. So bascially /admin loads but /index.php genrates an error.

In dutch: "Interne Serverfout Craft\EntryModel en zijn behaviors hebben geen method of closure met naam "heading"."

Which translated is something like: "Craft\EntryModel and its behaviours have no method or closure with the name heading"

Any idea what's wrong? Can be server-level..
I run it on a mac mini server, but mysql, php and apache (plus php-modules) are installed, and again, admin works nicely..
best,
Bart

**Tags:** error-message
> **Comments:**
> **username_1**: Since this was identified as a bug by Brad, and fixed in the next version of Craft, we'll close this thread as a "bug report".  

---

## 2 answers

### Answer by username_2 on 2014-12-06. Score: 2 | Accepted answer

Apparently this is a bug in the latest release.  Oops!
The default homepage template on a fresh install is referencing an entry.heading that no longer exists.
Fixed it for the next release, but in the meantime, you can change line 23 of craft/templates/index.html from:
{{ entry.heading }}

to:
{{ entry.title }}


---

### Answer by username_3 on 2014-12-06. Score: 1

I don't think the there is anything wrong with your Craft install. It looks like you might have removed a field from a section but it is still being referenced in your template, but because it doesn't exist for that entry anymore Craft is throwing that error.

Look in the template that is being rendered and there will probably be a tag like `{{ entry.heading }}` try deleting it and refreshing the page, or alternatively add a 'heading' field to the section the entry belongs to. This should solve the issue and make the error go away.

> **Comments:**
> **username_0**: it was a new bug! tot do with this entry.heading indeed (see choosen solution..)  
> **username_3**: Ahh nice glad it got fixed! At least you know why that error occurs if you see it again in the future :)  

---

