So, i want to study laravel 9, but after i create project laravel , there is a lot of problem inside file vendor. There r 1k problems. Syntax error: unexpected token function.... etc. I tried to created a new project , but there is still a lot of problems inside vendor folder.
How to resolve this problems. I dont know what should i do
I had the same problem before. What I did was I uninstalled all the PHP extensions on my VS Code. All the alerts were gone in an instant. I just installed them again one after another to see what was causing the problem.
Related
I've got a strange problem going on with Symfony. Today I made brand new project using composer create-project symfony/website-skeleton gall command and right after installation, before doing anything in code I go to the website and the only thing that is said on webprofiler toolbar is "An error occurred while loading the web debug toolbar." I don't even get to see what kind of error is this.
The server I'm running is PHP v. 7.2.3, program is Xampp for Windows.
I thought maybe this default starting page is bugged, so I made some test controller and the error is exactly the same. Have you encountered such problem with latest symfony?
I would never figure it out myself, but adding index.php to browser address resolved the issue.
Much better solution is to use command
composer require symfony/apache-pack
As the .htaccess file is not included in the website-skeleton by default :)
Thanks for pointing me in the right direction guys!
Im working on a existing project, which uses symfony to provide web services. I'm new to Symfony technology but I have good experience in Laravel, the project has an issue in JwtAuthenticator.
Symfony\Component\Debug\Exception\ClassNotFoundException
Attempted to load class "JwtAuthenticator" from namespace
Thing is this issue does not occur in windows OS, but while working in linux Ubuntu it occurs, so far what I found is that the cache data seems to trouble, also unable to delete them without changing the folder access permission to 777. But once if it is given full access permission and if the cache folder is emptied then application runs without error, but from the next request it again happens. So if removing files in cache is done then it works.
Here, JwtAuthenticator is used to provide authentication verification
Can anyone help me to solve this.
There is a project in a bitbucket repository where I am developing with 3 more other people. We have the development branch where we close versions and it is the main branch of the project. The thing is that in my computer all files pulled from that branch works fine and I can navigate trough all pages without getting any exception. On the other hand the other 3 people are getting this error in some pages:
Like I said, in my computer this page and some other ones work fine so my guess is that's most likely an error in a file that has .gitignore or individual computer file.
Already tried:
running composer update, composer dump-autoload, php artisan optimize;
clearing cache;
searching into real syntax error in controller (didn't find anything. If there really was this syntax error i'd be getting it too because files are pulled from git);
deleting logic inside controllers to check if it was syntax error (didn't find anything again);
replacing their vendor folder with my vendor folder;
cloning the project again in their machines
These exceptions occur mainly in namespaces after /admin/editar_paginas/vantagens
We are using AdminLTE package, not sure if there is something related with it.
Honestly I have no ideia what's going on. How can it work specifically in my computer and on theirs not? Let me know if it's not clear enough.
yesterday i got stuck on a similar situation where i was not getting what the error was all about, so what i did was i deleted the controller,model ,request and migration and recreated it all it removed the error. it worked for me and if there is not much data in the database you could give it a try, laravel does produce such errors from time to time.
It was really PHP version. They had PHP 5.6 in their machines. Upgrading it to ^7.0 solved the issue.
This happened to me a couple of months ago. It might have happened in the process of a composer update, but I'm far from sure on that one. I've even updated my project to Laravel 5.3 and it still I can not get make:migration to work through Artisan. No the project it updated to 5.4 and it still do not work.
I've checked out this thread and I have the exact same problem. The symptoms were exactly the same, however the OPs solutions did not work for me.
I get no error or result in the terminal when running make:migrate.
I can generate any other file through Artisan it seems.
I tried to create a new model and pass the -m along with it. Didn't work.
I've checked permissions (and even changed migration folder), but didn't
help.
If I create my own migration-file the rest of the process through artisan works fine (migrate, DB-manipulation etc).
I've tried with different terminals and computers.
Since project were upgraded and even reinstalled I fear it has
nothing to do with the deep kernal. However maybe some sort of conflict from the higher level.
And in the last phase of my quest I tried to figure out what user interacting elements that can possibly effect the make:migration. Nothing worked.
I searched the web without any solution, then I gave up on that project and started to make my own migration files. However I now got some new hope when I saw that other thread.
After some troubleshooting I finaly managed to figure out the problem.
I narrowed it down to have something to do with the config/app.php-file.
Seems I in this project had typed in:
'timezone' => 'UTC+2'
This made creation of migration-files come to a halt without error messages. And it effected only the creation of migration-files (at least what I noticed).
I changed it to 'UTC' and it worked liked a charm again.
Note: the 'UTC+2' worked in the application and I never saw any other indications of errors regarding the rest of the app.php-file, or in the application in general.
Solution: When I instead used the parameters from this site it all worked perfectly again.
I've been developing locally on MacOS X Snow Leopard using PHP 5.3, CodeIgniter 2.0 and HMVC Modular Extensions. Everything has been working great.
Suddenly, for no reason I can pinpoint, I am occasionally getting this error when trying to bring up a page:
Unable to select the specified
database: app Filename:
/Library/WebServer/Documents/www/development/appdb/third_party/MX/Loader.php
Line Number: 96
The error doesn't occur at any specific place, it just seems to appear every 5-10 page loads or so. It usually goes away after a refresh, although sometimes I may need to refresh a couple of times.
Has anyone encountered this error before? Is it just some flakiness in mySQL on my Mac? (I also tried exporting the current DB and re-importing it under a different name and assigning that new DB, but the problem persists. I don't know of a way to test and "repair" a MySQL DB on a Mac.)
Thanks in advance for any help!
Gary
This is just an issue with your MySQL database. While I'm not sure what that issue is, HMVC has nothing to do with it.
The error comes from there as the loader is extended by HMVC, but no logic is changed. I'd fix up your database or install MAMP.