@xsmall well its too bad you don't like my Skype SDK integration idea. However, I do like the idea of an official site with the best and most trusted packages for Laravel. A site where volunteers can make sure the code is secure. Part of the reason I am learning Laravel is because Wordpress has tens of thousands of cool addons but I read that 98 percent of them are not secure, they are also not updated or patched in a timely manner.

Since I’ve said I wouldn’t like an ACL implementation as part of Laravel’s core, I best suggest something I would like :P

One thing I miss coming from CakePHP is the ability to have different response formats based on a URL extension, similar to Rails’ respond_to declaration.

When I’m building my app, I want to be able to easily render data as JSON without having to create additional routes or controllers, if litter my controller actions with Request::wantsJson() conditionals. Like CakePHP, it would be great if I could stick .json on the end of a URL and have Laravel render the JSON representation of that endpoint.

@martinbean you mean non eloquent data? ( ->toJson() )

@Kryptonit3 I know I can cast Eloquent models to JSON, but I’d like to be able to get a JSON representation of an endpoint by tacking .json on the end of a URL and Laravel automatically convert the view data to JSON rather than render it in a view template, again like CakePHP or Ruby on Rails.

@martinbean I know I am a total noob but couldn't that be done by parsing the last element in the URI and checking for '.json'?

1. An ACL would make a big difference. Even if it didn't match everyone's needs, the fact that there would be a standard way of doing things that could be extended would be incredibly beneficial.

2. ESI inclusion Yes there is a package, and it's pretty decent. I know my guys feel a bit weird about having something truly fundamental outside of the framework (especially as it's aimed at 4.x!)

3. Turn of CSRF as a middlewear command on route I understand why it's on as default. I understand why it's on across all routes. But when building a few API type routes, having to start hacking parts of the framework seems wrong.

Route::post([
    'useCSRF' => false,
], function () {

// stuff :]
});

How do you turn the CSRF protection? isn't it just by commenting the service provider in the global array?

@Ruffles

Yes but that turns it off on all routes. If you only want it turned off on some, there's quite a few hacks to go through, and you need to edit your code every time you add a new route (and it seems incredibly challenging to do it on a route group). I am all for these decisions being made and set as standard in the framework, I just think it's weird to have a pre-defined middlewear thats on as standard that you can't turn off on route as you would for all other middlewear examples.

it would be cool to make something like this

artisan make:website domainname --options='bootstrap,dark|light'
artisan seed:database scrapefrom 'google,yahoo,bing' --keywords="some search query"

I guess all spammers of this wold would start using it and laravel would power 99% of the internet

@kevinjohn This is what I do

csrf middleware

if ($request->is('api/*') {
    return $next($request);
}

// else check csrf

This is not a Laravel feature request but a lesson request. Microsoft used to publish beautiful MSDN library diagrams that you could request (as a student). I'd like to be able to download a pdf file of the entire Laravel framework diagrammed poster size.

I will create one if it does not yet exist when I fully 'get' this stuff.

also pagination at the top of forum page. I love this forum tech:)

@Ruffles

Few pages back, but very well said.

Few knocks on laravel that I have read is because of the other packages that laravel depends on. I 110% agree, why re invent the wheel. If someone open sourced good code/package why not utilize it. Why recode faker or carbon. No need. Utilize what the community has to offer. It isn't lazyness at all, it's efficiency that every one wants.

Really anyone codes a blog set up new each and everytime? No, you build it once, add or remove features depending on the use case and move on.

And about the acl discussion, just as laravel has packages added into the core maybe add an existing acl too.

As stated it helps with continuity across apps from different developers.

What I'd really love to see a product released along with 5.1 more than what features that others have mentioned so far. Something like LaravelSD.com, except well-designed with a little more custom functionality, would be neat.

I would agree with @maxi032, more blade features would be great. As powerful as it is, there are still times (10%-20% tops) that I have to do an old fashion tag.

and @continue tag would be awesome along with @break support during loops.

@include is great for bringing in sub views, but what about the .007% of the time that you need to sneak in a file that is not a blade or PHP file (for me, it's typically a markdown file)? While that can be done from the controller in those instances and passed to the view via a variable, it would be nice if there was another option like @get that would be similar to include, but doesn't expect the file to start in the views folder and can grab any file you pass it, not just php files.

Also, someone mentioned breadcrumbs, not sure that's so much a feature of the framework as it would be for a CMS. However, I think that might be something that could be accomplished using the route:list feature. It knows your routes, so it knows what routes above your route. It knows that /home/user/you has a parent of /home/user and of which that has a parent of /home of which that has a parent of /. So being able to return an array of the route to each parent item could be a useful function. So I think that could be something cool for anyone to build. (just a side thought).

@BenderIsGreat Sorry to ask, but why not just splitting/skipping the data in the controller? I'd imagine view layer is good enough with conditionals and simple A-Z loops. That way when you look at your view later you don't need to think what's going on.

@Ruffles @kevinjohn

How do you turn the CSRF protection?

From: Everything we know about Laravel 5.1 – Updated
https://laravel-news.com/2015/04/laravel-5-1/

CSRF Except

In Laravel 5.0 all requests are ran through the CSRF middleware and this is great for most use cases. However, one gotcha is using services with web hooks where you do not have the ability to set a token. A new feature in 5.1 is an except property on the VerifyCsrfToken class which will allow this to be easily over-ridden.

protected $except = [
 'webhook/*'
];

@zoransa http://laravel.com/docs/master/installation#install-laravel

laravel new blog

Great that Laravel 5.1 will have LTS!

Would be nice to have a native Twig support. Since all other great packages from Symfony are used why not take mature template engine as well? A normal template engine is a must.

Since TwigBridge is broken in 5.0, it is a real pain to try to port everything from Twig to Blade. Actually I have played with Blade only for a day - trying to rewrite everything and already hate it. :D

Now I have to write PHP in templates and my religion says that it is wrong. ;)

form builder like symfony

@rayhan0421 the package illuminate/html (together with a few other packages) was part of the Laravel core but it was removed and a few people from the community took it over and renamed it to laravelcollective/html. Check out the Laravel Collective's Website for more info.

@Ruffles i mean this type package ......https://github.com/kristijanhusak/laravel-form-builder

I know we'll never see it, but I would like to have the option to use doctrine as the orm instead of eloquent. Not because eloquent isn't amazing, I've been using it for a long time and I'm very comfortable using it. I just think there are some scenarios where a bit more flexibility would be nice.

@isaackearl check out Analogue, Eloquent like Data Mapper (Doctrine is a data mapper too)

Users that will do a thorough search before posting a question.

@Ruffle

Sorry Bro I started Learn laravel 5.3

@vandan29 are you posting drunk, or just up to no good?

People stop digging up these not applicable post.