Im using ScrapingBee and I input this JSOn and it works fine and return the 2 expected items from my personal website. But when I add 3 more CSS selectors to scrape, I get a runtime error. Logic is the same and the CSS selectors are on the page so they should find them also, but I get runtime error 400.
this works fine in MAKE AND ScrapingBEE test console:
the ONLY difference is that the first 2 items on the page are written in php and from a mysql query without a loop, and the other 3 are in a while loop as they are written, but as far as the web page and scraping, its just elements on a page in a CSS selector to scrape right? So shouldnt make a difference, excet since its a loop there are more than one of each. Many rowas actually, but I just need the first one, but I tried doing :first-of-type but Scraping bee does not recognize those kind of selectors. Like
Does the runtime error state which field is invalid?
1.
Could you please share screenshots of the module fields and filters in question? It would really help other community members to see what you’re looking at.
2.
You can also export the scenario blueprint file to allow others to replicate the issue. At the bottom of the scenario editor, you can click on the three dots to find the Export Blueprint menu item.
If possible, could you also please provide the input/output bundles of the modules by running the scenario, then clicking the bubble on the top-right of each module, taking screenshots of, and copying the contents into this discussion thread:
This will allow others to better assist you. Thanks!
In answer to #1. there was no specific field or anything mentioned, just runtime error 400 and some very geneeric lingo.
BUT the good news is it just started working all of a sudden after a day of not working. No idea why it started working as I didnt do anything. If I had to guess it seems like MAKE was caching the sites OLD version prior to me making some changes to the site being scraped, as it was my own personal site and so I made it easier to scrape
So it just stopped giving the error. which it should not have as I said it worked fine on the ScrapingBee scrape builder page.