The Magento 1.4 update provides an effective way of modifying themes that keeps changes separate from the default files through the use of the layout.xml. This allows for layout changes to be kept in one location. For a full explanation of this see ‘The better way to modify Magento layout“.
The standard Google Analytics code contains auto-detection for HTTP/HTTPS. Unfortunately Adobe contribute enforces a level of XHTML compliance that exceeds the level built into the Analytics code causing corruption of the HTML, leaving “)); at the bottom of a page after it has been edited.
I’ve just completed a website redesign and uploaded the files onto the new server, tidied up some of the code, tested and checked that my css was working correctly. during this process I find that my background image is peaking out below the footer image causing a silly white block at the bottom of my page. This was only in IE; firefox and Safari were fine.
After a line by line check between the working build page and the faulty page I noticed a single difference – the position of a comment.
Correct page looked like this
Faulty page looked like this
Who would have thought a simple comment placement could have made so much difference.