Now it is for example "magento/1.9.1.0", which is not right.
It is better when composer name shows github organization and repo.

Magento released multiple security patches of SUPEE-8788 contains 17 APPSEC updates. https://goo.gl/gwEafl

I am not sure if we need to include this piece of code to composer, but it will make it easier to use composer to install magento, so end-users don't need to include it in their project composer json:

     "repositories": [
        {"type": "git", "url": "https://github.com/AydinHassan/magento-core-composer-installer"}
    ],
    "require": {
        "magento-hackathon/magento-composer-installer": "*",
        "aydin-hassan/magento-core-composer-installer": "*"
    },

add version:

• 1.9.1.2

add patch for:

• 1.9.1.1
• 1.9.1.0
• 1.9.0.0
• 1.8.1.0
• 1.7.0.2

more information about patch

I think suffix "-ce" makes no sense, as enterprise edition will never be in github public repo.

Using tags which could be potentially released by magento is not good approach

Add mapping via composer or modman

@SchumacherFM try to clone https://github.com/firegento/magento
it's too slow. any idea how we can solve it?

Hello

Good Morning

Please add support for the new version of Magento, version 1.9.3.3

Thank you very much in advance

CE 1.9.2.0 is out, in case you missed it :)

Let's give it a try to use one central repo for Magento:
Firegento Magento Community Magento-1.x Mirror Github Repository with Patches.

Follow instructions in README to install magento.
In case of any problems we will fix it ASAP.

Nowadays there are thousands of other magento-mirror-repos which are doing the same job every time when new patch or magento version is released. Here is just a small list of repos, which I know:

• OpenMage/magento-lts
• bragento/magento-core
• OpenMage/magento-mirror
• AydinHassan/magento-community
• WeareJH/magento-ce

What if we bring our hands together and help each other to deliver security patches faster and with better quality?

This patch addresses two issues related to APIs and two cross-site scripting risks. - Added Aug 4, 2015

https://www.magentocommerce.com/download

Updating dependencies (including require-dev)

• MagentoCoreInstaller: Removing: "firegento/magento" version: "1.9.2.0" from: "/var/www/src"
• Removing firegento/magento (1.9.2.0)
• Installing firegento/magento (v1.9.2.1)
  Loading from cache
• MagentoCoreInstaller: Installing: "firegento/magento" version: "1.9.2.1" to: "/var/www/src"
  Writing lock file
  Generating autoload files
  /var/www/src/app/Mage.php is not a file.

Hey guys,

I was looking for a fully patched magento resource. But for older versions there a many patches missing. So what is the idea behind this repo?

For Magento 1.7.0.2 the following patches need to be applied:

2016-01-31 12:52:29 UTC | SUPEE-2677 | EE_1.13.0.2 | v2 | d20e6763cd0df70c4ac6e418c9775a1ff0f2618f | Tue Jan 14 17:49:25 2014 +0200 | v1.13.0.2..HEAD
2016-01-31 12:52:33 UTC | SUPEE-6237 | EE_1.14.2.0 | v1 | 8b216c42e2e5d2cb5d8e500fcb6690abede9df52 | Fri Jun 12 13:39:59 2015 +0300 | v1.14.2.0..HEAD
2016-01-31 12:52:33 UTC | SUPEE-1533 | EE_1.12 | v1 | _ | n/a | SUPEE-1533_EE_1.12_v1.patch
2016-01-31 12:52:38 UTC | SUPEE-2629 | EE_1.12.0.0 | v1 | 5de775cf535e137b0b099d8066bd5b3a81f7ec4c | Wed Dec 11 16:50:40 2013 +0200 | v1.12.0.0..HEAD
2016-01-31 12:52:39 UTC | SUPEE-5345 | EE_1.12.0.2 | v1 | 2d36f61cf684ed26286b6d10307fcb99dd47ff02 | Thu Feb 5 19:39:01 2015 +0200 | v1.12.0.2..HEAD
2016-01-31 12:52:41 UTC | SUPEE-6482 | CE_1.8.0.0 | v1 |  | Tue Jul 14 14:17:04 2015 +0300 |
2016-01-31 12:52:41 UTC | SUPEE-1049 | EE-1.12.0.2 | v1 | 6d06f286f461562fa6d6573349f1491f7bf89859 | Wed Feb 13 17:46:13 2013 -0800 | v1.12.0.2..HEAD
2016-01-31 12:52:42 UTC | SUPEE-7405-CE-1-7-0-2 | CE_1.7.0.2 | v1 | cf09a622d30efae9499273206790f4ca27675593 | Tue Jan 19 16:06:09 2016 +0200 | 0398c4b951..cf09a622d3

The latest Magento 1 security patch SUPEE-8788 contains 17 APPSEC updates...https://goo.gl/ZLtHB3

It seems like 1.9.3.4 got merged into the magento-1.9.3.3 branch just like the SUPEE-9767 patch.
Can we get a release tag and maybe a separat branch for it?

There is enough

                +'<?php echo $this->_renderCellTemplate($columnName) ?>'

Today was released a new version for Magento CE (1.9.3.1), I'd like to create a PR to solve this but as far as I know first a new branch "magento-1.9.3.1" should be first added to this repo. Anyone willing to do this?

The branches should be composer compliant like in https://github.com/bragento/magento-core.
This leads to automatically generated dev - Versions pointing to each branch
Thanks to @davidverholen for idea in #27

@SchumacherFM @therouv @AydinHassan what are you thoughts about it?

@SchumacherFM hi! I wanted to discuss with you some tag naming conventions.

1. Most of composer modules I've seen are using tags without "v" prefix.
   Can we agree on using version tags without prefix?

2. Signing tags with PGP keys is some unneeded overhead, that will just stop community from taking part in updates. Let's simplify the process?

3. Maybe it make sense to include descriptive changelog (like you did in README) in releases page: https://github.com/firegento/magento/releases. See for example 1.9.2.1

add patch for:

• 1.9.1.1
• 1.9.1.0
• 1.9.0.0
• 1.8.1.0
• 1.7.0.2

composer require firegento/magento ~1.9.3.1

Root package 'firegento/magento' cannot require itself in its composer.json
Did you accidentally name your root package after an external package?

composer.json

{
    "name": "firegento/magento",
    "type": "magento-core",
    "license": ["OSL-3.0", "AFL-3.0"],
    "description": "Magento CE",
    "require": {
        "magento-hackathon/magento-composer-installer": "~3.0",
        "aydin-hassan/magento-core-composer-installer": "~1.2",
        "firegento/magento": "~1.9.3.1"
    },
    "extra": {
        "magento-root-dir": "./"
    }
}

Hello,

I'm not sure if this is the correctly place to post this, if not please direct me to a proper location. I'm working on a website that is using Magento 1.8 and the URL is: www.xb2h.com

I am receiving the following error in the system.log:

2017-01-25T04:48:28+00:00 ERR (3): Warning: Creating default object from empty value in /chroot/home/crossing/xb2h.com/html/app/code/community/Nextend/AccordionMenu/library/accordionmenu/magento/tree.php on line 47

I tried initializing a class, but that just created more errors.

======
en_US

Hello

Good morning my friends

A few months ago I followed the following tutorial

Https://mozg.com.br/magento1/instalando-magento1

Where at the time was the installation of Magento 1.9.3.0

We can see in

https://mozg.com.br/magento1/instalando-magento1

If I come to update the project via composer

Running the command

composer update

It notifies you of the new version of Magento 1.9.3.1

Magento update is done, but there is a problem

After the execution of the processes by the composer

Then I see that the file

composer.json is replaced by the following content

{
    "name": "firegento/magento",
    "type": "magento-core",
    "license": ["OSL-3.0", "AFL-3.0"],
    "description": "Magento CE"
}

AND

If I come to update the project via composer

Running the command

composer update

Removal of modules that were already installed is done

I need help to stop this error

Do you know anything that might help me?

======
pt_BR

Ola

Bom dia meus amigos

Em alguns meses atrás eu segui o seguinte tutorial

https://mozg.com.br/magento1/instalando-magento1

Onde na ocasião foi feito a instalação do Magento 1.9.3.0

Podemos ver em

http://loja.cerebrum.com.br/composer.json

Caso eu venha a atualizar o projeto via composer

Executando o comando

composer update

É informado sobre a nova versão do Magento 1.9.3.1

É feito a atualização do Magento, mas ocorre um problema

Após a execução dos processos pelo composer

Em seguida vejo que o arquivo

composer.json é substituido pelo seguinte conteudo

{
    "name": "firegento/magento",
    "type": "magento-core",
    "license": ["OSL-3.0", "AFL-3.0"],
    "description": "Magento CE"
}

E

Caso eu venha a atualizar o projeto via composer

Executando o comando

composer update

É feito a remoção dos módulos que já estava instalado

Preciso de ajuda para não ocorrer mais esse erro

Sabem de algo que possa me ajudar ?

I am no more working with Magento and therefor I am looking for a new maintainer for this repository.

Does anyone want to volunteer?

Both .htaccess & .htacces.sample files are missing from v1.9.2.3

There's a file missing in this repo : /js/mage/adminhtml/uploader/instance.js

Can you please review the pull request for 1.9.3.8 patch SUPEE-10570 v2.

Need this pulled in to fix issues this is causing in checkout cart sessions.

Thank You,