Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trialRhian Thomas
7,489 PointsHTML & Form Helpers. If you are following using Laravel 5.0, note that HTML & Form Helpers are deprecated.
Not really a question, but rather a note. If you are following using Laravel 5.0, HTML & Form Helpers are deprecated. So using HTML::script will not work.
You can read more here: http://laravel.com/docs/5.0/upgrade#upgrade-5.0
1 Answer
Shane Meikle
13,188 PointsIt is extremely easy to get them back though, just install the packages via composer and make sure to add the necessary bits to the configuration for the usage.
Rhian Thomas
7,489 PointsRhian Thomas
7,489 PointsAgreed, Shane :) I was actually surprised that they were deprecated though... I wonder if they will come back in a future release (just including by default Laravel Collective version for example).
For those looking for details on how to install the Laravel Collective package via composer referred to by the Laravel official documentation: http://laravelcollective.com/docs/5.0/html
Shane Meikle
13,188 PointsShane Meikle
13,188 PointsLaravel 5.1 is going to be released on the 9th, but I think it still requires the additional step to get the helpers up and running.
While it isn't a whole lot of time to get it up and running, I found that I use those features on quite a few projects so a workaround I did was use Git locally to create a central hub for the laravel install, then made all the edits to composer.json and the config files, then when I need to start a new project I clone it to a new project directory.
Rhian Thomas
7,489 PointsRhian Thomas
7,489 PointsI did not know that Laravel 5.1 was coming out so soon! Thanks for the heads up and for the local git tip. Looking forward to "improved" documentation announced by the Laravel team. More code examples will be nice for those of us starting out.
Shane Meikle
13,188 PointsShane Meikle
13,188 PointsI suggest checking out Laracasts if you haven't already, it is an amazing resource for Laravel. I love Treehouse, but nothing can come close to the content on Laracasts for Laravel.
Shane Meikle
13,188 PointsShane Meikle
13,188 PointsNot to spam this topic, but another option I have taken up was to use Windows batch commands to automate the creation of new projects.
1: Set up a central hub for the laravel versions to live in. Customize each for the things I use across majority of projects (ie. form helpers, asset configuration and so on). 2: Create the batch file:
3: Run the batch file. I created a WebDev toolbar that lives near my task panel on the bottom right. From there, I run the batch and answer the questions and have a version up and running in no time.
Anyways, hopefully this helps anyone coming across issues with the missing things they have enjoyed and don't want to reconfigure each project.