Autoload Error on Installation in my Local Machine

[rustsol]

Autoload Error
Vendor autoload is not found. Please run 'composer install' under application root directory.

[ishakhsuvarov]

You have to install composer and run 'composer install' in application root directory.

[maksek]

@yogisfunda please follow the installation guide - http://devdocs.magento.com/guides/v1.0/install-gde/install/prepare-install.html

[verklov]

@yogisfunda, we'd like to hear from you. Did you have your issue resolved using recommendations in the thread?

[rustsol]

I will solve the issue, but i'm not sure why this complication to have
composer, it was not happening with Magento 1 versions..... i want to
understand the use of installing composer, what is the concept behind it?

Thanks
Yogesh

On Fri, Jan 2, 2015 at 11:12 PM, Sergey Verklov, Senior Product Manager <
notifications@github.com> wrote:

@yogisfunda https://github.com/yogisfunda, we'd like to hear from you.
Did you have your issue resolved using recommendations in the thread?

—
Reply to this email directly or view it on GitHub
#838 (comment).

[snky1987]

Hi Yogesh,

The concept behind composer is to use universal and organised Packages Manager.

Web Applications became really complex now and lots of applications uses even more other libraries. Magento2 for example use some Symfony packages as well as some others. And simply composer is used to download them into your machine.

Advantage is that when someone improve his package you can simply update it (package) using "composer update" without downloading whole Magento anew with new core. And even then some packages may be changed with dependency to the other packages (new ones) so then composer will install them too. It should work the same with extensions.

Disadvantage of this solution however is backward compatibility so for example there may be change in Symfony package that will crash whole Magento2 application if Magento2 team don't update their packages to fir new changes. And so on.

There is no better solution for now and everyone uses Composer at the moment (incl. biggest frameworks like Zend, Symfony and Laravel) for their packages management.

[buskamuza]

Great explanation, @snky1987 . Thanks.
About backwards incompatible changes in libraries. It's not a problem, if dependency is specified as a certain version or, at least, as certain major version. For example, "zendframework/zend-stdlib": "2.3.1" means that Magento 2 is compatible only with this version, so we can avoid problems when newer version of this library is released. While, if we want to be compatible with the newer version, we can change this dependency in the new version of Magento.

[rustsol]

Thanks for the elaborated information and it looks interesting.... :)

Thanks
Yogesh
On Jan 6, 2015 5:47 AM, "Olga" notifications@github.com wrote:

Great explanation, @snky1987 https://github.com/snky1987 . Thanks.
About backwards incompatible changes in libraries. It's not a problem, if
dependency is specified as a certain version or, at least, as certain major
version. For example, "zendframework/zend-stdlib": "2.3.1" means that
Magento 2 is compatible only with this version, so we can avoid problems
when newer version of this library is released. While, if we want to be
compatible with the newer version, we can change this dependency in the new
version of Magento.

—
Reply to this email directly or view it on GitHub
#838 (comment).

[muasir]

Closing the issue based on @yogisfunda comment. Thanks @snky1987 for your explanation.

[rushabhshah341]

@ishakhsuvarov is perfectly right if you are on windows you just need to open command prompt and go to your project root directory and write "composer install" and restart your local server that's it you are all set to run by typing "http://localhost/Magento-project-name/setup" @snky1987 Thanx for explanation.