Sunday, April 19, 2015
Marketing Agency Coeur d'Alene ID
We're the Marketing Agency Coeur d'Alene ID that helps service & licensed professionals grow year over year without wasting precious money using our Target Marketing System.
Marketing Agency Coeur d'Alene ID
Friday, April 17, 2015
[solved] Flush Magento Logs
Believe it or not, every time a user looks at a page (pageview) in Magento, it’s logged in the database. The worst part about the Magento logs, is the fact that they’re not cleared by default, you actually have to set it up.
I normally run into a problem with logs when I’m backing up Magento. The database file will take minutes to dump and even longer to restore or recreate. In addition to a heavy database, having an excessive log file will cause Magento to load much slower than normal.
Let’s clear the logs and then setup a regular schedule for truncating the Magento logs on a regular basis. Let’s get started:
Step 1 : Truncate the database tables
[solved] Flush Magento Logs
[solved] Enable Magento Maintenance Mode with Custom 503 Page
When working with Magento there are times when you need to place the store into maintenance mode for everybody else to see a pretty notice while you still have access to the store. I’m going to give you multiple steps to follow to do just this. However, you can jump right to any step, because no step relies upon another. Here you go:
Step 1 : Putting Magento into maintenance mode
This is very easy, all that you need to do to enable Magento’s maintenance mode is to create a file in the root directory called maintenance.flag. Once this file is created Magento will serve an Error 503 :Â Service Temporarily Unavailable notice to the user.
To disable Magento’s maintenance mode, just rename or delete the maintenance.flag file and your store will be live again.
Step 3 : Enable developer maintenance bypass
When the store is in maintenance mode, you still may want to have the developers and yourself be able to access the site. To do this we’ll need to modify the index.php file found in your root folder.
[solved] Enable Magento Maintenance Mode with Custom 503 Page
Postal Codes To Help Debug Shipping
It seems that I’m always debugging shipping problems in Magento, so I’ve created this reference list of addresses from around the country to help me debug them.
[business] Microsoft Corporate Office & Headquarters
1 Microsoft Way
Redmond WA 98052
[business] Nike Corporate Office & Headquarters
1 Bowerman Dr.
Beaverton OR 97005
[business] Apple Computer Corporate
1 Infinite Loop
Cupertino, CA 95014
[business] ClickBank
917 S. Lusk St., Suite 200
Boise, ID 83706
[business] Berkshire Hathaway Inc.
3555 Farnam Street Suite 1440
Omaha, NE 68131
Postal Codes To Help Debug Shipping
[Solved] Sort Configurable Product Attribute Options and Dropdowns
So there’s this new problem that has crept into Magento 1.9.1. When you create a configurable product the attribute options resort themselves by the Simple product IDs instead of your stated sort order. To fix this problem you will need to apply the patch file that I’ve created below.
[Solved] Sort Configurable Product Attribute Options and Dropdowns
Thursday, April 16, 2015
Enable Magento Debug Mode and the Magento Profiler
There are a number of ways to debug in Magento, so I’m going to go through each of the methods that you can use to explore deep inside the core.
Logging Magento Database Queries
It is possible to log every SQL query that Magento calls. To do this we’ll need to edit the database query code to enable the debugging logs. If you’re up to the task, locate and open this file:
lib/Varien/Db/Adapter/Pdo/Mysql.php
Once you’ve located the file you’ll see the following options. Enable the $_debug member to TRUE and save the file.
/**
* Write SQL debug data to file
*
* @var bool
*/
protected $_debug = false;
/**
* Minimum query duration time to be logged
*
* @var unknown_type
*/
protected $_logQueryTime = 0.05;
/**
* Log all queries (ignored minimum query duration time)
*
* @var bool
*/
protected $_logAllQueries = false;
/**
* Add to log call stack data (backtrace)
*
* @var bool
*/
protected $_logCallStack = false;
/**
* Path to SQL debug data log
*
* @var string
*/
protected $_debugFile = "var/debug/sql.txt";
Magento Collection SQL Queries
Magento Collections are responsible for querying the database, filtering the results and joining the extra data tables. If you’re working with a Magento collection you’ll be able to print the sql statement as follows.
echo $query->printLogQuery(true);
Magento Template Path Hints and Block Names
If you’re trying to figure out how to customize the Magento template files, then you’ll want to learn about template path hints. By enabling these you’ll be able to see exactly what template files that Magento is using to create the current view. Follow this navigation to the setting:
Admin (site) > System (nav) > Configuration (nav) > Developer (sidebar nav) > Debug (accordion)
If you cannot see the template path hints or the Magento block name hints, then you’ll need to change the Current Configuration Scope. The Configuration Scope can be changed by selecting your specific store from the dropdown, just above the left sidebar.
Magento Log Files
There are two default log files that Magento will create for you. Exceptions and debug logging, although the debug logs in my opinion are not that thorough. Once enabled, you can also begin creating your own debug logs. Here’s how you enable Magento Exception and Magento Logs.
Admin (site) > System (nav) > Configuration (nav) > Developer (sidebar nav) > Log Settings (accordion)
Debugging Production Sites
If you’re attempting to debug a production website, you’ll want to limit who sees the debugging actions. For this we can use the Magento Developer Client Restrictions. To use this we’ll need to locate our public facing ip address and enter it into the Allowed IPs setting. To get there you’ll need to follow this breadcrumb:
Admin (site) > System (nav) > Configuration (nav) > Developer (sidebar nav) >
Developer Client Restrictions (accordion)
Enable The Magento Profiler
The Magento Profiler is the ultimate debugging system in Magento. This profiler will provide you with a stack trace and sql captures for debugging. To enable the Magento Profiler you’ll first need to enable it within the Magento Developer Settings. Follow this breadcrumb:
Admin (site) > System (nav) > Configuration (nav) > Developer (sidebar nav) > Debug (accordion)
Once it’s enabled in the administration, you’ll need to enable it in the code. The Magento Team has left you all of the pieces within your index.php file. All you need to do is uncomment each of the following items within your index.php file. If one of the lines does not exist, go ahead and create it.
Varien_Profiler::enable();
Mage::setIsDeveloperMode(true);
ini_set("display_errors", 1);
Enable Magento Debug Mode and the Magento Profiler
Friday, April 10, 2015
Magento Themes Forum
If you need help installing or customizing a Magento theme you are more than welcome to post your questions here.
Magento Themes Forum
Tuesday, April 7, 2015
Residual Income
We’re working together to increase our residual income streams. There are many residual income opportunities available, make sure to read the stickies and join the programs that are available.
Residual Income
Launching Software Together
Who wants to make extra money selling plugins on CodeCanyon.net? You’re encouraged to post software that you have already partially or mostly completed in order to get the support that you need to get it into production. Don’t post your wannabe ideas and dreams. We’re here to make money, not tickle your ego.
Launching Software Together
Magento Meetups and Events
There’s nobody in charge but you! Take the lead and put together a meetup in your area. Backyard BBQ or Beer at the bar, the choice is yours.
Magento Meetups and Events
Monday, April 6, 2015
Hey Eric,
You’ll need to enable Template Path Hints in order to locate the template file that’s being used. I’m confident that it’s a template file and not somewhere in the code. You can also locate the XML path that’s responsible for injecting the PO Number and remove that as well.
The PO Number is used for Level 3 Order Processing in order to get you better rates with your credit card processor. It’s also not a requirement in order to process any orders, so deleting it won’t be a problem.
Hey Eric,
You’ll need to enable Template Path Hints in order to locate the template file that’s being used. I’m confident that it’s a template file and not somewhere in the code. You can also locate the XML path that’s responsible for injecting the PO Number and remove that as well.
The PO Number is used for Level 3 Order Processing in order to get you better rates with your credit card processor. It’s also not a requirement in order to process any orders, so deleting it won’t be a problem.
Hey Eric,
You’ll need to enable Template Path Hints in order to locate the template file that’s being used. I’m confident that it’s a template file and not somewhere in the code. You can also locate the XML path that’s responsible for injecting the PO Number and remove that as well.
The PO Number is used for Level 3 Order Processing in order to get you better rates with your credit card processor. It’s also not a requirement in order to process any orders, so deleting it won’t be a problem.
Hey Eric,
You’ll need to enable Template Path Hints in order to locate the template file that’s being used. I’m confident that it’s a template file and not somewhere in the code. You can also locate the XML path that’s responsible for injecting the PO Number and remove that as well.
The PO Number is used for Level 3 Order Processing in order to get you better rates with your credit card processor. It’s also not a requirement in order to process any orders, so deleting it won’t be a problem.
Subscribe to:
Posts (Atom)