However, it also wasn’t finding existing ingredients correctly and if you upgraded and then logged in to view a post with a recipe, it probably looked like all your ingredients were lost. Don’t fret, they are still there, just don’t resave the post as you see it or they will be lost for that post. The problem has now been fixed, so please upgrade to version 2.9.6 and if you ahven’t already upgraded from previous versions, you should feel safe that this problem won’t effect you if you go straight to version 2.9.6.

Many thanks to user Peter Ricci for finding this error and reporting it to me so that we could get it all fixed up! If you notice any other quirks surrounding this, please comment here or post in the support forums.

Enjoy!

UPDATE: Due to the amount of bug reports coming in, I’ve rolled the stable version number back to 1.9.4. I will be getting things sorted out as soon as I can, but have had a death in the family consuming my attention right now instead. Thanks for your help and patience during this time. – TH, 2/9/13

Another cool new feature from a developer’s point of view is the improved field output function which is now being used by the recipe meta box and the options page. Everything is output in a neat, orderly fashion and sanitized before it is saved. Yay for clean code!

Here’s a full breakdown of fixes and updates:

• fixed a few missing text strings for localization
• major code cleanup for things like whitespace
• adding php docs for major functions
• changed the ingredients selection to “chosen” select box
• improved checks and balances by creating settings defaults function
• depcrecated recipress_post_type() in favor of recipress_options( ‘post_type’ )
• depcrecated recipress_use_taxonomies() in favor of recipress_options( ‘taxonomies’ )
• deprecated recipress_theme() in favor of recipress_options( ‘theme’ )
• added option to “unlink” ingredients
• changed recipress_time() to accept iso format as boolean
• updated icon.css for 3.5
• improved repeatable fields by creating empty array, rather than repeating code
• added functions for properly sanitizing options and meta
• moved html output for options and meta box fields into it’s own, cleaner, easier to use function
• removed use of Google font in admin areas
• fixed recent recipes widget to support custom post type
• changed media uploader from old thickbox method to new media manager (3.5 now required)

The pro add-ons are still on the roadmap and 10up (the company I work  for) will be taking over the oversight of the development of these. We should have more updates in regards to actual plans for this coming in the second quarter and hope to officially ramp up development. Thanks for holding on; we promise you won’t regret it!

Why has “soon” taken so long?

I’ve said before on the blog that it has been difficult to keep up with the development because I’m working on this alone. Add that to the personal struggles I’ve experienced this year (sickness, hospitalization, job loss, etc.), and you’ve got yourself a delayed plugin. Thankfully, I’m now employed by not just another web company, but a team of WordPress experts that specialize in premium WordPress engineering, 10up. We’re going to wrap ReciPress into company oversight which means I’ll have backup and help with future development.

I still don’t want to promise any dates quite yet, but I am working on a major cleanup of the core plugin and do feel confident that the first two add-ons (print and advanced search), will be available sometime in the next few weeks. I can’t wait to share these with you and as always appreciate you’re ongoing support and patience.

Another new feature with this release is the ability to add other time to the ready to time calculation. Several users had pointed out that the ready time wasn’t always a simple calculation of prep +  cook. Now you can add any extra time that the recipe calls for into the “other time” field and the ready time will calculate accordingly.

The Changelog

• changed “Upload Image” to a more suitable “Add Image”
• made options and meta box field behave more similarly
• added option to change post types
• added an “other time” input for proper “ready time” calculation.
• fixed Quick Edit error of removing hasRecipe

So here’s the deal, I’m going to select 5 varied beta testers based on my criteria of what I’m looking for, and those 5 users will gain access to a hidden forum so that we can discuss bugs and issues. Those lucky 5 will also get a lifetime ReciPress license absolutely free when it hits the shelves! Applications will run between now and Friday.

Submit to be a Beta Tester

All Beta Testers have been chosen and testing is under way!

Other Help

If you’re not selected to be a beta tester or if you’d just like to help monetarily, I am now taking donations to kickstart the Recipress marketplace. I need a little financial help to get the store up and running as I mentioned before in a previous post. All users that give a donation will receive an equal amount in store credit.

I have the best users a developer could ask for. Thanks so much for your help. Let’s get this show on the road!

The Changelog

• Added functions to add and remove items from arrays
• Cleaned up recipress_fields array and changed the way items are added
• Cleaned up recipress_options_fields array and changed the way items are added
• Converted the output into a filterable array
• Added default to recipress_recipe

If you’ve been muddling around with making changes to the way the recipe is outputted, options, or the meta box, this update will put a double rainbow in your sky.

Filterables

The functions recipress_options_fields(), recipress_fields(), and the_recipe() are now filterable and each item is it’s own array value with a unique key. Plus, there’s a couple of built in funcitons that will let you add and remove array items. This will let you filter the function to add items in specific places, change items, and even remove them altogether. Here are a few examples:

Add an Allergy Information Textarea to the Meta Box After the Instructions Input

add_filter('recipress_fields', 'recipress_insert_allergies');
function recipress_insert_allergies($meta_fields) {
	$allergies = array(
		'allergies' => array(
			'name'	=> __('Allergy Information', 'recipress'),
			'desc'	=> __('Describe any allergy information about this recipe.', 'recipress'),
			'id'	=> 'allergies',
			'type'	=> 'textarea'
		)
	);

	return recipress_array_insert($meta_fields, 'instructions', $allergies);
}

Add the Allergy Information to the Recipe Output After the Instructions

add_filter('the_recipe', 'recipress_allergies');
function recipress_allergies($recipe) {
	$allergies = array(
		'allergies' => '<p><small>'.recipress_recipe('allergies').'</small></p>'
	);

	if (recipress_recipe('allergies'))
		return recipress_array_insert($recipe, 'instructions', $allergies);
	else
		return $recipe;
}

To find out more about these new functions, see the documentation on Filterables.

It also includes five new languages! These language files are donated by plugin users and are thus not supported by me. If you notice any errors, please let us know in the support forums and we’ll try to get it fixed.

1.9.2 Changelog

• fixed error for adding widgets after ReciPress taxononmy widgets
• fixed Quick Edit error of removing hasRecipe
• fixed recipress_recent count
• made the_recipe() filterable
• removed all HTML from recipress_recipe
• added shortcode [recipress_recent]
• updated English language file
• added new translations: French, Japanese, Slovenian, Hungarian, & Italian

The Bad News

So the plugin is no where near ready for the public, not even for testing.  I haven’t had the time to develop it and I’m so far behind schedule it’s time to wipe that one off the board and start a new one.

The Good News

I’m now working a 4 day work week and using Fridays to work on my own projects and ReciPress is at the top of my list!  I want to start getting the most requested features out and then continue to introduce more features as we go along. Some features are more niche and will be released as add-on’s rather than in the core plugin itself.

Besides time, money has also been a barrier. There will be an up front cost for me to get this thing out to you in a way that will be future proof and simple to manage from both ends. My plan is that once the plugin is close enough to being ready to be sold, I’ll allow you to pre-purchase your license at a discount. The proceeds will be used to finance the plugins and the eCommerce setup, etc. Please give me feedback on that idea in the comments.

I’ve also moved the mailing list from Feedburner to MailChimp to make it easy to send you pretty news updates. If you’re a registered user, you probably got an opt-in notification for this. If you don’t wish to receive updates to your email, simply ignore the opt in or unsubscribe.

Lastly, I’ve beefed up the footer area a bit to offer an easy way to subscribe and a quick glance at what’s going on in the news blog.