dispatch = 'feedwordpress_performance'; $this->filename = __FILE__; } function has_link () { return false; } function display () { global $wpdb, $wp_db_version, $fwp_path; global $fwp_post; if (FeedWordPress::needs_upgrade()) : fwp_upgrade_page(); return; endif; // If this is a POST, validate source and user credentials FeedWordPressCompatibility::validate_http_request(/*action=*/ 'feedwordpress_performance', /*capability=*/ 'manage_options'); if (strtoupper($_SERVER['REQUEST_METHOD'])=='POST') : $this->accept_POST($fwp_post); do_action('feedwordpress_admin_page_performance_save', $GLOBALS['fwp_post'], $this); endif; //////////////////////////////////////////////// // Prepare settings page /////////////////////// //////////////////////////////////////////////// $this->display_update_notice_if_updated('Performance'); $this->open_sheet('FeedWordPress Performance'); ?>
| Feed cache: |
This will clear all cached copies of feed data from the WordPress database and force FeedWordPress to make a fresh scan for updates on syndicated feeds. |
|---|---|
| Guid index: |
Creating this index may significantly improve performance on some large FeedWordPress installations. You have already created an index on the guid column in the WordPress posts table. If you'd like to remove the index for any reason, you can do so here. |
| Optimize IN clauses: |
Advanced setting. As of releases up to 3.3.2, WordPress
still generates many SQL queries with an extremely inefficient use of the IN
operator (for example, Note. This is an advanced setting, which affects WordPress's database queries at a very low level. The change should be harmless, but proceed with caution, and only if you are confident in your ability to restore your WordPress installation from backups if something important should stop working. You can use this setting to disable any attempts by FeedWordPress to optimize or rewrite WordPress's SQL queries. |