When trying to upgrade a Magento 184.108.40.206 site I encountered the error ‘Cannot add foreign key constraint’, when trying to update the database to 1.5, 1.6, 1.7 or 1.8.
After moving a Magento website to a new server, the downloader page reappeared, even though the site was already built. Redirects to Downloader – Solution.
Solution: Magento – Integrity constraint violation. This error is more common found when migrating / importing large amounts of data, where there is a discrepancy between the table log entries.
After installing Magento security patch SUPEE 7405, individual order pages no longer appeared within Magento’s admin section.
When trying to update a Sage Pay plugin on a Magento 220.127.116.11 site, I encountered the following Magento Connect Manager error.
Magento has been inundated with patches and security fixes. I recently encountered several odd php files on a client’s site that flagged up on MageReport as ransomware: a Magento virus that encrypts all Magento core files and demands a ransom to give you access to your site.
Magento – missing blocks after 18.104.22.168 update. After updating a Magento site to v 22.214.171.124, I noticed that the randomised block code used on the homepage was missing.
Solved – applied.patches.list” must be writeable. The issue wasn’t permissions but file format. It had been saved as Unix, so needed converting to UTF-8.