Magento comes with a sample file in your root as auth.json.sample you need to copy it to auth.json
It contains 2 key sets: 1 for Github and 1 for the Magento Repo
Enter the following data to your auth.json file to login. Please use the Public Key and the Private Key
I use "CENTOS PHP 5.4.43 cURL 7.19.7"
In downloader/lib/Mage/HTTP/Client/Curl.php, try changing:
Extension Installation & the Consequences
The idea of having an extensible system is great, but as we developers know, its not that simple. Many things can (and, unfortunately, do) go wrong.
I'll start with a list of issues potentially caused by installing extensions. Then, I'll make my main point and state the conclusions I personally make ...
Just put a .htaccess (or if nginx/whatever a config) into the downloader directory with Disallow from all in it to forbid any request on the directory.
If you wanted to allow a few IP addresses in (like your own), try something like this in your .htaccess
deny from all
allow from 22.214.171.124 126.96.36.199
Where 188.8.131.52 and 184.108.40.206 are IP ...
I think that removing extensions on MC is bit too extreme .. Connect is not just for mechants but for developers as well (I love the upgrade feature). But I agree that people without right skills should not install extension as they are seldom compatible with used themes, there are too many potential conflicts and more often than not it'll cause totally ...
Along with @daniel-sloof's recommendation I would say to ditch the Magento Connect installer altogether. I generally add it to .gitignore when setting up a new repository.
The reason being, as Fabian points out in his answer comments, that there is no way to ensure the replication of your production environment in source control without committing the ...
We have had many clients install extensions via Connect, and I'm aware of many thousands of sites using our extension successfully as a result. Connect needs a revamp, everyone is aware of that. But as technology solution providers we should be making our products ever easier, and my ultimate goal at WebShopApps is to reach a point where a merchant can ...
Installing via SSH:
Obtain the Connect 2.0 key via Magento Connect:
Ensure that mage is executable from your Magento root:
chmod +x ./mage
Execute ./mage install and paste your extension key immediately after the word 'install' - remove the slash between 'community' and your extension package name. E.g.:
./mage install http://connect20.magentocommerce....
After reading other people's opinion I decided to write my own.
I will not accept this answer because I promised so. :)
I only have on extension published on Magento Connect (MC), because of latest policy it has.
I'm a developer and I only know how to develop.
I have no artistic skills at all, the only thing I know about Photoshop is that it exists and you ...
Login in magento using your credentials.
Then follow the navigation
3.My Access Key
Public Key: xxxxx
Public Key used as user name and Private Key used as password.
Let's say you have developped a module under app/code/Vendor/Module, here is the procedure you have to follow:
Create a composer file
Go to app/code/Vendor/Module and create the following composer.json file:
"description": "Description of your Magento 2 module",
Magento Connect Channel 2.0 support was introduced first time in CE 220.127.116.11-rc1. However, some problems arose and in rc2 it was replaced with MCC 1.0 version. It was introduced again in 18.104.22.168-alpha1 and from that time is used in all Magento releases. I believe this information is included into official Magento Connect guide.
All the "maintenance mode" does is creating empty semaphore file maintenance.flag to store root folder. You can create the file manually if you want to, however you can't get into backend interface after that. You can also delete it manually.
Maintenance flag behavior itself is simple and it can be found from index.php file:
$maintenanceFile = 'maintenance....
Previous examples are correct. In addition it is also possible by composer's config command.
Inside the Magento project directory execute the following Composer command:
$ composer config http-basic.repo.magento.com <public_key> <private_key>
Just replace the placeholders with the actual values (public_key will become the username and ...
No, you can't. Magento Connect will refuse to install a package if any of the packages files already exist on the system. While to you it seems like this extension is installed, since it was installed manually Magento Connect is unaware of it, and therefore can't upgrade it. This is a (reasonable) precaution to ensure to package manager doesn't remove ...
That first example should be correct and is a Connect 2.0 format key. That's the format you want for Community 1.9. It looks like your error comes from the 2nd example which isn't a hostname. If you copy the installer key directly from Connect as-is on the product page it should work. Alternatively you can use a tool like http://freegento.com/ddl-magento-...
Currently the Marketplace is Magento 2-only, and Connect is Magento 1-only. Later this year Magento 1 support will be added to the Marketplace (on a temporary basis, I think), at which point vendors will be engaged to migrate their listings across. Once that is done, Connect will go away entirely. The exact timeline and migration process is yet to be ...
Whether an extension is approved or not-approved, an email is sent to the email address listed on your community member account. For your particular instance, please check your email for a rejection letter and tips of corrections required for final approval.
As long as the extension meets the Magento Connect Guidelines, your extension will be approved. Also,...
I think it's really up to the developer - removing your extensions from connect attempts to force people to better manage their codebase as they can't install from admin, but at the same time means they are that much less likely to actually find the extension in the first place. Ultimately people are going to have their stores developed exactly how they ...
We are forgetting how excellent 'Connect' was when Magento first came out. It showed that Magento was a developer platform rather than one of those open source projects that nobody uses. Although 'Connect' was useful for ensuring Magento gained adoption, time has moved on and I think that people expect to be a little less 'happy go lucky' with extensions ...
You can use this link to fetch all of them:
However, it still won't be too reliable as it contains also extensions which are no longer available on Magento Connect site.
You can also fetch list of releases for single extension eg:
Magento 1.5 and up require Magento Connect 2.0
According to this post if you package it for Magento Connect 1.0 it wil automatically create the 2.0 version for you. But then again, who wants to support Magento Community versions < 1.5 in 2013?
I usually delete the downloader directory, but also found the following directive in the root htaccess helpful:
RewriteRule ^downloader/ - [L,R=404]
Which will make Apache send a 404 response even if the downloader directory is present.
What you can try here is to delete the file downloader/connect.cfg. This file should be created the next time you load the Magento Connect section of the website.
I would always suggest taking a backup of files before deleting them though just for the case that something goes wrong.
We (ebizmarts) have removed extensions from MagentoConnect in the past, over the years we've only kept the ones we are willing to support and are financially viable to us. By accepting these basic rules, we were able to keep support under control and merchants/developers happy.
MagentoConnect as it is right now, only works for listing, discovery, and ...