What’s wrong with this piece of code?
Ivan Kruchkoff
function get_foo() {
$cache_key = 'fookey';
$data = wp_cache_get( $cache_key );
if ( false === $data ) {
sleep( 10 );
$data = 'foodata';
wp_cache_add( $cache_key, $data, '', HOUR_IN_SECONDS );
}
return $data;
}
Read More on Engineering challenges: Caching under high load
When making copies of a website for development and testing, populating a thorough content and data set is vital for Quality Assurance (QA). The most efficient path typically involves mirroring the entire production site’s database. But this can be problematic: a large site can have tens of thousands of posts (each with many revisions and healthy doses of metadata) and many user accounts.
Those user accounts (and sometimes the site’s content) can contain sensitive data that, if mishandled, can put clients at risk. On top of that, testing, development, and initial imports—often executed on lightweight virtual machines—can be painfully slow when working with very large datasets. Cleaning up imported production data is a must, but has been a tedious, inefficient task.
Enter 10up’s WP Hammer: an open source developer tool that quickly and efficiently reduces—or completely removes—production data and sensitive client information like email addresses and hashed account passwords from a WordPress installation.
Read More on Clean up and secure WordPress data with WP Hammer