undefined method in styleguide view

[stoplion]

Getting an..
undefined method `[]' for nil:NilClass
in..
<h3><%= section.section %> <em><%= section.filename %></em></h3>

[dewski]

Could you paste your config/routes.rb file? Or at least confirm it has mount Kss::Engine => '/styleguide'.

[stoplion]

I can confirm it's in routes file..
mount Kss::Engine => '/kss' if Rails.env.development?

Should this be in routes as well?
mount Kss::Engine => '/styleguide'

[dewski]

You changed the original issue after I commented on it. You mentioned you were trying to get /styleguide? What happens when you go to /kss, and have you restarted the server?

[stoplion]

I can navigate to http://localhost:4000/kss/ There it displays some links, Home and Styleguide. Styleguide is where i get the above error on line two <h3><%= section.section %> <em><%= section.filename %></em></h3>

[dewski]

I'll need the full backtrace to give a deeper look, undefined method[]' for nil:NilClass` and whatever else comes after that.

[stoplion]

undefined method `[]' for nil:NilClass

Extracted source (around line #2):

1: <div class="styleguide-example">
2:   <h3><%= section.section %> <em><%= section.filename %></em></h3>
3:   <div class="styleguide-description">
4:     <p><%= section.description %></p>
5:     <% if section.modifiers.any? %>

Trace of template inclusion: app/views/kss/home/styleguide.html.erb

app/views/kss/home/styleguide.html.erb:1:in `_app_views_kss_home_styleguide_html_erb___1281663321373551429_2526041660'

[JAndritsch]

Sounds like you're might be trying to call "styleguide_block" with a section that doesn't exist in your CSS. For example, if you want to call "styleguide_block '1.0' ", you have to make sure you have "Styleguide 1.0" somewhere in one of your CSS files. That was at least my issue when I first started using this.

[jankeesvw]

I've had this questions several times in my team, I have fixed this by adding an error when the section is nil.

[jankeesvw]

More descriptive error with my this patch: #18

[jankeesvw]

This issue can be closed, it's fixed!