Krankor

Tom,

Sorry for the late response. Turns out the new update pushed me over the WordPress Memory Limit for some reason, so flopping the standard – define(‘WP_MEMORY_LIMIT’, ’64M’); into my WP-Config ended up fixing the problem.

Thanks!