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?

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?

Full M1 CE 1.9.3.4 from the following file: magento-1.9.3.4-2017-07-12-04-19-23.tar.gz

M1 CE 1.9.3.4 includes this patch: SUPEE-9767 v2

Further information on the update: https://magento.stackexchange.com/questions/176871/security-patch-supee-9767-possible-issues

====== 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 ?

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?

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": "*"
    },

Applied following patches:

• PATCH_SUPEE-6237_EE_1.14.2.0_v1.sh
• PATCH_SUPEE-6482_CE_1.9.2….0_v1.sh
• PATCH_SUPEE-6788_CE_1.9.1.0_v1.sh
• PATCH_SUPEE-7616_CE_1.9.2.2-CE_1.8.0.0_v1.sh
• PATCH_SUPEE-8788_CE_1.9.1.0_v2.sh

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.

firegento/magento-ce now has a Chat Room on Gitter

@razbakov has just created a chat room. You can visit it here: https://gitter.im/firegento/magento-ce.

This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.

Happy chatting.

PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

https://github.com/firegento/magento/blob/714e57008c9e7d55fee8d3cab1eae13a3e50f13a/app/design/adminhtml/default/default/template/system/config/form/field/array.phtml#L77

There is enough

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

Hey, in your magento version 1.9.3.3. there is the patch SUPEE-8167 missing.

See https://magento.com/tech-resources/download?_ga=2.33092921.683408746.1498461872-518715573.1490859397#download2007

Can you merge and regenerate the tag v1.9.3.3 ?

Thx ;-)

PS: Sorry for that wrong commits before.

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 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?