Yesterday when I was trying to publish a post it was redirecting me to 404 error page. The problem was with only one particular page and it was some way related to the post content. I was able to save the post when I removed some part of the post. I tried a lot of things like

• Disabling plugins
• Activating the default theme
• Updating and reinstalling WordPress
• Rewriting htaccess and updating permalinks

Nothing helped, some of the threads on this problem referred to mod_security rules. The problem was due to the mod security rules. As my post had some strings that directly relate to security issues. These obviously triggered some mod_security rules I had to disable mod_security rules temporarily to publish the post.

This is what I added to /usr/local/apache/conf/modsec2/whitelist.conf, (location may be different in your case)

[code]

<LocationMatch "/wp-admin/*">
SecRuleRemoveById 300015
</LocationMatch>

[/code]

If don’t have the permissions to edit mod_security rules, ask your hosting support team to update them for you. You may want to show this post as reference to them.

Sometimes bugs do get in !

Hello SWIFTLERS, there is a small bug in single.php file of version 4.1.3.
An extra div crept into single.php and it was breaking the layout on single post page. I corrected it and uploaded the new version on WordPress theme directory. Use the following download link until its updated on WordPress theme directory.

Sorry for the inconvenience caused

-Satish Gandham

In case if you are using version less than 2.1.4, or If you don’t want to lose the customization you did find this in <?php echo $_GET['s']; ?> search.php  and replace it with (There are 2 occurences)

[php]<?php the_search_query(); ?>[/php]

Even if you are not a swift user you should check your theme for the following vulnerability and fix it ASAP.
Search for something like this in your theme’s PHP files:

[php]Search results for "<?php echo $_GET['s']; ?>"[/php]

and replace with

[php]Search results for "<?php the_search_query(); ?>"[/php]

Note: This vulnerability is taken care in version 3.1.7, so you dont have to do any modifications.

Thanks to Rene Schmidt for reporting this vulnerability.