#1486 new
Peter Hilton

Tutorial: guide7 corrections

Reported by Peter Hilton | April 10th, 2012 @ 08:58 PM

Disqus comment by Milan Stojanović:

Excellent tutorial so far. I have only a few suggestions regarding the very last part of this page (Customizing the 'Post' form). First, the last picture in the tutorial should be at the very end of the page, since we don't get to see the tags in action (like in the picture) until we finish the CSS stuff. Second, why are comments absent from the 'Post' form? And why do we get an empty row (div) in the form for them? You don't see that empty row in the pictures above though, but with play 1.2.4 it's there. HTML for that div is:

<span class="crudHelp"></span>
Maybe some clarification about the comments and the div should find a place in the tutorial. Third, if you follow the tutorial, there is no layout.html template in your views folder, so you have to override it first with: play crud:ov --template CRUD/layout Fourth, since at this point layout.html is top-level template (not extending any other), there is no #{set 'moreStyles'} block. Thus we only have to add the line: below the crud.css link. I hope this will help make an excellent tutorial even better :)

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.