mysqldump: Got errno 11 on write

Here is a quick one.  When trying to perform a database backup with mysqldump I received this error:

mysqldump: Got errno 11 on write.

I could find no references to this error number or a list of mysqldump error numbers.  You would think mysql would release this list else what is the point of showing a number.

Anyway, I created a new folder and gave permission to everyone  (chmod 777) and ran the mysqldump to place the backup file in that location and it worked so it appears to be a permissions issue.

Hope this helps

Facebook Comments

Magento 2 – Clearing the blasted caches and static files

I have never used a programming framework seemingly designed to frustrate the development process as much as Magento 2.  You have to constantly clear caches and static files to see your modifications, even when in developer mode.

Continue reading Magento 2 – Clearing the blasted caches and static files

Facebook Comments

New to development for Magento 2? You should read Alan Storm’s book

Having recently started work on learning the ropes with Magento 2, and finding all sorts of oddities, incongruities and banging-head-on-desk-ities, I decided to take a look at the blog of Alan Storm at alanstorm.com.

Continue reading New to development for Magento 2? You should read Alan Storm’s book

Facebook Comments

Magento 2 – Error – Exception #0 (LogicException): Unable to load theme by specified key: ‘4’

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’

Continue reading Magento 2 – Error – Exception #0 (LogicException): Unable to load theme by specified key: ‘4’

Facebook Comments

Magento 2: Command Line Interface Reference

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

Facebook Comments

Magento 1.9. One page checkout not working past address stage

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

Facebook Comments

Magneto 1 – Customer database full of spam

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

Facebook Comments

Magento 1.9x Write to Custom Log File

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.




Facebook Comments