500 Error Failed To Locate View Layout
Support Search GitHub This repository Watch 1,552 Star 27,625 Fork 5,132 expressjs/express Code Issues 90 Pull requests 37 Projects 0 Wiki Pulse Graphs New issue Error: failed to locate view "layout" #720 Closed codesplicer opened this Issue Jun 22, 2011 · 11 comments Projects None yet Labels bug Milestone No milestone Assignees No one assigned 2 participants codesplicer commented Jun 22, 2011 Just updated express and keep getting this error when directory layout is like: views frontend room index.jade layout-room.jade and my view function is: res.render('frontend/room/index', {
layout: 'layout-room'
}); This was working fine until I updated, if that helps. expressjs member tj commented Jun 22, 2011 you shouldn't need to specify "/index", res.render('frontend/room') should work, that might resolve the layout issue expressjs member tj commented Jun 22, 2011 also note that by default if layout.ENGINE is defined in the same dir as the rendered view it should be automatically selected by default so maybe try removing the layout option and renaming it to layout.jade codesplicer commented Jun 22, 2011 I tried that, but still get the following in the console: failed to locate view "layout", tried: /Users/vik/local_repository/myapp/views/layout.jade /Users/vik/local_repository/myapp/views/_layout.jade /Users/vik/local_repository/myapp/views/layout/index.jade It doesn't seem to be following the path down correctly, but its wierd because this code has been working fine until I updated express. expressjs member tj commented Jun 22, 2011 hmm do you know which version you were on before updating? that might help track down the change. codesplicer commented Jun 22, 2011 2.3.10 expressjs member tj commented Jun 22, 2011 very odd, not much changed in 2.3.11 just some express(1) stuff codesplicer commented Jun 22, 2011 hmm. Very odd. Guess I need to restructure my views directory. expressjs member tj commented Jun 22, 2011 weird I just tried with HEAD and it works for me with: views/ users/ layout.jade index.jade for res.render('users') expressjs member tj commented Jun 22, 2011 hmm it does seem broken when you explicitly pass layout, so this is definitely a bug, though I would suggest just using layout.jade i
from GoogleSign inHidden fieldsSearch for groups or messages
been using redmine since 0.9.3, and we're currently running 1.3.0. I've got a test server that I upgraded from https://confluence.atlassian.com/confkb/java-lang-runtimeexception-error-rendering-template-for-decorator-root-in-a-page-217743738.html 1.3.0 to 2.1.0 -> 2.2.0. 2.1.0 was working just fine, but I wanted some of the enhancements from 2.2.0 500 error so I upgraded. Now I cannot list issues. Below is the error Im seeing, anyone have any ideas? Thanks. -Garrett Marone Connecting to database specified by database.yml OpenIdAuthentication.store is nil. Using in-memory store. DEPRECATION WARNING: Calling set_table_name is 500 error failed deprecated. Please use `self.table_name = 'the_name'` instead. (called from 22: <%= label_tag('add_filter_select', l(:label_filter_add)) %> 23: <%= select_tag 'add_filter_select', filters_options_for_select(query), :name => nil %> 24: 25: 26: app/helpers/queries_helper.rb:27:in `sort' app/helpers/queries_helper.rb:27:in `filters_options' app/helpers/queries_helper.rb:22:in `filters_options_for_select' app/views/queries/_filte
upgrade. The page may have been working fine previously. Not all pages are affected. The atlassian-confluence.log file contains a stack trace similar to: 2010-04-08 11:35:24,597 ERROR [http-10.28.1.96-80-12] [atlassian.confluence.servlet.ConfluenceServletDispatcher] sendError Could not execute action -- referer: http://confluenceURL/dashboard.action | url: /display/Spacekey/Home | userName: admin java.lang.RuntimeException: Error rendering template for decorator root at com.atlassian.confluence.setup.velocity.ApplyDecoratorDirective.render(ApplyDecoratorDirective.java:211) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:175) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336) at org.apache.velocity.Template.merge(Template.java:328) ... Caused by: java.lang.RuntimeException: Error rendering template for decorator page at com.atlassian.confluence.setup.velocity.ApplyDecoratorDirective.render(ApplyDecoratorDirective.java:211) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:175) ... Caused by: org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getDisplayableLabel' in class com.atlassian.confluence.plugin.descriptor.web.model.ConfluenceWebLabel threw exception com.atlassian.core.exception.InfrastructureException: Error occurred rendering template content at template/includes/menu-macros.vm[line 132, column 36] at org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:337) ... Caused by: com.atlassian.core.exception.InfrastructureException: Error occurred rendering template content at com.atlassian.confluence.util.velocity.VelocityUtils.getRenderedContent(VelocityUtils.java:123) at com.atlassian.confluence.util.velocity.VelocityUtils.getRenderedContent(VelocityUtils.java:106) at com.atlassian.confluence.plugin.descriptor.web.ConfluenceWebFragmentHelper.renderVelocityFragment(ConfluenceWebFragmentHelper.java:57) at com.atlassian.plugin.web.model.DefaultWebLabel.getDisplayableLabel(DefaultWebLabel.java:71) at com.atlassian.confluence.plugin.descriptor.web.model.ConfluenceW