Title: distobj's Replies | WordPress.org --- # distobj [ ](https://wordpress.org/support/users/distobj/) * [Profile](https://wordpress.org/support/users/distobj/) * [Topics Started](https://wordpress.org/support/users/distobj/topics/) * [Replies Created](https://wordpress.org/support/users/distobj/replies/) * [Reviews Written](https://wordpress.org/support/users/distobj/reviews/) * [Topics Replied To](https://wordpress.org/support/users/distobj/replied-to/) * [Engagements](https://wordpress.org/support/users/distobj/engagements/) * [Favorites](https://wordpress.org/support/users/distobj/favorites/) Search replies: ## Forum Replies Created Viewing 14 replies - 1 through 14 (of 14 total) * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Apache rewrite rule not working in WP 2.6](https://wordpress.org/support/topic/apache-rewrite-rule-not-working-in-wp-26/) * Thread Starter [distobj](https://wordpress.org/support/users/distobj/) * (@distobj) * [17 years, 4 months ago](https://wordpress.org/support/topic/apache-rewrite-rule-not-working-in-wp-26/#post-898989) * So fixing rewriting seems a dead end. 8-( * Anybody else got any ideas about how I can avoid these two redirects? Two is two too many, but one would at least be an improvement. The only one-redirect solution that comes to mind is to generate the Redirect commands for all (~5000!) effected permalinks and stick those in .htaccess. * Thoughts? * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Apache rewrite rule not working in WP 2.6](https://wordpress.org/support/topic/apache-rewrite-rule-not-working-in-wp-26/) * Thread Starter [distobj](https://wordpress.org/support/users/distobj/) * (@distobj) * [17 years, 4 months ago](https://wordpress.org/support/topic/apache-rewrite-rule-not-working-in-wp-26/#post-898945) * Yep, still a 404, which I’d expect because the old permalink structure was a proprietary one. Weird eh? * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Apache rewrite rule not working in WP 2.6](https://wordpress.org/support/topic/apache-rewrite-rule-not-working-in-wp-26/) * Thread Starter [distobj](https://wordpress.org/support/users/distobj/) * (@distobj) * [17 years, 4 months ago](https://wordpress.org/support/topic/apache-rewrite-rule-not-working-in-wp-26/#post-898940) * Ok, thanks. Unfortunately, I made that change but the problem persists. Here’s the full, revised .htaccess file; * # Rewrite old custom permalink structure to canonical post-id form RewriteEngine On RewriteBase / RewriteRule ^[0-9]{4}/[0-9]{2}/[ 0-9]{2}/00([0-9]*)/?$ /?p=$1 * # BEGIN WordPress RewriteEngine On RewriteBase / RewriteCond%{ REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index. php [L] * # END WordPress * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Apache rewrite rule not working in WP 2.6](https://wordpress.org/support/topic/apache-rewrite-rule-not-working-in-wp-26/) * Thread Starter [distobj](https://wordpress.org/support/users/distobj/) * (@distobj) * [17 years, 4 months ago](https://wordpress.org/support/topic/apache-rewrite-rule-not-working-in-wp-26/#post-898928) * Thanks Otto! * Here’s the rewrite that used to work in 2.5, but no longer does after the upgrade to 2.6.3; * RewriteEngine On RewriteBase / RewriteRule ^[0-9]{4}/[0-9]{2}/[0-9]{2}/00([0- 9]*)/?$ /?p=$1 [L] * what we’ve done for now is change the rule to use a 302 redirect; * RewriteRule ^[0-9]{4}/[0-9]{2}/[0-9]{2}/00([0-9]*)/?$ /?p=$1 [R=302,L] * That “works”, but it results in not just the initial 302 redirect, but a subsequent 301 to the new permalink (as you probably know), so it’s not a permanent fix ( we hope!). * Thanks again. * Mark. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [[Plugin: Yet Another Related Posts Plugin] YARPP Performance](https://wordpress.org/support/topic/plugin-yet-another-related-posts-plugin-yarpp-performance/) * [distobj](https://wordpress.org/support/users/distobj/) * (@distobj) * [17 years, 5 months ago](https://wordpress.org/support/topic/plugin-yet-another-related-posts-plugin-yarpp-performance/#post-830380) * I’ve just done a fair bit of testing, and when I enable tags & categories (at“ consider”), I see the widest variance in CPU utilization by the mysql daemon. For bodies and titles, I’m seeing anywhere from about 0.6-1.1 sec, but for tags/ categories, it can consume anywhere from 1 to 5 seconds depending upon the particular post I’m testing on. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [[Plugin: Yet Another Related Posts Plugin] YARPP Performance](https://wordpress.org/support/topic/plugin-yet-another-related-posts-plugin-yarpp-performance/) * [distobj](https://wordpress.org/support/users/distobj/) * (@distobj) * [17 years, 5 months ago](https://wordpress.org/support/topic/plugin-yet-another-related-posts-plugin-yarpp-performance/#post-830370) * Hey. Thanks for the prompt response. * I’ll answer here in case my answers are useful to others. * For “relatedness”, we have everything selected with extra emphasis on the body content as well as “require at least one tag in common”. * I turned off RSS support only because I hadn’t had a chance to see how it worked. * Performance was “worse” than with 2.06 in the sense that 2.06 took about 15 minutes to bring the server to its knees (during almost peak traffic) whereas 2.1 brought it down almost immediately despite being tested during off-peak hours. That’s not entirely an apples-to-apples comparison though, because I’d done lots of MySQL tweaking in the meantime. * Yes, we’re using WP-Supercache. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [[Plugin: Yet Another Related Posts Plugin] YARPP Performance](https://wordpress.org/support/topic/plugin-yet-another-related-posts-plugin-yarpp-performance/) * [distobj](https://wordpress.org/support/users/distobj/) * (@distobj) * [17 years, 5 months ago](https://wordpress.org/support/topic/plugin-yet-another-related-posts-plugin-yarpp-performance/#post-830368) * I just tried the new 2.1 version, hoping it would help with the performance problems we had with 2.06. Alas, it brought the server to a crawl again. * The site I tried it on has 5400 posts, about 200 categories, and a couple thousand tags (and uses WP Super Cache of course). It runs on a quad core Xeon with 4G of RAM, and CPU and which serves about a million hits per day, all while keeping CPU utilization hovering at about 5-10%. When I turn on YARRP, CPU goes immediately spikes to 90% and the site becomes unusable. * Any suggestions for how we could optimize the query that YARRP performs? Perhaps additional indexes, turn types of matching off, etc..? * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Date based archive broken](https://wordpress.org/support/topic/date-based-archive-broken/) * Thread Starter [distobj](https://wordpress.org/support/users/distobj/) * (@distobj) * [17 years, 7 months ago](https://wordpress.org/support/topic/date-based-archive-broken/#post-833381) * I solved the problem, so I thought I’d let others now. * At the same time as the move, we upgraded our plugins which included the Meta Robots plugin. Unfortunately, in my haste to upgrade, I didn’t notice that upgrading Meta Robots sets a bunch of options to “on” that were previously off. One of those options was “disable date archives”. Oops. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Date based archive broken](https://wordpress.org/support/topic/date-based-archive-broken/) * Thread Starter [distobj](https://wordpress.org/support/users/distobj/) * (@distobj) * [17 years, 7 months ago](https://wordpress.org/support/topic/date-based-archive-broken/#post-833370) * Ok, thanks again for your help. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Date based archive broken](https://wordpress.org/support/topic/date-based-archive-broken/) * Thread Starter [distobj](https://wordpress.org/support/users/distobj/) * (@distobj) * [17 years, 7 months ago](https://wordpress.org/support/topic/date-based-archive-broken/#post-833362) * Sorry, there was no subdomain. The site is [http://www.windowsmobilecool.com](http://www.windowsmobilecool.com) and we have a staging site at staging.windowsmobilecool.com where the problem can also be demonstrated. * I tried changing the permalinks structure on “staging” to default, but even then, date archive links (using “?m=200808”) still redirect to the home page. * Yes, individual post permalinks work fine. * Thanks for your help. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Date based archive broken](https://wordpress.org/support/topic/date-based-archive-broken/) * Thread Starter [distobj](https://wordpress.org/support/users/distobj/) * (@distobj) * [17 years, 7 months ago](https://wordpress.org/support/topic/date-based-archive-broken/#post-833350) * Good thinking. I changed the theme back to WordPress default, but the problem still exists. * We moved the server & switched permalinks at the same time, so never checked. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Fatal error: Maximum execution time of 30 seconds AGAIN](https://wordpress.org/support/topic/fatal-error-maximum-execution-time-of-30-seconds/) * [distobj](https://wordpress.org/support/users/distobj/) * (@distobj) * [17 years, 9 months ago](https://wordpress.org/support/topic/fatal-error-maximum-execution-time-of-30-seconds/#post-690185) * I just ran into this problem last night too, on line 274 of plugin.php. I encountered it during an import of a small WXR file. It always stops at the same point in the file, and always on that line in plugin.php. * I don’t know where it’s getting the “60 seconds” value from though – I updated php.ini temporarily and increased the value to 600, but it still complains about 60. Weird. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [WP-Cache & WP-Super Cache Increasing CPU Usage](https://wordpress.org/support/topic/wp-cache-038-wp-super-cache-increasing-cpu-usage/) * [distobj](https://wordpress.org/support/users/distobj/) * (@distobj) * [17 years, 10 months ago](https://wordpress.org/support/topic/wp-cache-038-wp-super-cache-increasing-cpu-usage/page/2/#post-661498) * FWIW, I had the same problem described here, and am also at Dreamhost. It happens with the latest versions of WP-Cache and WP-Super-Cache: a few minutes after activation, whammo, the number of httpd instances goes sky high, consuming available memory. * What I did to fix it, was move the cache directory from wp-content/cache (NFS mounted) to /tmp/hostname-wp-cache (local) by changing the relevant line in wp- cache-config.php. Luckily my cache maxes out at about 10M, so it fits well in/ tmp: YMMV. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Can’t access some drafts](https://wordpress.org/support/topic/cant-access-some-drafts/) * Thread Starter [distobj](https://wordpress.org/support/users/distobj/) * (@distobj) * [18 years, 11 months ago](https://wordpress.org/support/topic/cant-access-some-drafts/#post-550306) * FWIW, the problem was the [XHTML Validator plugin](http://rudd-o.com/projects/wp-validator/). Viewing 14 replies - 1 through 14 (of 14 total)