Level 12
It's not a composer dump-autoload thing is it? also I assume you did composer install?
Aug 29, 2014
7
Level 16
4.3 - Classes not found
I just took the most recent copy from the dev branch to play about with. After everything has updated I get the standard you have arrived screen but as soon as I started to do anything like Form::open, HTML::style etc... I just get errors like
Symfony\Component\Debug\Exception\FatalErrorException thrown with message "Class 'HTML' not found"
Stacktrace:
#1 Symfony\Component\Debug\Exception\FatalErrorException in /home/vagrant/Code/forum/storage/views/56c382bc8a2b88ef74bf0bf1605ff8a5:5
#0 Illuminate\Exception\Handler:handleShutdown in <#unknown>:0
Has anyone else had those? I am guessing they have been renamed / moved elsewhere? I see that there's a few things that have been removed from the aliases.
Anyho, it's 5:30 here, I should go to bed this is what happens when you get side tracked by new things :(
Level 12
I notice the alias is also not listed in app.php, and it's not in my vendor illuminate folder
'HTML' => 'Illuminate\Support\Facades\HTML',
been removed? maybe still being implemented?
Level 12
This tweet would be relevant
Level 18
If I recall what I read on the live feed from the Laracon, Form is no longer standard. You have to bring it in yourself.
Ahh, @aardalich beat me to it. :)
Level 8
It's interesting that these are optional. I wonder if any work is done to separate these from the framework/backed and bring them closer and more easily customisable within the views. I rely on twig and not blade for my views and have a lot of macros equivalent to these. However these are not tied to the framework but are macros I can easily customise within my views. I am wondering if laravel is following this route
Level 16
Ah, interesting they're optional now
Please or to participate in this conversation.