Deeba – A print function is something I can consider for the future, but it will probably be a while before I can get to that. I can look into styling options for the posts, when I have some time to do so.
Stephanie – We’ve tested it with a basic version of Thesis, and haven’t had any issues. Could you explain in more depth what the problem is? I haven’t been able to replicate it, so I’m not quite sure how to fix it.
Cathy – Click on the placeholder image, and there will be two big buttons that appear on top of it. Click the pen button to edit the recipe, click the X button to delete the recipe. Currently no, the plugin will not degrade gracefully – if you delete the plugin, your recipes should still be in your database (so if you reinstall the plugin you’ll be able to use them again) but they won’t display any longer. This is an upgrade I’m working on, and hopefully will be available soon.
Jessica – Thanks for the recommendation!
Gary – Thanks for the review. 🙂
Michael – Thanks, I’m glad to hear you like it!
Connie – If you look at the image, you’ll see that it says you need to preview or publish the post in order to see your recipe. I’ve explained why I decided to do it this way in my FAQ.
Kathy – That actually has nothing to do with the RecipeSEO plugin. hcard is not an hrecipe field, so this probably has to do with your theme itself, rather than the RecipeSEO plugin.
Deeba – The error in the Rich Snippets Testing Tool is not because of my plugin – if you test the other pages on your site where you didn’t use my plugin, you still get the same error.
James – Thanks for the suggestion for my other users. 🙂
Mike – You’re very welcome! I’m glad you like it.
Jennifer – The errors that you are getting are not related to my plugin. hfeed, hentry, etc. are things that are in your theme as a whole, not in the recipe itself. I am hoping to be able to add formatting options soon. You can put the recipe source in the ‘Summary’ section.
Nate – Thanks. Photos are something I’m planning on adding, when I get the time. Yes, all codes must be inside the *same* hrecipe div, otherwise it will not be considered a part of that recipe. For now, any formatting you want will have to be done in your theme’s CSS. I’m planning on adding styling options for all the components, but it may be a week or two before I can release that version.
Meathead – Thanks for writing about the plugin!
Venetta – Do you have the latest version of the RecipeSEO plugin, and the latest version of WordPress? If not, try upgrading and see if that helps. If you do have the latest versions, can you give me more details about the problem, and a link to the page so I can take a look at it?
Matt – Thanks, I’m glad you like it!
Amber – If you look at the image, you’ll see that it says you need to preview or publish the post in order to see your recipe. I’ve explained why I decided to do it this way in my FAQ. It will be the same for both old and new posts.
Arjun – Currently no, the plugin will not degrade gracefully – if anything happens to the plugin, your recipes will still be in your database (so if you reinstall the plugin you’ll be able to use them again) but they just won’t display while the plugin isn’t active. This is an upgrade I’m working on, and hopefully graceful degradation will be available soon. Right now you cannot edit the HTML of your recipe.
Anita – I’ve fixed the problem with backslashes before apostrophes, can you try the latest version and see if that fixes it for you? 🙂
HankShaw, Rob, Jessica, and Lauren – Could you all give me more details about exactly what happened? Unfortunately I haven’t gotten any errors on my end, so I’m going to need more information before I can try to fix it. You can email me at allison@sushiday.com so we can try to get this fixed. Thanks, and my apologies for the bug!
