Magento – missing blocks after 188.8.131.52 update. After updating a Magento site to v 184.108.40.206, I noticed that the randomised block code used on the homepage was missing.
Magento has released critical patch being SUPEE-5994. However, when trying to apply the patch for one Magento site, I received the following PEAR (input line 347) error
I hit the following error when trying to reindex a client’s website in Magento admin; Invalid backend model specified: catalog/product_attribute_backend_startdate_specialprice
Magento 404 frontend error. After upgrading a Magento ecommerce store from v 220.127.116.11 to 18.104.22.168 the frontend displayed a 404 error. The admin section worked
A client contacted me today unable to login into her Magento site via the admin panel. There hadn’t been any recent changes to the db or files, but every time she tried to login entering a correct username and password the page would just reset.
Resolving Magento 404 errors after theme changes can be a frustrating experience. These can usually be resolved by flushing the cache or reindexing.
“There has been an error processing your request. Exception printing is disabled by default for security reasons.”
A 503 error after upgrading Magento is often because the temporary maintenance.flag has not been automatically removed.