Whoops, our bad…
The page you requested was not found, and we have a fine guess why.
If you typed the URL directly, please make sure the spelling is correct.
If you clicked on a link to get here, the link is outdated.
What can you do?
Well, you can start by looking in /var/report/ and view the file that corresponds with the error ID on the web address.
This is just a merely nice page to display to end users as not to display any nasty php errors to them. However looking at these reports can lead useful if your needing to find out more details on whats causing the issues.
Didn’t realize this until tonight, I must be slow… but thought I would share.
Simply configure the exceptions under “System”->”Configuration”->”Design”
Expand “Themes” see the screenshot and use the values “Mobile Safari|iPhone|iPod” for Matched expression, and “iphone” for value. Since both iPhone and Android use WebKit they will both return the user agent as “Mobile Safari”. Be sure and realize it IS case sensitive for all values.
However after some further testing with some iPhones won’t return “Mobile Safari” so the condition for iPhone or iPod needs to be added as well.
I’ve been doing quite a bit of Date and Time manipulations lately, and have grown to enjoy MySQL’s DateTime fields just as much as UNIX timestamps. Particularly its built-in functions for selecting any range of fields based on a time frame.
Needing to remove all entries from a table that are older than 30 days, at first I thought I would need to iterate over the very large table (90+k) rows of data and convert each MySQL DateTime field to a UNIX time stamp to do the calculations myself with PHP. However after a bit of research I’ve learned of a few things with MySQL DateTime that make this a lot easier.
The “timestamp” field is the MySQL DateTime field. Using the DATE_SUB, CURDATE and INTERVAL one can easily grab all records that are 30 days old without the headache of converting to UNIX timestamps in PHP and doing the grunt work yourself.
Also as a side note, if you wish to convert a MySQL DateTime field to a UNIX timestamp you can easily do this by:
For those that are subscribed to the Magento RSS news feed, this may not be news to you, but for those that aren’t here is a good listing of SEO best practices for Magento. My only suggestion to Yoast was to add in Google Site map generation to their list which was added, along with a bit more about how to setup the Google site map’s thats built-in to Magento automagically generate daily or such with a cron job.
Here is the full list and I’d highly recommend alot of the tips and tricks mentioned.
Since I’ve started customizing MagentoCommerce about a year ago, here’s a few tricks I’ve learned to help further development and general operations. I don’t claim to be a Magento Expert by any means but some of this information I had to dig long and hard before finally finding a resolution to the issues I was having.
Wouldn’t it be nice if you could actually display what template files are making up the current Magento page you are viewing? Well you can! Under the Admin area -> System -> Configuration. Select the “Current Configuration Scope:” to the left. <- This is an important step to get to this feature. After you have selected the Store of your choice proceed to the “Developer” Subsection to the left you’ll notice a “Template Path Hints” field with a drop down to enable/disable it. Enabling this will cause Magento to display what .phtml or template files make up any particular page. This really helps speed up time when it comes to customizing Magento’s theme or adding functionality.
When using MagentoConnect ALWAYS do a full site backup, including all files and database dumps, I know the docs mention this quite a bit but I have completely toasted Magento before by simply trying to update Magento to its latest release. The biggest issue I have seen with using MagentoConnect is sometimes files and/or directories are not writable by the web server. The best approach I have found for this is to download the latest version via Magento’s site and copying the files manually. Particularly /app/code/core/Mage/
Innon-db-fix.sql can be your best friend. From some reason, I’m not sure why but Magento will have issues with tables in the database not being the proper type, Normally MyISAM instead of InnonDB. Using this simple SQL file can help fix “some” issues that may not seem related to it. I’m still hunting for a definitive list of what tables should be which, but it appears the majority are InnonDB.
One error that plagued me for days after an upgrade was “SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails”, The innon-db-fix.sql did NOT fix this issue for me. After reading over Magento’s community forums there was one posting in regards to residual products and or categories, ghosts basically. Any attempt to save new products or categories yielded this error, Thankfully this was on a development site and I was able to simple clear out the table: “catalog_category_product_index“, which resolved the issue and I re-imported the products I had entered in before this error appeared.
Hopefully this has helped someone if so, leave a comment.
http://bit.ly/aoGT43 Had fun reinstalling Mac OSX 10 and realizing a iBook G4 won't play youtube videos well solution: downgrade to flash 9! [molotovbliss]
but thought I would share. 
Update: 
