-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] sort_by=upload_date does not work #3734
Comments
I just noticed that this seems to be a more general problem with
In other words... it looks like the Either I'm doing something wrong (quite posible!) or there is a bug or the documentation needs to be updated to remove that parameter if no longer supported. Does this make sense? |
Same issue here, sort_by: upload_date doesn't actually sort by date, but private browser window search by upload_date gives different ordered results than normal search so it seems to be a bug with invidious update: I was looking through the code, it seems the doc is just wrong, param is just sort not sort_by and value is date and not upload_date. Everything works. I think the issue can be closed, maybe update the doc. |
sort=date and sort=views seem to be used instead. @SamantazFox should the api docs be updated or should the code be updated to support both? The parameter name (sort_by => sort) and some of the values (upload_date => date, view_count => views) in the api docs don't match what is used in Invidious |
This issue has been automatically marked as stale and will be closed in 30 days because it has not had recent activity and is much likely outdated. If you think this issue is still relevant and applicable, you just have to post a comment and it will be unmarked. |
PR is still open in the docs repo so this can stay open |
Calling the search endpoint with
sort_by=upload_date
does not return the results ordered by upload date.Examples:
I would expect (maybe I'm wrong?) for the results to be sorted according to the "published" property so that they match the order returned by this equivalent YouTube search:
But #2824 is similar, but not the same, as there is no colon in any of the parameters.
The text was updated successfully, but these errors were encountered: