Disable duplicate comment detection for pages and posts

I’m involved in the production of a site and I found the need to disable WordPress’s detection of duplicate comments. While often a good idea there are times in certain use-cases to turn it off. In my case the comments system was being used to communicate back and forth with individuals over the content of a custom post type. More of a case of order processing. It worked out nicely. However it was common for us to repeat ourselves, even within the same conversation.
The only solutions I found were either editing a core WP file.(NEVER EDIT WORDPRESS CORE! Every time you do a kitten dies.) There is another solution.. several years old, that temporarily wraps the comment content in a random md5 hash. Nice trick, but that filter ends up going out in email alerts about the comment. The proper way to do it is to remove the filter that does the duplicate detection! Filters are important to understanding many of the things that happen to content like wrapping chunks of text in p tags and processing shortcodes.
Here is what I added to my theme functions.php file:

A single line in your functions.php file. Nice, eh?

Lupica: Colorado school shooting shows Newtown has changed nothing – NY Daily News

Link

Lupica: Colorado school shooting shows Newtown has changed nothing – NY Daily News.

I am saddened by the Sandy Hook shooting and any school shootings since. Unfortunately you can’t stop humans from being human. Bad people will do bad things. All we can do is make them accountable. The price of freedom is bad people can do bad things because we don’t know it will happen ahead of time. Freedom is important. It isn’t always nice.

New Theme: Part 5; about face

After many hours getting things set up properly with the Reverie theme, Foundation, Compass and Codekit I realized that Reverie wasn’t going to be a good solution for me. It’s a well built theme, however it would be difficult for me to use it as a framework. It hasn’t been updated in many months and there is not sign of development other than bug-fixes. In order for me to compile Reverie as I would need to as I make changes to the SCSS files I need to make sure I’m using an older version of Foundation that would not match the available Foundation documentation. Updating Reverie to make use of Foundation 4.2.3 defeats the purpose of using a framework, which is a head-start on development.
So now I am back to Underscores and the stand-alone version of foundation with the menu system integration provided by Reverie. I copied over the custom walker functions that apply the classes needed for the Foundation. A good result.
The next thing I decided I needed was a logo. I did spend several hours designing it.. and I tried not to over-think it. I wanted something simple and elegant with some sort of twist. The twist was I was going to animate it. I’m not clear yet on the device level support, but I’m happy to say it works great on my Android OS 2.3 phone. There were javascript solutions, but I chose CSS. I will always look for a css solution before I pick a javascript one.
I’m going to start tweaking the layout and adding in features from Foundation as I find good uses for them. This theme is going to be a playground and showplace for my web design skills so putting in features just for fun is acceptable.

New Theme: Part 4; A change of direction

I dove into the code.. and cringed. One of the next things after getting all the scripts and java-scripts linked up is to start with a working menu. Now I’ve created custom menus before.. and I know how to make some adjustments to a menu structure with wp_nav_menu. But the structure Foundation wants, takes a custom walker and a structure that needs classes at the sub-menu level.   Not fun. So I was going to see if there was a good example of how to handle it in an already existing WordPress theme. I looked up the Reverie Framework before. But I wasn’t happy with how long it’s been since it’s last update. But looking through the code.. I found I *can* update the Foundation to it’s latest version. The developers did a lot of great work merging WordPress theme and Foundation. From their site it appears to be inspired by the code structure of Roots that is based on HTML5 Boilerplate and Twitter Bootstrap.

So.. Re-invent the wheel.. try to merge underscores and Foundation by myself? Hmmm.. well, the point of all of this was to have a lean, responsive website that make use of tools that would give me a head-start to get right to the customization of a WordPress theme and a chance to learn what Foundation can do for me.

So.. I’m going to try Reverie and see what I can do with it. It will also give me a chance to play with Compass.  I’ve used SASS before.. I’m still learning as I go and hadn’t gotten around to Compass yet.

I just updated Reverie to Foundation 4.2.3.  Next I’ll upload and activate it. Then I’ll dig into the code and start customizing. This is my idea of fun. So… sad. ;)