enter image description here
I get this error in PHP storm. I am learning Laravel and can someone please help me with this error. The route is not defined.
Please see the attached screenshot.
No worries. Php-storm doesn't see some of the laravel facades static classes. (e.g. 'Route::', 'Auth::'). Your code will still run fine (provided there aren't any real problems).
PS - If you haven't done it yet, install the phpstorm laravel plugin. It will help eliminate some of these issues (but not all).
Have fun!
Related
I have followed each step from https://github.com/thedevdojo/chatter but got error during migration, as well as php artisan db:seed --class=ChatterTableSeeder command also didnt worked
I forked the original Chatter repository (it was left out) as a base and created a completely new, single-page forum using Laravel resources API, Tailwind CSS and Vue.js. It's easy to install and easier to extend.
Check it at Chatter-laravel/core and check a demo here
Laravel packages help any website in so many ways. Their implementation provides you with plenty of benefits.
To help you with the Laravel Packages, Here are Top 35+ Useful Laravel Packages to Improve Website Performance
Thank you!
I am learning Queues in Laravel I want a practical learning I didnt get exactly what i want still. Please anyone explain me about this.
You should take reference from below URL.
https://scotch.io/tutorials/why-laravel-queues-are-awesome
I've been reading the docs and set up a basic app.
Every issue I've had before I've been able to solve by looking in the docs and occasionally using Google, however I can't figure this one out.
I'm using Laravel version 5.2.43 and the Paginator works fine.
I use it in my view like this,
$data->links()
But now I would like to customize the look of the paginator.
So I tried running this command
php artisan vendor:publish --tag=laravel-pagination
In the hopes of simply being able to customize that view instead of creating a new one all over but that command didn't work, it just said
Nothing to publish for tag [laravel-pagination]
So, instead I did this.
{{ $data->links('folder.viewName') }}
But this command gives me this error,
Argument 1 passed to Illuminate\Pagination\LengthAwarePaginator::links() must be an instance of Illuminate\Contracts\Pagination\Presenter, string given
So I'm not sure what's going on. The pagination works but I can't set the view myself.
Any thoughts on what's going on here?
Any help would be greatly appreciated.
I believe you can't do this in Laravel 5.2 without "hacking" the framework. Fortunately, Laravel 5.3 is released this week and it features custom pagination views
Custom pagination in Laravel 5.3
So it turns out I've been reading the 5.3 documentation for Laravel all this time. Which explains a lot of things...
So when 5.3 comes out we can do
$paginator->links("myOwnView")
Until then, I've done it the manual way of using the instances inside the paginator object.
I am working on the codeigniter framework to make a cms.During development i.e. running the site on my localhost i had two controllers and both worked fine.But now that I have uploaded it to a server it doesnt run the second Controller..
Someone having any idea regarding this please help!!
If your page shows blank page then there might be possibility of php code error
Please try with enabling error reporting on from your index.php at the top level by following code
error_reporting(E_ALL);
ini_set('display_errors',1);
If there is any code error, it will display you error with detail
Hope this will help you
I am unfortunately getting a blank page when trying to run a site locally. There are other people running it locally just fine, so I am wondering if it could be something to do with my LAMP environment.
When I attempt to load the site, it's nothing but a blank page. I've ran php index.php in console and the error I get is the following "xajax Error: xajax failed to automatically identify your Request URI.Please set the Request URI explicitly when you instantiate the xajax object.". I'm not quite sure how to handle this in CodeIgniter and or at all to be honest.
I think it's a problem with LAMP configuration: check codeigniter folder permissions (add write permission to "logs" folder.
Thanks for your answer. I actually figured out what the problem was, it was like you said a problem with my LAMP configuration. Unfortunately XAMPP (which is what I am using and or was), the newest version uses PHP 5.3. Xajax doesn't support PHP 5.3 and this was causing the problems. After I went to an older version all was well!