Disane87
Amazon rolls out frontend changes in waves
Therefore versions of Amazon plugin can be too new for people or too old. It's a bit like schroedinger's cat unfortunately.
I can also confirm this error with a DE address from amazon.
But i must admit that i have docudigger running in portainer (converted via https://www.composerize.com/ ) I have made NO adjustments, except for the e-mail, password and log level set to debug. Is it possible that you still have an "old" view of amazon? They like to distribute the changes step by step,
[0] [info] [2024-02-03 23-02:30] [scrape:all]: runAll [0] [warn] [2024-02-03 23-02:30] [scrape:amazon]: process.json not found. Full run needed. OnlyNew deactivated. [0] [info] [2024-02-03 23-02:34] [scrape:amazon]: Logged in [0] [info] [2024-02-03 23-02:36] [scrape:amazon]: First possible year: 2020 [0] [info] [2024-02-03 23-02:36] [scrape:amazon]: Last possible year: 2020 [0] [info] [2024-02-03 23-02:36] [scrape:amazon]: Selecting start year 2020 [0] Error: No element found for selector: select[name="orderFilter"] [0] docudigger scrape all exited with code 1
Ursprünglich gepostet von @Sky-Dragon in https://github.com/Disane87/docudigger/issues/446#issuecomment-1925488396
I guess the only way to have a support for older rollout version of Amazon is to stay on the working version of docudigger.
We need a way to get a frontend version of Amazon to determine the correct selectors. But at the moment I don't have a clue how to get this or if they have anything in the HTML parse. Could be that they have anything in the local storage or cookies. But at the moment it would be better to stay on the supported version until you get the updated frontend of Amazon.
Ah I figured out the problem after I have cleaned and bumped up the deps and some build errors. Please test it again with the latest dev release 2.0.3-dev.2 or the next main release