kalenjordan

Content Management

Inefficient Order Processing over Cron

I was able to run update_availability_status, update_sales_history, and execute_tasks without any issues, and I have them enabled with a cron running every 5 minutes.

I can bump the processing frequency up to 2 minutes as mentioned in the docs, if needed. But that shouldn't be necessary for the module to function, it should just increase the freshness of data.

I ran into a problem with the update_stocks task though. It's hitting a memory limit because of a very inefficient query. I traced it back to MDN_AdvancedStock_Helper_Product_Base on line 130. In my case I have like 14k order IDs that it's attempting to query.

It should be splitting the processing up in to chunks. Perhaps this is related to the problems in the initial order preparation step. Let me know.

Edit Content over the Frontend

Background

Content editing is always a little bit of a hassle. Sometimes your team might not know where a given piece of content exists - whether in CMS Pages, Static Blocks, Product content, or static HTML.

The Idea

Give admins the ability to edit content directly through the frontend via something like a blogger-style interface (you guys remember the blogger days, right?).

The Featuh's

Load via AJAX after page load - only shows if the admin is viewing the page.


	Memory usage: real: 23855104, emalloc: 23466888
	Code Profiler Time Cnt Emalloc RealMem
	mage 56.8197 1 0 0
	mage::app::init::system_config 0.0023 1 31,176 0
	CORE::create_object_of::Mage_Core_Model_Cache 0.0023 2 138,728 262,144
	mage::app::init::config::load_cache 0.0144 1 1,536 0
	mage::app::init::stores 0.0203 1 1,458,984 1,572,864
	CORE::create_object_of::Mage_Core_Model_Resource_Website 0.0004 1 21,128 0
	CORE::create_object_of::Mage_Core_Model_Resource_Website_Collection 0.0068 1 600,488 524,288

	SELECT DATE_FORMAT(o.created_at, "%b"), count(*)
	FROM sales_flat_order AS o
	WHERE created_at BETWEEN
	DATE_FORMAT(DATE_SUB(NOW(), INTERVAL 12 MONTH), "%Y-%m-01")
	AND
	LAST_DAY(DATE_SUB(NOW(), INTERVAL 1 MONTH))
	GROUP BY DATE_FORMAT(o.created_at, "%m")

	SELECT
	date_format(date_sub(created_at, INTERVAL 5 HOUR), "%Y-%m-%d") AS `Day`
	, count(*) as `Count`
	, AVG(grand_total - tax_amount - shipping_amount) AS `Avg Sales Excluding Tax/Shipping/Discounts`
	, AVG(discount_amount) `Avg Discount`
	, AVG(tax_amount) `Avg Tax`
	, AVG(shipping_amount) `Avg Shipping`
	FROM sales_flat_order
	WHERE created_at BETWEEN '2014-04-01 05:00:00' AND '2014-04-30 05:00:00'
	GROUP BY date_format(date_sub(created_at, INTERVAL 5 HOUR), "%Y-%m-%d")

	// Drop this javascript in the page where your grid is - maybe using a .phtml
	// in before_body_end or whatever.
	var statuses = document.querySelectorAll(".admin-autoemail-adminhtml-rule-index td");
	[].forEach.call(statuses, function (status) {
	if (status.textContent.indexOf("Inactive") > -1) {
	status.up('tr').style.color = "#aaa";
	status.up('tr').down('a').style.color = "#aaa";
	}
	});

	/* Here are some example custom report queries for use with the custom
	* reports module
	*
	* http://magemail.co/free-custom-reports-module-for-magento/
	*/

	/*
	* Number of items in order
	*
	* Useful to find out whether customers are buying a given product