We’re rewarding the question askers & reputations are being recalculated! Read more.

Hot answers tagged

20

The biggest problem, which was found: Mage::log() works incorrectly. If you call this function with custom log file (and it does not exist yet), log will not be written to the file, because of additional validation, added in the SUPEE-11086.


12

So far, I have come across the following issues with the SUPEE-10975 patch: It is not possible anymore to delete customer groups via the admin because of a missing return statement in the new method Mage_Adminhtml_Block_Customer_Group_Edit::getDeleteUrl (issue found by @mikhail-chelevich). This is the case when secret keys are enabled for the admin, which ...


11

Important: the patch name includes the highest version the patch applies to. So a patch for 1.9.3.10 would apply to 1.9.3.10, 1.9.3.9,.... down to another patch. We will try to improve naming in the next release and you can also use https://github.com/steverobbins/magedownload-cli as it should see the versions metadata properly over API.


11

Missing return parent::getDeleteUrl() in app/code/core/Mage/Adminhtml/Block/Customer/Group/Edit.php + public function getDeleteUrl() + { + if (!Mage::getSingleton('adminhtml/url')->useSecretKey()) { + return $this->getUrl('*/*/delete', array( + $this->_objectId => $this->getRequest()->getParam($this-&...


11

This patch is incompatible with the PHP 7.2 support patch. Removing lines 1711 to 1761 allows to apply the patch. This patch tries to patch files that have been removed by the 7.2 support patch. Removing these lines should be safe.


11

Error installing on 1.7.0.2 CE with all previous patches installed (see below). EDIT: Issue (#1) was caused by missing file - app/code/core/Mage/Catalog/Model/Product/Option/Type/File.php.orig Issue (#1) resolved by removing lines 874 - 1702 (referring to File.php.orig) from the patch script. Issue (#2) was caused due to improper formatting of patch and ...


9

I use this method for creating patch, hope it helps . Let suppose you will modify this file vendor/magento/module-customer/Block/CustomerData.php Create a copy of that file whith your changes on it : vendor/magento/module-customer/Block/CustomerDataModified.php What you need to do is run this command : diff -u CustomerData.php CustomerDataModified....


9

Magento 1.9.1.0. Patch was applied successfully. After adding a product to the cart and then logging in, the cart is empty again. I don't think the issue was there before and there seem to be changes made to app/code/core/Mage/Checkout/Model/Session.php UPDATE: I've debugged this a little bit. When I revert the patched version of app/code/core/Mage/...


8

I ran into an issue with the 10975 patch. After some investigation I was able to track down the answer as to where the patch was messing up and why. To summarize the below check and make sure you patched SUPEE 9767 V2 properly. That is the root of my issue. sh PATCH_SUPEE-10975_EE_v1.12.0.2_v1-2018-11-27-10-36-30.sh Checking if patch can be applied/...


7

On M1, specifically 1.9.2.1 w/ all previous patches applied. I got the following error: Hunk #1 FAILED at 483. 1 out of 1 hunk FAILED -- saving rejects to file js/tiny_mce/plugins/media/js/media.js.rej Removing the lines about that file from the patch file and manually applying that change worked for me when I re-applied the patch file. When I looked at ...


6

This might be totally just our project related but thought to share this finding. After applying this patch I noticed that if grid, like orders grid, has some custom filtering which uses filter_condition_callback setting. This might produce an error. In our case we have a date field and for the grid it has index recurring_billing_dates and '...


5

Like others, I had log files completely stop writing data. Source of the Bug - Log Files Not Writing Data In app/Mage.php they made this change: // Validate file extension before save. Allowed file extensions: log, txt, html, csv - if (!self::helper('log')->isLogFileExtensionValid($file)) { + $...


5

Firstly, sorry for the duplicate of erej's answer, i can't comment nor edit because of my reputation score. The patch creates a new file here : app/code/core/Zend/Controller/Request/Http.php Which is added to override this file : lib/Zend/Controller/Request/Http.php Problem is for Magento under 1.9.0.0 (EE 1.14.0.0) : This method : /** * Everything in ...


5

1.9.1.0, after applied patch successfully, get below error when login admin Fatal error: Call to undefined function random_int() in /app/code/core/Mage/Core/Helper/Data.php on line 257 how to fix?


5

Problem: Line endings js/tiny_mce/plugins/media/editor_plugin_src.js checking file js/tiny_mce/plugins/media/editor_plugin_src.js Hunk #1 FAILED at 379 (different line endings). 1 out of 1 hunk FAILED Solution: Execute: dos2unix js/tiny_mce/plugins/media/editor_plugin_src.js Now you can apply patch SUPEE-11219


4

I have a problem with 'Hunk #1 FAILED at 28' Rejects are supposedly saved to config.xml.rej but this file doesn't exist, neither is there any description of what part of the script failed in my terminal window. Basically the patch fails and there is no indication why - at least not to a dumbass like me! On first run the patch attempted to delete three ...


4

With version 1.8.1.0 after applying this patch we also had to change app/code/core/Mage/Core/Controller/Request/Http.php::getBaseUrl() function to be public function getBaseUrl($raw = false) { $url = parent::getBaseUrl($raw); $url = str_replace('\\', '/', $url); return $url; } because this patch adds app/code/core/Zend/Controller/Request/Http....


4

Mage::log() fails to write anything to the log files if they do not exist initially. This is due to the isValid function of Zend_Validate_File_Extension throwing a not found error when calling Zend_Loader::isReadable($value). I have temporarily fixed this by moving isValid into the try/catch after the log file is actually created and then removing the file ...


4

If you have existing customer accounts with 6-character passwords, this patch will lock them out as the new requirement is 7-character. This is pretty frustrating because there isn't any way of bulk checking this and notifying them as far as I can tell.


3

Trying to install the patch on Magento 1.9.0.1 using PATCH_SUPEE-11086_CE_1.9.1.0_v1-2019-03-26-03-03-13.sh I came accross this error Hunk #1 FAILED at 141. 1 out of 1 hunk FAILED I fixed this by removing the following code from 'app/etc/config.xml' and then running the patch again <dev> <template> <allow_symlink>0</...


3

I'm also a bit confused about the naming for the M1 patches. For older patches they named them like SUPEE-10975 for CE 1.9.3.4-1.9.3.10 or SUPEE-10888 for CE 1.9.2.0-1.9.2.4 (0.07 MB) but now it's only addressing one version PATCH_SUPEE-11086_CE_1.9.3.10_v1.sh. Is the current patch addressing all releases of a minor release or only the last one? I made ...


3

Possible issue with patching 1.9.3.10 checking file app/code/core/Mage/Adminhtml/Block/Customer/Group/Edit.php Hunk #1 FAILED at 57. 1 out of 1 hunk FAILED In the patch we have: diff --git app/code/core/Mage/Adminhtml/Block/Customer/Group/Edit.php app/code/core/Mage/Adminhtml/Block/Customer/Group/Edit.php index 8d3c526c280..fde2ef0d45d 100644 --- app/code/...


3

Now Apply Patch directly in vendor folder This patch is applicable on all Magento 2.x and 1.x versions. Alternatively you can use patched files from following address and replace them in your vendor folder. https://github.com/MeetanshiInc/Magento-Authorize-Net-Direct-Post-Patch-for-M1-M2 If Need Run php bin/magento setup:upgrade; php bin/magento setup:...


3

The Mage_Backup Module will be disabled by the patch. This is mentioned in the official release notes (https://devdocs.magento.com/guides/m1x/ce19-ee114/ce1.9_release-notes.html#ce19-1940). However the suggested solution to re-enable it is wrong: ("Alternatively, you can use one of these two methods to enable database backups") You actually need to use ...


3

Patch is supported for your version.Apply the patch PATCH_SUPEE-11086_CE_1.9.1.0_v1.sh. I was using Magento 1.9.3.7, applied PATCH_SUPEE-11086_CE_1.9.3.10_v1.sh. The patch was applied successfully. I was also confused earlier tried both 1.9.2.4 and 1.9.3.10 where the second was applied successfully which does it mean the patch can be applied for versions 1.9....


3

1.Download the composer patch for Magento 2.2 version PRODSECBUG-2198-2.2-CE.composer.patch. 2.Remove the a/ and b/ before the path name. 3.Move the patch file to your Magento root and execute patch -p0 < PRODSECBUG-2198-2.2-CE.composer.patch The patch has very critical fixes. To get the other Magento bugs fixed do update to the latest version.


3

On M1, 1.9.1.0 with all previous patches applied, I get numerous errors: checking file app/Mage.php Hunk #1 FAILED at 813. 1 out of 1 hunk FAILED checking file app/code/core/Mage/Adminhtml/Block/Catalog/Product/Edit/Tab/Super/Config.php Hunk #1 FAILED at 155. 1 out of 1 hunk FAILED checking file app/code/core/Mage/Adminhtml/Model/LayoutUpdate/Validator....


3

Magento 1.7.0.2 I'm getting: Hunk #1 succeeded at 113 with fuzz 2 (offset 4 lines). checking file js/tiny_mce/plugins/media/js/media.js checking file js/varien/js.js Hunk #1 succeeded at 707 (offset 5 lines). checking file lib/phpseclib/PHP/Compat/Function/array_fill.php checking file lib/phpseclib/PHP/Compat/Function/bcpowmod.php checking file lib/...


3

How about https://magento.com/tech-resources/download#download252 :) Sorry for one line answer (have to write something)


3

Don't have enough Rep to comment on xyphoids answer, so I'm putting this here. Passwords with <7 characters still work and users are only locked out if you overrode the templates for persistent/checkout/login.phtml and persistent/customer/form/login.phtml. Since the patch adjusted these templates to no longer validate the password inputs. If posting ...


Only top voted, non community-wiki answers of a minimum length are eligible