3

Yes - if your current magento version is 1.9.3.7 - then yes you need to start with from scratch !! As both version of Magento have huge difference. If you wanted to install Magento 2 - Below i am sharing two links which is self explanatory for how to install magento 2 with step by step : https://devdocs.magento.com/guides/v2.2/install-gde/bk-install-guide....


2

Copy this file and move to app/code/local/Zend/currency.php this path then local code pool file will be called instead of lib file this is the only way to override lib folder files


2

I doubt that you upgraded your shop properly. "Upgrading" does not just mean copying new files over the old ones. Yet, the issue with checking for patch SUPEE-8788 does happen in exactly this situations. But one after the other. First of all, Magento 1.9.3.7 does include SUPEE-8788 already! Hence, all your tries of applying this patch are meant to fail. Do ...


1

Do not update via backend interface. Update via filesystem!


1

I found the reason. Actually I was using the https://www.tripleginteractive.com/blog/wordpress/integrate-magento-wordpress/ solution to use WP functions inside magento and written the code in index.php file that why it was happening. Now I have placed that code in that particular file only where I am using WP functions. Hope It helps someone in future.


1

Magento scan tool and Magereport performs the same work but in little different way. I would say Magereport is more flexible than Magento scanner. I'll give you an examples here: One of my security patch was detected as failed by Magento and on the same time Magereport was saying passed. After investing a lot of effort and time we find out that Magento ...


1

It can be because of form key. You need to add following line to add form key just after form tag in give file list <?php echo $this->getBlockHtml('formkey') ?> 1) For Add to cart in product view app/design/frontend/theme/package/template/catalog/product/view.phtml 2) For login & customer registration app/design/frontend/theme/...


1

If you use PHP opcode caches (APC/XCache/eAccelerator) make sure to flush it (or restart webserver) after patching, otherwise code will continue to run from caches. Sometimes you need to upload the patched files yourself, depending on your server configuration. Running the patch script with the wrong user can result in problem. I would suggest looking at ...


1

Join the club. I have the same failed security scan and like yourself I checked the files and all is as it should be with the SOAP adapter updates. My test failed on Enterprise, patched to the latest and greatest. I did actually have a fail on SUPEE-8788 too, however, once I removed the .swf uploader files all was fixed - that patch had worked but left ...


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