poundifdef / plainoldrecipe Goto Github PK

Found a broken recipe, where no directions/ingredients are displayed:

https://www.plainoldrecipe.com/recipe?url=https%3A%2F%2Fwww.realsimple.com%2Ffood-recipes%2Fbrowse-all-recipes%2Fmustard-pork-chops

Perhaps this will be fixed by updating the scrapers dependency, but if not I don't mind digging into why this is failing.

Sorry if this a dumb question, but is there a way to run plainoldrecipe locally without deploying to gcloud as described in the README.md?

It would be great if there were a title tag for the recipe, this would help give the browser a clue for saving files that included the recipe title.

I don't have a way to test a patch locally, but I found that adding this to the @screen style improves the layout of the ingredients:

            li {
                -webkit-column-break-inside: avoid;
                page-break-inside: avoid;
                break-inside: avoid;
            }

some websites checks the JS support and blocks the request if its not exists.
e.g. https://www.rewe.de/rezepte

if i try to add a parser i get as response

<h1 data-translate="turn_on_js" style="color:#bd2426;">Please turn JavaScript on and reload the page.</h1>

I appreciate this project and it's ability to cut the fat on a lot of recipe websites.

While we all want our favourite sites to be compatible as soon as possible it's seems odd to have yet another repo of parsers. recipe-scrapers, a dependency of this project, is quite mature in the amount of scrapers it has and it used by other projects. Wouldn't it make more sense to encourage parser PRs to be sent to that project and eventually get them downstream? In doing so, each repo can be focused on singular functionality while sharing the parsers with more projects.

Something as simple as a line in README or a reminder in a Github issue template would suffice.

Thanks

Bit of a minor issue, but I'm often using this app on mobile, where the <input /> element will appear quite small / is not an ideal UX.

I propose making the site a bit more responsive by adding some very simple mobile-friendly CSS. I am well-versed in this area and would love to open a PR and help add this, if we think it's a good idea.

Thanks for making this app, I use it multiple times a week (because I can't stand the ads and long-winded stories that often accompany recipes on food blogs).

These days there are a very great many recipes shared via Pinterest. If it's possible to add it to the list of supported sites I'm sure many would appreciate it (besides myself).

To save the user a click/entering tab, let's auto-focus the input whenever the page loads.

I don't mind opening a PR for this, as it should be very straightforward to implement. 👍

Would it be possible to log the sites that folks are trying to use and post statistics to help prioritize which parsers might be most useful?

Minor feature request to include the photo in the print version of the recipe. This is helpful for dead-tree versions recipes I keep on hand for later.

Thanks so much, this is awesome!

Revisted this bookmarked page and got the error:

https://plainoldrecipe.com/recipe?url=https%3A%2F%2Fwww.spendwithpennies.com%2Foven-baked-chicken-breasts%2F

Then tried a random recipe from one of the other supported sites and received the same error.

E.g. https://plainoldrecipe.com/recipe?url=https%3A%2F%2Fwww.seriouseats.com%2Frecipes%2F2016%2F04%2Fno-knead-english-muffins-recipe.html

Currently, when adding a new recipe parser, you have to map the full hostname to the parser code, including the "www". It would be nice if we could standardize on just using the top-level domain ("example.com"), and for the code to, by default, also map "www.example.com".

Might be nice to have a bookmarklet on the home page. I've found this useful:

javascript:void(window.open('https://plainoldrecipe.com/recipe?url='+location.href.replace(/%5C/$/,%20'')));

These parsers all seem to do essentially the same thing:

• bowlofdelicious
• gimmesomeoven
• hostthetoast
• lovingitvegan
• minimalistbaker

I'd like to add thewoksoflife.com which includes the same json. Ideally I could just add it to a whitelist or something, instead of copying a lot of boilerplate.

Alternatively, since the format seems to be fairly common, you could potentially grab the html, attempt to scrape it, and only if that fails you would show the unsupported page.

I would love to add a Favicon missing in this project to make this project stand out from a group of tabs/websites.

Please assign me this issue or let me know if we can discuss on a favicon to use and then let me create PR.

PlainOldRecipe 🚀 @poundifdef

The website is offline, did the domain name expire?