-
Notifications
You must be signed in to change notification settings - Fork 278
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
Show count over 1000 gives some issues. #5240
Comments
i would like to note that this was not the case before i updated last which might be a week or so ago. |
It's currently limited to getting a maximum of 1000 shows per call.
Medusa/themes-default/slim/src/store/modules/shows.js Lines 84 to 92 in 359df69
Medusa/medusa/server/api/v2/base.py Lines 321 to 330 in 359df69
|
thanks. hopefully possible to fix in later update. i'll manually edit that file now for myself. |
changing those two to 2000 instead of 1000 did not fix the problem. the pyc files generate by themselves when medusa runs them? |
when you restart Medusa, yes but you need to also update the frontend code
and then you need to compile it using yarn build in themes-default/slim you need to have Node.js installed to do that https://github.com/pymedusa/Medusa/wiki/Themes#make-changes-to-existing-themes |
@sharkykh we could use vuex-persistedstate and keep the shows array in local storage and just update on load? It would mean we'd have cached results for a few seconds but I think that should be okay..? |
is a limiter here really needed? is it put in place due to performance? would it be a lot slower if limit set to 2000 or 3000? on the other hand, if a limiter is really needed here. why not just put "number of shows in database"-count as the limit? i know it's low priority for the project as it's set to 3. Low, and I'm not the average user.. but Medusa in it's current state is unusable for me so would love a fix :) |
@wimpyrbx want to try something for me? Make these changes and let me know if it loads okay. I'll make a PR when I get a chance.
|
@OmgImAlexis i did the changes to the two files and restarted medusa. no change. |
* Fix #5240 by bumping up the API pagination limit * Update CHANGELOG.md
Fixed on |
When you have db with more than 1000 shows the following issues arise:
displayShow page does not display the shows that are above 1000 count (when sorted "alphabetically")
#1000
show the show "The Young Ones" does not show data on displayShow page, but the show "A Touch of Cloth" does work.Also an issue is the dropdown box on displayShow does not render all shows, but rather stops at 1000 entries.
When I found what would be show
#1001
in the list and removed the#1000
the next show in the list (#1001
) took #1000s place in the dropdown. I tried this 4 times by removing of the of shows that was in the list. For each I removed the next in line after#1000
would be visible and displayShow worked.The index page does however display all show entries if > 1000 in total.
If this issue is affecting other aspects of the medusa enviroment I am unsure as I noticed this today.
Tested in both chrome and firefox.
No visible bugs noted in console or log files as far as I can see.
No errors reported inside medusa error reporting page.
The text was updated successfully, but these errors were encountered: