juliannay

My host upgraded from 4 to 5 last weekend, and everything seems to be working, with no changes required. *knock on wood*

After searching the web a bit and some back and forth with my host, I’ve found the problem. It seems my host upgraded to ModSecurity 2, and disabling it is (a) no longer possible through the htaccess file and (b) if they disable it for me, it would be for my entire website rather than just the xmlpc file.

If anyone else is having this problem, first try one of the following:

• the solution above
• https://www.red-sweater.com/forums/viewtopic.php?pid=3218
• https://www.mydigitallife.info/2006/10/21/remove-and-uninstall-or-disable-modsecurity-mod_security/

If you get crazy errors with those fixes, it’s likely ModSecurity can only be disabled through the Apache config file, which must be done by your host. Again, this can only be done for your entire site and not just the Metaweblog API file (xmlpc.php, in most cases), so you’ll need to consider the security risk before requesting it.

This solution worked well for me when my server was using php4, but I get Internal Server Errors when on php5.

The error returned is:

Invalid command ‘SecFilterInheritance’, perhaps misspelled or defined by a module not included in the server configuration

The server is using php 5.2.5, and my host has confirmed the command is not available anymore (https://forums.wirenine.com/showthread.php?p=1522#post1522).

Is there another way to make the Metaweblog API work on php5? If it makes a difference, I’m trying to use Ma.gnolia’s blog posting feature (which worked fine with the SecFilterInheritance Off command on php4).

I found this solution:
https://www.ads-software.com/support/topic/66084

I implemented and tested it, and it worked very well. Or so I thought. Just today, I received a comment which was longer than what I had set as the maximum length. Luckily, all my comments are held in moderation, but it drove me a little crazy.

It turns out the code only works if javascript is enabled in the commenter’s web browser.

I suspect there should be a way around it with code that:
1. detects whether the browser supports javascript
a. if java enabled, uses the java version of the comment box
b. if java is not enabled, uses a text box with a set length size.

My blog doesn’t get too many comments (just the occasional very long one), so I probably won’t get around to trying to write that code for a while.

Does anyone else want to give it a shot in the meantime?

Did you ever find a solution for that? I just looked through the plug-ins, and couldn’t find anything. The only thing I can think of is changing the length of the field in the database itself, but that’s probably a very messy option.

I found a solution for people who use Ma.gnolia.

They have a Blog Tools option in your Profile. This allows you to link your Ma.gnolia account with your WP blog, and setup jobs to have links posted to your blog daily (or less frequently).

Just make sure you apply this patch:
https://www.ads-software.com/support/topic/124241

Thanks.

For reference, I had to change the Permalink structure to Default and remove the WP code from my .htaccess file.

Thanks! I replaced wp-login.php and it’s working now.