• I initially considered giving this plugin a 4-star review but thought this could be a better approach.

    Currently my go-to free plugin, it impresses with its solid features. However, a few snags are worth noting:

    Firstly, the lack of documentation is a drawback, though I appreciate the author’s commitment to fixing this soon. Hopefully, a comprehensive guide with all shortcodes included.

    The persistent “cuisine missing” warning in the rich snippet is a minor annoyance, but not that much of a problem.

    While the bulk ingredient and instruction feature is great, the absence of grouping options is a significant limitation. Many recipes require grouped instructions with headings, a functionality not currently supported in bulk inputs.

    Popular SEO plugins like Yoast and Rank Math only recognize the introduction section of the recipe, neglecting ingredients, instructions, and notes. This limits the plugin’s compatibility with widely-used SEO tools.

    The absence of a gallery option limits users to a single image for each recipe unless manually attached to individual steps.

    Introducing a rating feature without requiring comments could boost user engagement.

    Features like reading mode, timer, and meal plans (collections), usually found in premium plugins, would be awesome additions.

    Despite these areas for improvement, I’m optimistic about the plugin’s future enhancements and potential to become an even better tool for users.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Kemory Grubb

    (@w33zy)

    Hello @nwn2006,

    Thank you for providing this feedback as your input towards having this plugin grow. I will respond to each item you’ve highlighted below.

    I do know that the lack of documentation is holding back the wider adoption of this plugin. This something I have been trying to fix for a while now but there is always some setback that pushes this goal down the line. However, I can say that there are concrete plan going toward fulfilling this goal; I’ve even bought a new domain (recipepressr.com) for the site.

    A “cuisine missing” warning should not be occurring if that recipe is in fact assigned to a cuisine in the recipe editor. If that is the case I would like to look at that website. Also, I must add that there is even a “Default cuisine” feature where you set the default cuisine for recipes that does not have a cuisine explicitly set. This is a feature I added to specific fix that warning.

    In the bulk ingredients and bulk instructions inserters you can add headings by placing a hash # at that start of the line where the heading is. That will transform that line to a heading and create groups on the frontend.

    I am not too sure how to approach that issue with SEO plugins not recognizing content inside metaboxes. I will have to research how or if other plugins, such as WooCommerce, that rely on metaboxes surface their content to SEO plugins.

    I do not understand this one about galleries. Can’t you use galleries in the content editor, like you would a regular WordPress post?

    I am not too sure about this one about ratings I will have to look into user experience of having reviews and ratings on a page.

    The “reading mode” feature is doable and the “meal plan/collections” is already available via the “Favorite Recipes” extension that comes with the plugin. All you have to do is enable the extension, enter the page URL that will be favorites page and and the [rpr-favorites] shortcode to that page.

    Thread Starter Behrouz

    (@nwm2006)

    Great so 5 stars it is.

    Thread Starter Behrouz

    (@nwm2006)

    here is an example of cuisine warning:

    https://shorturl.at/glnrJ

    Plugin Author Kemory Grubb

    (@w33zy)

    In this example it looks like you didn’t enter a course and cuisine for this recipe.

    Thread Starter Behrouz

    (@nwm2006)

    But I did! Is it possible if I change the labels in taxonomies settings it doesn’t recognize them? because I have selected both of them for the recipe, but I have changed the labels to their Persian equivalent!

    Plugin Author Kemory Grubb

    (@w33zy)

    I was able to recreate your issue using Google Translator and it seems I still have some figuring out to do with figuring out how best handle RTL and non-Latin languages.

    I will release and update by this Friday that fixes this issue.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Improvements and ideas’ is closed to new replies.