I personally prefer the CSS to load in a separate file rather than spitting out that much CSS in a style tag at the top of the page, which is why I packed it into a PHP file. However, I can render this PHP as minified CSS so keep things loading nicely. I’ll see what I can do here.
Thanks for the feedback!
Breadcrumbs are handled via the theme you’re using, so you would need to get in touch with the theme developer to see how they handle breadcrumbs so you can make the changes there.
Sorry I can’t be of more help!
Thanks so much @rabit101!
@foliumpartners: Well, yes but only if you’re using 1-3 instead of just a single digit. I might be able to resolve this by converting digits between a hyphen into two numbers and then displaying them properly. But for now this is the way it works! 🙂
The published “recipe” post will be hidden, so you can use the [cooked-recipe] shortcode to display any recipes, without the fear of duplicate content. 😉
@aum001: See my comment above, I mentioned naming it “single-cp_recipe.php”, which should work. 😉
@foliumpartners: There is a really good reason those fields are stored separately. You can adjust the servings on the front end, which will then adjust those numbers.
It would be highly suggested that you use a single digit for the amounts, both for the feature described above and also for a more straightforward recipe. 🙂
@geraldthey: Recipes are a custom post type with meta fields, so you can do a backup via the Tools > Export feature, or by simply backing up your database using something like WP Migrate DB: https://wordpress.org/plugins/wp-migrate-db/
@foliumpartners: 1-3 isn’t a valid number for Cooked. If you want to use a range, you will need to put that “1-3” in the ingredient Item column instead of on the Amount column. Here’s a screenshot:
@aum001: This is a custom theme that will be available soon. 🙂
Yes, you would have to create one. I would suggest using a child theme if possible. Copy the single.php file from your parent theme and then place it into the child theme. Rename it: “single-cp_recipe.php” and then Cooked should use that file instead of the “single.php” one:
See: https://codex.wordpress.org/Post_Type_Templates
This version is brand new and built from the ground up. Cooked Pro (when released) will replace Cooked Classic on CodeCanyon. It will include the same features and more, just done in a much better way. 🙂
Okay, I will take a look at this for the next update. Thanks @rabit101!
@travelnlass: This was something I took care of as well recently. If you go to the Recipes > Settings panel, near the bottom under the “Advanced” section you will see an option to “Disable Public Recipes”. Check that and voila! No more duplicate content. 😉
@rabit101: Here’s what’s coming in the first version of Cooked Pro, as it relates to your suggestions:
- Taxonomies: Cuisine, Cooking Method, and Tags. The ability to create your own taxonomies will be there for developers by using hooks and filters.
- Each user gets a profile, with access to their own recipes, favorites and the ability to submit recipes from the front-end.
- This will be coming at a later date in some form or another… 😉
- Lot’s of customizable widgets will be included. 🙂
