enderandrew

The problem is that the count is off. So my tag cloud links to tags that it thinks are in use, when they are not.

There are some plugins that delete tags that have a count of zero, but I need to recalculate the count.

Thanks! I did remove the ifmodules earlier realizing they are pointless. I know I have the modules loaded. I also removed the IP-based denies and moved them to my firewall.

I’m also going to experiment for a few days with Apache worker as opposed to prefork (which has also necessitated moving to php5-cgi). Everyone says it uses less memory and is faster, but right now it appears to be using more memory.

I’ll move the redirects up above rewrites.

I’ll also check out the p3-profiler plugin tonight.

Here are my new rules, a little shorter: https://pastebin.com/rtK8KW5X

I’ve also thought of trying nginx, but that means converting all those rules and honestly I’d be lost.

I’m on 2.2.22.

You mentioned coming 75-82 and how 75 and 76 were redundant. I’m looking at a regex basics guide, and I’m assuming I’d combine them like this:

RewriteCond %{QUERY_STRING} ((<|%3C)([^s]*s)+cript.*(>|%3E)|(<|%3C)([^e]*e)+mbed.*(>|%3E)|(<|%3C)([^o]*o)+bject.*(>|%3E)|(<|%3C)([^i]*i)+frame.*(>|%3E)) [NC,OR]

I assume a lot of the rewrite rules are somewhat redundant. The second I fired up the VPS, I was getting hit by would-be hackers in Romania, Thailand, Taiwan and China. I’ve installed a few WordPress security plugins who added such rules, as well as followed this guide:

https://perishablepress.com/6g-beta/

I think moving the rules to my config and out of .htaccess did have a noticeable impact, but I also assume I could benefit from consolidating those rules.

If you’ve any more advice (such as how to change the RedirectMatch rules) that would be great.

My rules are duplicated under <VirtualHost *:80> and <VirtualHost *:443> so I really only have half as many as it looks like.

I’m terrified to launch this site publicly because this is happening with almost no traffic hitting the site right now.

I’m running apache2-mpm-prefork with stock settings from Debian. My site config has a lot of rewrite rules in it for WordPress, caching and security. I’ve moved those to 000-default.conf and out of .htaccess to help with performance. My 000-default.conf is here:

https://pastebin.com/yaZb4Q8d

And my enabled Apache modules are:

alias auth_basic authz_host authz_user cache cgi deflate dir env expires filter headers include info mime negotiation php5 reqtimeout rewrite setenvif speling ssl status

I suspect it might be a bad WordPress plugin and PHP causing all the problems. I’m tempted to crank down my PHP settings just in case.

The worst case is what is happening where Apache eats so much memory the entire system is unresponsive and does nothing. Can I write a basic script that checks memory consumption and restarts the apache2 service if need be?

Or can someone help me and point me to how I would identify what is causing the memory to spike every once in a while? Would there be something in the Apache logs at some point?

Sadly, I’m in the same boat. It does not seem to work with newer versions of Buddypress or bbPress.

+1 for half stars please!

The G+ sprite doesn’t show up for me. I cleared my WP cache, my mod-pagespeed cache and browser cache. I can see it in my sprite.png file, but it isn’t showing up on the site.

I have a redirect issue as well that stops me from logging out.

Will do. I’ll experiment with disabling different plugins.

I’m running WP 3.4 from SVN if it makes a difference.

Thanks!

Thanks! This is a bleeding edge development server I’m working on, which is why I was showing warnings. I’ll test it there.

I hadn’t voted down the plugin because it has worked great in the past. If something breaks when I’m testing bleeding edge stuff, I assume I broke it rather than the plugin is broken.

I’ll gladly test the new version. Please send me a URL.

I can test it. But the errors ended up being my own fault. I still had Use Google Libraries activated, but I was testing WP 3.4 so it was pulling the wrong version of jquery.

You can always delete the folder with an FTP client or whatever to disable a plugin. But I get the same fatal error trying to activate the plugin.