New answers tagged

0

you must have some monitoring enabled. you can use all these tools, or some of them, configure some options and settings. csf firewall fast software firewall with easy to use config + cli: https://configserver.com/cp/csf.html WAZUH (OSSEC mod) + ELK stack you can configure it to monitor and run some actions. Kibana dashboard + email reports. remote and ...


1

for hackers version detection is not from that url, they have files hashes to scan your shop to get magento version with 95% accuracy. and so the same way they scan for any vulnerabilities. what you need to do is to monitor your access log for any suspicious access pattern. also there are nginx configs that block any basics, and if you add some secutiry ...


1

This was news to me https://www.atwix.com/magento-2/hide-version/ php bin/magento module:disable Magento_Version I can't think of anything negative


0

You can get an answer from your share screenshot. Action tab already gives the answer what action need to resolve the issue. Asking to apply patches. It will resolve your issue.


0

I am currently faced with this issue when updating from 1.9.4.1 to 1.9.4.2. Whereby, admin order create, and frontend checkout now result in 500 internal server errors without any error logged or shown.


0

I'm currently on v1.9.3.1 and got several conflicts. I'm using the third version of the patch (see the filename): EDIT: After some check we are actually missing some previous patches. Will update later. PATCH_SUPEE-11155_CE_1.9.3.1_v3-2019-06-18-08-15-43.sh: 14: PATCH_SUPEE-11155_CE_1.9.3.1_v3-2019-06-18-08-15-43.sh: 127: not found PATCH_SUPEE-11155_CE_1.9....


0

Something missing with SUPEE-11155 (CE/EE) is that, on Mage_Catalog_Helper_Product class file, getDefaultProductValue method has been introduced, and rely on DEFAULT_QTY constant variable. The problem is that this variable does not exist on many different patch files, and only present on few of them: https://ibb.co/LzcL0gn Shall we patch it ourselves? ...


1

Using open-mage-lts 1.9.4.1 checking file app/design/adminhtml/default/default/template/catalog/product/helper/gallery.phtml Hunk #1 FAILED at 59. 1 out of 1 hunk FAILED Comparing -lts to core: 00:20 $ diff app/design/adminhtml/default/default/template/catalog/product/helper/gallery.phtml /tmp/gallery.phtml 62c62 < <th><?php ...


2

EE 1.13.1.0 running PHP 7.0.x with the Inchoo PHP7 module: Promotions > Shopping Cart Rules (probably others, as well): you can't save a rule, an exception, "Wrong rule specified," is thrown. We resolved this by rewriting Mage_Adminhtml_Helper_Data::removeTags with the one from 1.14.x.x (I used 1.14.4.0 - not sure of the exact version that changed it). ...


1

On M1 version 1.9.4.0 with all previous patches applied I got the following error checking file app/Mage.php Hunk #1 FAILED at 816. 1 out of 1 hunk FAILED as I can see from the patch file, it's looking for diff --git app/Mage.php app/Mage.php index 1136f6e9351..eb9e6db3a9e 100644 --- app/Mage.php +++ app/Mage.php @@ -816,9 +816,9 @@ final class Mage ...


8

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


0

On M1, 1.9.1.0 I've got Hunk #1 FAILED at 483 (different line endings). Even when I run find . -type f -exec dos2unix {} \; nothing changes. How can I know which file it is ? 486 is path line ?


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?


2

I would suggest to update to the new version on your staging environment, run the regression. If everything turns out fine, roll out the new version in production.


1

Had the same issue as @Mat On M1, 1.9.1.0 with all previous patches applied, I get numerous errors: My line endings were not set to unix/macosx on the repo (another dev using Win-dows). used dos2unix to convert the necessary files and worked. And as @chaoticgeek, I have the: Hunk #1 FAILED at 483. 1 out of 1 hunk FAILED -- saving rejects to file js/...


7

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/...


0

Change to app/code/core/Mage/Cms/Model/Wysiwyg/Images/Storage.php causes (another) bug that thumbnails not generated correctly ... details 1.9.4 thumbnails not generated correctly in media dir


2

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/...


9

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.


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


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


0

Get the latest patches, security updates, and best practices for your Magento sites https://magento.com/security


Top 50 recent answers are included