disagree

Would be great to get an answer on this, still an issue.

We have a nicely configured master.php, and would like to find out how W3TC should be configured after a successful WP deployment.

– e.g. copy the master.php into the proper folders
– run a specific function?

Tried with the wp-cli available functions, but e.g. minify folders are not being built etc.

Would love to use the plugin, can you please take a look?

Is there a dev version that has those issues fixed already that could be pulled? e.g. from git

thanks, would be great if this could be fixed. cannot get the plugin to work due to this at the moment

however, $_SESSION[‘cdn’] is an Incomplete Class Object at that stage, so properties might not be accessible. so although print_r($_SESSION[‘cdn’]) will show e.g. oc_container as a key, $_SESSION[‘cdn’]->oc_container itself is also an incomplete class object and checking the type of it returns NULL.

if (is_null($_SESSION['cdn']->oc_container)) {

this check doesn’t work correctly. it gives null although oc_container is defined and an object

mysql error might be unrelated – issue still persists. mysql error is due to the missing ” , ” before the PRIMARY KEY declaration

same here. installed, tried to specify CNAME, it wouldn’t save and throw the same ‘creating default object error’. when i uninstalled, and re-activated, got the following :

WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(path_to_file)\n\t) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci' at line 3 for query CREATE TABLE IF NOT EXISTSwp_rscdn_failed_uploads(\n\t\tpath_to_filevarchar(300) COLLATE utf8_unicode_ci NOT NULL\n\t\tPRIMARY KEY (path_to_file)\n\t) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci made by activate_plugin, do_action('activate_rackspace-cloud-files-cdn/rackspace-cdn.php'), call_user_func_array, rscdn_install, dbDelta, referer: wp-admin/plugins.php?deactivate=true&plugin_status=all&paged=1&s=

function restrict_admin_area() {
    if ( !is_user_logged_in() && $_SERVER['PHP_SELF'] != '/wp-admin/admin-ajax.php' ) {
        wp_redirect( site_url() ); exit;
    }
}

add_action( 'admin_init', 'restrict_admin_area' );

put that in your theme’s functions.php. it would redirect users if they try to access the admin area, while not being logged in.

you could also simply produce a 404 there.

This would be related to namespaces which were introduced in PHP 5.3.0. Check if your PHP version is the latest.

( https://php.net/manual/en/language.namespaces.importing.php )

This would be rather related to namespaces which were introduced in PHP 5.3.0. Check if your PHP version is the latest.

( https://php.net/manual/en/language.namespaces.importing.php )

I would like to know that too!

some food for thought :
WordPress with Redis
and
Ludicrous Speed: WordPress Caching with Redis

check out the plugin ‘Typekit’, they have very nice options regarding that

https://s.stefanxo.com/oBu.png

This could maybe be accomplished by hooking it up to

add_action('login_init', 'functionname');
and
add_action('admin_init', 'functionname');

instead of add_action('init', 'functionname'); which does it globally

( wrong wording; with theme files i meant frontend pages generated by the theme )