Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

YAML Frontmatter not process when html extension is implied #422

Closed
heygrady opened this Issue May 7, 2012 · 3 comments

Comments

Projects
None yet
2 participants

heygrady commented May 7, 2012

From the 3.0 Beta 2 notes:

"Templating engines can now set a default output extension. For example, .erb now implies .html so my-template.erb will ouput to my-template.html."

This works really well but when I do something like index.erb the YAML Frontmatter is output to the browser as if it hadn't been processed at all. I got the following result with the latest code from the repo on a fresh project where all I had done is rename index.html.erb to index.erb.

<!doctype html>
<html>
  <head>
    <meta charset="utf-8">

    <!-- Always force latest IE rendering engine or request Chrome Frame -->
    <meta content="IE=edge,chrome=1" http-equiv="X-UA-Compatible">

    <!-- Use title if it's in the page YAML frontmatter -->
    <title>The Middleman</title>

    <link href="/stylesheets/normalize.css" media="screen" rel="stylesheet" type="text/css" />
<link href="/stylesheets/all.css" media="screen" rel="stylesheet" type="text/css" />
    <script src="/javascripts/all.js" type="text/javascript"></script>
  </head>

  <body class="index">
    ---
title: Welcome to Middleman

---

<div class="welcome">
  <h1>Middleman is Watching</h1>
  <p class="doc">
    <a href="http://middlemanapp.com/">Read Online Documentation</a>
  </p><!-- .doc -->
</div><!-- .welcome -->
  </body>
</html>
Owner

tdreyno commented May 7, 2012

Which version? Beta 2?

heygrady commented May 8, 2012

The latest from master, pre-beta 3.

Owner

tdreyno commented May 8, 2012

This should be fixed as soon as we merge in:

#416

@tdreyno tdreyno closed this in 7929ed6 May 9, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment