I’m working on the next milestone release of ONW Simple Contact Form. One of the main features I’m adding to the plugin in version 1.9 is the ability to change the style settings of the reCAPTCHA object, but I’ll also feature some other small changes, such as the ability to auto detect the presence of other reCAPTCHA installations and to tap into their settings.
Please use the contact form on my website to send me an email if you want to help with testing. I’ll get back in contact with you and keep you updated on the availability of beta versions.
Please note whether you’d like to help test all future releases or just v1.9.
Version 1.8 of Simple Contact Form has been released.
1.8 introduces the ability to modify the text above the form and the labels for the form fields. Also, you can remove the fieldset (the border around the whole form). See more details about the plugin here. As always, if you’ve got comments relating to the plugin, not the release, please comment on the plugin’s page at the link above.
Future releases are going to feature internationalization (i18n) for multiple language support, and integration to support the WP-reCAPTCHA plugin if it’s installed.
Quick question: does anybody (all my tens of readers) know of a good resource for GOOD documentation of the WordPress brand of tinyMCE? The resources on WordPress were very basic (and more concerned with WP hooks than the tinyMCE API), and the docs on the tinyMCE are more of a reference book for those who already understand how the program works.
I was able to figure out enough to get the contact form’s button working, but the way it worked wasn’t ideal. In a perfect world, the button would insert the shortcode in the html editor and an image in the visual editor (much like WordPress already does with flash video, like a youtube embed.
Just hoping somebody stumbles across this.
I’ve been hard at work integrating the Simple Contact Form into the tinyMCE editor so that there’s a custom button.
Why would I do that, you may ask? Because the Simple Contact Form wasn’t simple enough. As crazy simple as shortcode seems to me, this is what I do for a living. It’s my job to think it’s easy and make myself look smart by using highly technical language.
With the click of a button, you can have a fully functioning contact form in any post or page.
And now the release date has arrived.
Of course, I had good reason to release some kind of an update, since the wonderful minds at Automattic just released Wordpress 2.9 (Carmen!) a couple of days ago.
Anyway, I’m sure I’ll have to release a new version soon, in a quest to make the plugin ever more accessible.
Please let me know if you have any problems with the plugin, but please post comments on the plugin page so that other people (who may have the same question) can see the discussion.
Two more things: first, if you have any suggestions for future versions, please send them my way, and I’d be happy to put them on the list. After all, I’m making this so that people will use it (and enjoy it).
Version 1.6 of my plugin ‘ONW Simple Contact Form’ has come out (and has been out for a couple of days without any reports of bugs).
In the latest stable release, I’ve added the ability to customize the subject of the email sent. You can set a default subject line in the admin page, and you can also set the subject individually in any instance of a form. To set the subject in the shortcode, use the `subject` argument. If you want the subject to include the user’s name and/or email, use %name% or %email% where you want them to go. For more information, see the plugin’s page here.
I don’t want to jump the gun too much here, but I’m in the final stages of developing a new plugin which would enable dropdown menus for any theme.
The plugin will also feature an admin page where you can limit which pages will appear in your menus.
Toodle pip!
Version 1.4.1 of ONW Simple Contact was released recently. The new version includes full reCAPTCHA integration for the spam filter, as well as a new admin panel under the settings category.
In order for the reCAPTCHA integration to work, you have to go to reCAPTCHA.net and sign up for free to get your API keys. Then you enter them into the appropriate fields in the admin settings page. Enable it, and you’re set to go.
You can still manually override the reCAPTCHA settings in the shortcode by adding the ‘onw_recaptcha’ argument (setting it to ‘on’ or ‘off’).
So I’ve gotten a couple of people telling me that they were getting the same error about the ‘filter_var’ function in PHP not being defined. My guess is that either they’re running off of an older version of PHP or their PHP settings have disabled the function. Either way, it’s out of my control.
But what I am able to do is to replace the ‘filter var’ functions with other sanitization/filtering functions.
So I did.
Version 1.3 now uses validation methods other than filter_var.
Enjoy.
New release on the simple contact form. The new version standardizes the way the bot check image is inserted. Initially, I had written the src attribute like this:
src="/wp-content/plugins/onw-simple-contact-form/check.jpg"
But that won’t work with people who have a WP installation in a subdirectory of their domain’s root directory. For example, a website (http://www.example.com) has a seperate blog (at http://www.example.com/blog/). The way I’d written the form initially, the browser will look for an image at http://www.example.com/wp-content/plugins/onw-simple-contact-form/check.jpg when it should be looking in http://www.example.com/wp-content/plugins/onw-simple-contact-form/check.jpg
Then I changed it to
src="./wp-content/plugins/onw-simple-contact-form/check.jpg"
Which fixed the last problem, but only if you have your permalinks set to the ‘ugly’ setting (http://www.example.com/index.php?p=1253), but not if you have them set to look like actual individual pages (like mine do).
So. Now I changed it to look like this:
src="'.get_bloginfo('wpurl').'/wp-content/plugins/onw-simple-contact-form/check.jpg"
Which gets the url of the directory that WordPress is actually installed in and adds the location of the image to it. So now it will work for all different types of installs.
Except those who have moved their wp-content directories. But I feel that anybody who can do that is a competent enough programmer to just go into the code and change it themselves.
I just released version 1.2 of my simple contact form last night (early this morning?). The update adds an argument to the shortcode allowing you to specify the recipient email address. You add the shortcode like normal, except before the last bracket ] you add
to_email="youremail@example.com"
You don’t have to define a recipient, though. If you leave the argument out (or if you make a typo and the address isn’t a valid email) the script will default to your blog’s admin email.
Some time this weekend, I’ll probably add an option to send a copy of the email to the blog’s admin.
~UPDATE~
There was a small bug in the release. The bot check image was not being rendered due to an incomplete filepath. That’s been fixed in 1.2.1, now released.
