-
-
Notifications
You must be signed in to change notification settings - Fork 401
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
Approve 4K Request Button Does Nothing #4509
Comments
Hi! |
I noticed after setting up the radarr4k profile and root folder the setting does not seem to apply. Navigating away from the radarr4k settings and back shows blank settings even after submitting the profile and folder change. In testing 4k request I do not see my 4k root folder as a option to select. I'm wondering if this is why the same thing happens to me, 4k request goes in and then nowhere because the new root folder path is not present. I really appreciate this new feature and look forward using it |
The root folder "disappearing" thing is common to both 4k and non 4k configuration pages. If you save the settings, navigate away and then come back and press Load Profiles and Load Root Folders, they should auto populate with the correct values. |
Ya you are correct it is doing it in both configurations. The difference being that even after saving the root folder on the 4k config It does not show up as a root folder option for user assignment or as a option when making a request. Maybe I'm wrong in assuming that is how it would work. The ability to assign this as a root folder for a user may not be an option. Are you seeing the request hit your radarr4k instance? |
Ah. Ok so different than what I'm seeing. Mine does indeed "stick". |
I am also seeing the 4k request get stuck in pending and the approve 4k doing nothing also. I thought that I could get around this by selecting the correct root folder override when making the request which is when I realized my 4k root was not there as an option. |
Makes sense. I've tried requesting with root folder override vs not. Same situation where the request is stuck pending approval and the button doesn't do anything. |
I expected a few hiccups with this. I’ll get onto it asap. Apologies guys |
I’ve also missed the admin overrides for 4K. I thought I covered everything but I must have missed that. |
This feature is an AWESOME addition! Thank you for all the hard work on this project! Kudos! |
No worries, I greatly appreciate all your hard work in continuing to develop awesome new features like this. |
…t send it to the correct 4K radarr instance #4509
So the above commit should fix the problem when approving 4k, it did nothing. If there are other issues, please can we raise a new bug, it can be hard to track when there's one issue on github with multiple issues being discussed. Regarding the area's missed, I'll get around to doing them this week |
Looks like this fixed the bulk select -> bottom right pancake button -> approve 4k request. Looks like the individual request option button -> approve 4k still doesn't function. Thanks for the quick turn around!!! |
This is not from the details page but the request grid? |
Just pushed another update to fix that. I'm already aware that the request grid is not showing correctly (Movies that only have a 4k request is still showing as Pending approval). Will fix this later |
Confirmed that fixed it! Rockstar. |
Describe the bug
Successfully enabled and configured the new 4K movie request function! Alas, all 4K Requests are required to be approved (no auto approve flag in user settings) but when clicking the Approve 4K button, nothing happens. If you click Approve Request, it follows the non-4K request flow.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The request is approved and sent to the appropriate 4K Radarr instance as configured
Logs (Logs directory where Ombi is located)
No log lines generated when clicking the Approve 4K Request button
Desktop (please complete the following information):
Ombi Version (please complete the following information):
The text was updated successfully, but these errors were encountered: