i know there are many questions asked about this before. but the issue is none of them is helping me in anyway?
There is no step by step configuration help..
The most colosest good help i think i could find is here in stackoverflow answer.
http://stackoverflow.com/questions/12814263/phpunit-via-composer-and-phpstorm
The answer provided by #Adam Lynch should be explained more clearly, As not everyone is expert in this debugging.
I recently installed xdebug for php today for the first time on windows 8.
Now as i am using phpstorm so went to setup the xdebug settings for phpstorm and couldn't make it to work, so i start searching net and it seemed ppl liked composer more then pear.
So i downloaded and installed composer from here.
https://getcomposer.org/doc/00-intro.md
Seems to me composer installed successfully, but now still there is issue of setting composer with phpstorm.
THERE IS NO VENDOR DIRECTORY
Gosh... i want to tell this to the person who answered in that stackoverflow. xD. i know its crazy. but i am banging banging my head over walls, no matter how much searches i do there is no vendor directory came with composer installation.???
Now how to setup the autoload.php from vendor directory if there is no vendor directory.
There is only composer.phar file.
what to put in below picture?
its been hours, i am stucked and cant find my way out of it :(
EDIT:
Thanks to #LazyOne, i now know that vendor directory will come if i define any dependency.
Now as i moved forward to install Dependency i got this error.
This is how i tried to install it.
Related
composer error
I am getting error while trying to install Composer.
The error is
Remove from the System path: c:\windows\system32.
Please help me in finding the solution.
same here but, trying to uninstall/reinstall composer but after uninstallation and clicking the composer installer i had the same prob..
I got the installer FIXED after a computer restart so that the uninstall will be complete and "system variables" will be updated.
I do not know what the problem is, but I ran into the same problem. On a hunch, I tried reinstalling composer again. When asked to choose the PhP engine, I chose PhP 5.6, which I understand is still available on all wampp / xampp installations.
That seemed to do the trick. Why 5.6 is working but 7.3 is not working I have no idea. Furthermore, I feel there is a better solution to this. Unfortunately I don't know it, but at least you can get working if that is the right solution for you.
Open CMD as Administrator type: where composer
It will show where your global composer file is.
"Remove from the System path: c:\windows\system32." If this the error you will find a "composer.bat" file in that directory. Delete that file and run installation again. Hope this fix your problem. Cheers :)
i have the same problem
i resolve by
delete php.exe in c:\windows\system32
So I've been trying to install the LaravelCollective/Html package via composer update (already added "laravelcollective/html": "5.2.*" to the project composer.json file), but I keep getting this...
[Symfony\Component\Debug\Exception\FatalThrowableError]
Class 'Illuminate\Html\HtmlServiceProvider' not found
Script php artisan optimize handling the post-update-cmd event returned with error code 1
It seems I need to update app.php, but only after the install I can't get out of.
Thanks in advance.
(Oh and I'm using Windows, if that's of any importance. And yes, I did look for answers, but most were either relative to people having trouble after install or wrongly assuming they were)
So, I ended up finding the answer myself. I really dislike when I ask for help and end up not needing any, but this answer might be useful for others thinking the same way as I did.
Some answers I looked for said something about using composer dump-autoload after installation. I didn't try this step because I was fixated on the installation failing, and assumed it only worked if the install itself did. But then I decided to go with it, then retried composer update and nothing happened (maybe a sign there was nothing broken to fix). Then I edited the config/app.php file as explained on the docs and, surprisingly, it started working. I still might need to test it a little, but for now it seems nothing's broken.
running mac Yosemite 10.10.5
A couple of days ago I installed Laravel for the first time. That part went pretty smooth! Once it was time to install composer I was able to find some help here! This command on bash Profile made it work for me: PATH="$PATH:~/.composer/vendor/bin"
Fast-Forward to today when I am attempting to install XAMPP and Bitnami.. The Apache server and all that. So I think I am ready to roll and as I tried to create a project I was told that I did not have the mcrypt file? So down THAT rabbit hole I went. That was a tough one but I managed to get it to work.
Now forgive me but I don't remember what happened next that led me to re-install composer and that turned out to be an other huge issue as it wouldn't allow me to do so.. I would get this message
Some settings on your machine make Composer unable to work properly.
Make sure that you fix the issues listed below and run this script again:
The detect_unicode setting must be disabled.
Add the following to the end of your `php.ini`:
detect_unicode = Off
After doing some research I was able to download Composer again by running this command..
curl -s getcomposer.org/installer | php -d detect_unicode=Off
I thought I was on my way.. 2 hours have gone by! Boy was I wrong! :(
What once used to work.. composer commands in my terminal.. all of the sudden are not recognized..
Commands like this worked before.. composer create-project laravel/laravel=5.0 TestApp
but now it returns this.. ??+?abelista /Applications/XAMPP/htdocs Question Marks along my machines name..
Nothing with composer runs.. I have tried changing my PATH in my Bash Profile too..
PATH="$PATH:$HOME/.composer/vendor/bin"
PATH="~/.composer/vendor/bin/laravel:$PATH"
and remember this one below used to work..
PATH="$PATH:~/.composer/vendor/bin"
From my understanding.. If I can recall correctly.. I think the problem began when I ran homebrew to install mcrypt.. I could be wrong. Does anyone here have the slightest idea what could be my issue?
BTW, according to my command line.. composer is installed..
All settings correct for using Composer
Downloading...
Composer successfully installed to: /Applications/XAMPP/xamppfiles/htdocs/composer.phar
Use it: php composer.phar
Thanks for reading and trying to help me out.
I think you've messed up with PHP installing XAMPP or other tools...
Nothing to do with composer. If you want something to work, try using Homestead, everything is setup for you in there.
In general, I would recommend you to not install stuff directly on your development machine. Try using virtual machines instead, that way you can do all the mess you want and reset everything easily.
I was following a noobies guide to Laravel, but sadly I am stumped on step one..
I have tried many threads relating to the same thing, but none seem to work - and I am stumped.
I have followed to the letter, this helpful video, and never diverted in any detail.
https://www.youtube.com/watch?v=JNn_tS2KpcY
For example I have changed all the required extension=php_openssl.dll's mentioned in posts such as this:
https://stackoverflow.com/questions/16940582/laravel-4-composer-error/16940691#16940691
As you might expect I am very new to coding, so I have provided images to help illustrate things I am not too sure about.
Firstly I download and install the .phar file, and my folder structure and files look like:
This is setup globally I assume? I also have the PATH variables added correctly when the installation prompts to add them.
So next I run composer in my command line, and successfully receive:
This to me, indicates Composer is installed at least?
Ok, next I make a folder in my WAMP server, and copy the contents from "Laravel-Master", which is from Laravels GIT and quick start guide:
Next I cd to the www folder and run the command:
composer create-project laravel/laravel your-project-name --prefer-dist
Things seem to go fine, and it does make a new Laravel "project-name" (if the folder is empty)
but then errors:
Composer could not find the config file: c: programdata\composer setup\bin To initialize a project, please create a composer.json file.
This is most annoying as I stick very close to the video linked above, but do not get the same results.
Thanks very much for your time.
Your Composer installation is misconfigured (or rather un-configured.) I don't know what that video says about installing Composer however I would download an installation executable here for Windows and follow the instructions.
If you have done this, great! However something got screwed up in the installation process, so you should try running the same installer again.
According to this and this, you could also try this command instead:
COMPOSER=composer.json composer create-project laravel/laravel your-project-name --prefer-dist
You would be better suited with Laravel Homestead, which already comes with everything you need to run Laravel in a Vagrant Box
http://laravel.com/docs/4.2/homestead
So I've recently developed a CMS with Laravel and its all working great - on my local machine that is...
When I upload it to my webserver I start getting file not found errors from what I believe is composer's autoloader.
The errors originate from the require $file on line 52 (I think, I'm not at the computer right now) in the vendor/composer/autoload_real.php.
I'm not familiar with composer at all so I'm not really sure where to start. All I do know is that it works fine on my localhost but doesn't work on my server with the exact same files. I am just lost as to what to try. Any ideas?
Thanks to everyone for their support. I've got it working now.
I deleted the vendor directory, installed composer on the server, updated my files to the ones provided at laravels github, ran composer install and finally re-uploaded my config, controllers and views.
This was necessary as composer update was giving me even more errors. Either way, I've finally got it working and you guys helped a lot.