You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I want to use the CSS Selector Bridge to generate a feed from this https://www.deschakelbarendrecht.nl/search page, however the bridge is not able to find the elements with the links, while finding it in the browser works fine. I checked that the articles are not loaded asynchronously, they are already present if you download the page through curl.
To Reproduce
Steps to reproduce the behavior:
Set up the bridge with these parameters: action=display&bridge=CssSelectorBridge&home_page=https://www.deschakelbarendrecht.nl/search&url_selector=a.block.relative&url_pattern=&content_selector=&content_cleanup=&title_cleanup=&limit=100&format=Html
go to the generated feed
The following error will be shown: No results for URL selector
Expected behaviour
A feed is generated with links to the articles
Additional context
I am running the tool in a docker container. The lack of debugging in the logs makes it very difficult to find the cause.
The text was updated successfully, but these errors were encountered:
Describe the bug
I want to use the CSS Selector Bridge to generate a feed from this https://www.deschakelbarendrecht.nl/search page, however the bridge is not able to find the elements with the links, while finding it in the browser works fine. I checked that the articles are not loaded asynchronously, they are already present if you download the page through
curl
.To Reproduce
Steps to reproduce the behavior:
action=display&bridge=CssSelectorBridge&home_page=https://www.deschakelbarendrecht.nl/search&url_selector=a.block.relative&url_pattern=&content_selector=&content_cleanup=&title_cleanup=&limit=100&format=Html
No results for URL selector
Expected behaviour
A feed is generated with links to the articles
Additional context
I am running the tool in a docker container. The lack of debugging in the logs makes it very difficult to find the cause.
The text was updated successfully, but these errors were encountered: