After renaming a custom Magneto 2 theme folder, to correct a capitalisation mistake, I ran into all sorts of issues, starting with this error:
Required parameter ‘theme_dir’ was not passed
After reading around I removed the entry from the database table “themes” and tried to set any pages or stores set to use that theme to use something else. Then I endlessly got this:
Error – Exception #0 (LogicException): Unable to load theme by specified key: ‘4’
MAGENTO 2 – COMMAND LINE INTERFACE
M2 utilises CLI (command line interface) commands heavily from using composer to install modules and keep things updated to clearing the cache, switching in and out of production mode and that sort of thing. This is very new for a Magento 1 developer like myself so it is time to start documenting all of this. Here is a list of the all the standard bin/magento commands, plus a few extra bits and pieces that have proved useful.
Continue reading Magento 2: Command Line Interface Reference
The checkout issue of not being able to proceed past entering the initial address is a real sod to sort out. There seems to be a variety of possible causes almost all of which leave no easy trail of errors or, in some cases, no errors at all. I am posting my latest discovery here after migrating a site a new server to find that I was unable to progress past stage 2 of the one-page-checkout process. Spoiler alert: it was the CSP!
Continue reading Magento 1.9. One page checkout not working past address stage
So, one day, I noticed one of my servers was sending a ton of emails out to dodgy looking ….@mail.ru or ….@list.ru addresses. UH OH!
At first I thought the mail server on my webserver had been compromised. On further investigation I managed to see to that the contents of these mails were account registration validation emails. Looking in the Magento admin (Customers>Manage Customers) I saw them…thousands of new customer registrations – with Russian copy in the name fields and, on the whole [something]@mail.ru or [something]@list.ru addresses but also some with [something]@gmail.com.
Continue reading Magneto 1 – Customer database full of spam
To write information to your own custom log file, say to trace errors in a custom module, track odd behaviour or record that a certain event has happened, you use Mage::log()
Mage::log(‘<WHAT TO WRITE IN THE LOG>’, null, ‘FILENAME.log’, true);
If you want to log the output of an array, use print_r but with the second parameter set to true – this converts the output to a string.
e.g. Mage::log(print_r($myArray,true), null, ‘FILENAME.log’, true);
I hope this is helpful. If it has and has saved you some time, feel free to buy me a beer.
OK, so as lovely having ones browser update automatically to the latest version (see that IE you annoying thing) the recent Chrome update (currently at 69.0.3497.81 – fine incrementing there lads) did something rather strange. Aside from the oddly curvy address bar and tabs (hey this ain’t no MAC) the peeps at Google have decided to remove/hide the www. part of URLs in the address bar.
So www.thelazywebdev.co.uk will be displayed in the Chrome address bar as
thelazywebdev.co.uk
Apparently this is the same for m. subdomains but I don’t have of those to test.
Anyway…for me this is REALLY ANNOYING as I have local development copies of sites without www. but that look similar to their live counterparts. Besides, in many situations the sub domain IS important.
Fortunately this odd functionality can be reset back to normal using one of the chrome settings flags. Enter this as your URL in chrome:
chrome://flags/#omnibox-ui-hide-steady-state-url-scheme-and-subdomains
and you can change it. Yes! Grumble over. I wonder how many updates away we are from this being reset.
I think custom variables were originally designed to be used in emails but I use them within the main site for little bits of information whose value needs to change on a per store/language basis.
This is how you get a custom variable inside a phtml file:
Mage::getModel(‘core/variable’)->setStoreId(Mage::app()->getStore()->getStoreId())->loadByCode(‘[variable-code]’)->getValue(‘plain’);
Continue reading Magento: Get a custom variable value in a phtml file
You may well have certain pages that you do not want Google, et al, to index in the SERPS. Examples include log in pages, thank you pages, and perhaps content of little search value such as legal blurb. This can let you control a little more, albeit very slightly, the pages you want Google to show and those that you don’t.
You can use the Custom Layout Update control (in the Custom Design tab) to set the robots control on a per-page basis. Simply add the following code into the Custom Layout Update textarea in the Magento admin:
<reference name=”head”>
<action method=”setRobots”><value>NOINDEX,NOFOLLOW</value></action>
</reference>
Continue reading Magento Custom Layout Update: Robots No-index
Some useful bits and bobs to do with ordering, size-limiting and getting data out of collections that I tend to often need to look up.
Limiting the Size of a Collection
Adding isActiveFilter
Loading Friendly URLs/Rewrites
Filter Collection by Attribute and Conditionals List
Get First Item From Collection
Continue reading Magento 1.9: Useful Collection Snippets
As of today (1st November 2017) we noticed a change in how Google is producing searching results. We knew that this change would be affecting mobile search results (mobile first index) but today we have seen it happen on desktop. This Google algorithm change might rock the SEO world…[update:….but hasn’t]
Continue reading Google TLD searches now return searcher-local results