{"id":23607,"date":"2013-06-08T12:49:47","date_gmt":"2013-06-08T12:49:47","guid":{"rendered":"https:\/\/wordpress.org\/plugins-wp\/em-object-cache\/"},"modified":"2013-07-08T21:01:37","modified_gmt":"2013-07-08T21:01:37","slug":"em-object-cache","status":"closed","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/em-object-cache\/","author":2864227,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"2.1","stable_tag":"trunk","tested":"3.6.1","requires":"3.0","requires_php":"","requires_plugins":"","header_name":"EM Object Cache","header_author":"Vladimir Kolesnikov","header_description":"","assets_banners_color":"","last_updated":"2013-07-08 21:01:37","external_support_url":"","external_repository_url":"","donate_link":"http:\/\/TBD","header_plugin_uri":"http:\/\/blog.sjinks.pro\/wordpress\/plugins\/776-sj-object-cache-faster-object-cache-for-wordpress\/","header_author_uri":"http:\/\/www.extrememember.com\/","rating":4.4,"author_block_rating":0,"active_installs":50,"downloads":6645,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":[],"upgrade_notice":{"":"

If upgrading from WP File Cache or SJ Object Cache, please deactivate and remove them first, the activate EM Object Cache.<\/p>\n\n

If upgrading from EM Object Cache 2.0, please note that the plugin path has changed (em_object_cache<\/code> => em-object-cache<\/code>).\nThios is because "an underscore character is not valid in a path, therefore you can't have em_object_cache as the plugin's slug. Only alphanumeric characters and the dash are valid."\nTherefore please uninstall EMOC 2.0 completely and then install 2.1 from the wordpress.org.<\/p>"},"ratings":{"1":"1","2":0,"3":0,"4":"1","5":"6"},"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":[],"block_files":[],"assets_screenshots":[],"screenshots":[],"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[3888,146,7913,247,3887],"plugin_category":[52,54],"plugin_contributors":[85001],"plugin_business_model":[],"class_list":["post-23607","plugin","type-plugin","status-closed","hentry","plugin_tags-apc","plugin_tags-cache","plugin_tags-object-cache","plugin_tags-performance","plugin_tags-xcache","plugin_category-performance","plugin_category-security-and-spam-protection","plugin_contributors-extrememember","plugin_committers-extrememember"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/em-object-cache.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n

The plugin implements object level persistent caching and can be used instead of the built in WordPress WP_Object_Cache<\/code>.\nUnlike WP Super Cache, Hyper Cache and other plugins, EM Object Cache does not cache the entire page; instead, it caches the data WordPress explicitly asks it to cache (using wp_cache_xxx()<\/code> API functions).\nAlthough this means that the performance will be less than with, say, WP Super Cache, all your pages remain dynamic.<\/p>\n\n

EM Object Cache won't help you much if the plugins or theme you are using do not use WordPress Cache API<\/a>.\nThis is by design, since the plugin tries to play nice. However, for most WordPress installations this will not be critical.<\/p>\n\n

EM Object Cache significantly reduces the load from your database. Say, my blog's home page without the plugin\nexecutes 24 queries (0.02403 sec); with the plugin enabled, only 4 queries (0.00188 sec).\nUnlike DB Cache\/DB Cache Reloaded, the plugin will work in the Admin Panel and supports all plugins that use WordPress Cache API.<\/p>\n\n

This plugin is the successor of WP File Cache<\/a> and SJ Object Cache<\/a> and is based on their codebases.<\/p>\n\n

CAVEATS:<\/em>\n* if you want to use FileCache caching engine, chances are that the plugin will not work when PHP safe mode is enabled and web server is operated by a different user than owns the files.<\/p>\n\n

Deactivation\/Removal<\/h3>\n\n
    \n
  1. Please make sure that wp-content<\/code> directory is writable by the web server: the plugin will need to delete object-cache.php<\/code> from it.<\/li>\n
  2. Deactivate\/uninstall the plugin in the 'Plugins' menu in WordPress.<\/li>\n
  3. Please verify that wp-content\/object-cache.php<\/code> file was removed.<\/li>\n<\/ol>\n\n\n
      \n
    1. Upload em-object-cache<\/code> folder to the wp-content\/plugins\/<\/code> directory.<\/li>\n
    2. Please make sure that wp-content<\/code> directory is writable by the web server: the plugin will need to copy object-cache.php<\/code> file into it.<\/li>\n
    3. Please make sure that wp-content\/plugins\/em-object-cache<\/code> directory is writable by the web server: the plugin will store its configuration (options.php<\/code>) there.<\/li>\n
    4. Activate the plugin in the 'Plugins' menu in WordPress.<\/li>\n
    5. Make sure that wp-content\/object-cache.php<\/code> file exists. If it is not, please copy it from wp-content\/plugins\/em-object-cache\/object-cache.php<\/code><\/li>\n
    6. wp-content\/object-cache.php<\/code> file wust me writable by the server since plugin stores its options in that file.<\/li>\n
    7. That's all :-)<\/li>\n<\/ol>\n\n

      WARNING:<\/em> if you are upgrading from 2.0, please make sure to read \"Upgrade Notice\".<\/p>\n\n\n

      \n
      The plugin does not work with Custom Field Template plugin.<\/dt>\n

      This is because Custom Field Template maintains its own cache for the post meta data which gets out of sync with WordPress cache. Please add cft_post_meta<\/code> to the list of the non-persistent groups (EM Object Cache > Generic Options)<\/p><\/dd>\n

      After activation of FileCache engine, I see an error: \"Warning: file_exists(): open_basedir restriction in effect. File(`filename`) is not within the allowed path(s)\". What to do?<\/dt>\n

      A1: Try to get rid of open_basedir<\/code> form your php.ini\/Apache config. open_basedir<\/code> is considered a \"broken\" security measure anyway and only slows down file operations.<\/p>\n\n

      A2: If disabling open_basedir<\/code> is not an option, set the Cache location<\/code> under the EM Object Cache > FileCache to the directory that satisfies the open_basedir<\/code> restriction.<\/p><\/dd>\n\n<\/dl>\n\n\n

      EMOC 2.1 (Jul 08, 2013)<\/h4>\n\n