-
-
Notifications
You must be signed in to change notification settings - Fork 404
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
{"result":true,"message":null} on landing page setup in 1.9.4 #586
Comments
Repros for me as well. Step (2) isn't required however, clicking the submit button with no changes has the same result. Created a pull request: #597 Haven't tested yet, but I'm pretty sure that's it. |
Fix boostrapper-datetimepicker imports (#586)
Fixed in the release of 1.9.5 |
You mean fixed in 1.9.5? It's not fixed in the 1.9.4, thats where the issue was found. |
Tonight @RXWatcher1 ;) |
Yes I'm sorry. I mean 1.9.5. The release is very soon |
This issue remains in 1.9.5. Mono: 4.6.1 Full URL: https://my_domain/plexrequests/admin/landingpage web page output: {"result":true,"message":null} |
@RXWatcher1 |
I thought I commented but apparently I didn't. I was focused on the --base issue. This does fix the {"result":true,"message":null} message however the landing page behavior is erratic. I havent nailed down when it shows up. It seems most of the time it just doesnt show up but sometimes it will show up when logging out of the admin section. I am using the --base build but I experienced the same issue with 1.9.6. I have it set to show before the login and I have the message enabled with no time limited(defaults in place). |
@RXWatcher1 |
Plex Requests.Net Version:
1.9.4
Operating System:
Ubuntu 16.04
Mono Version:
4.6.1
Applicable Logs (from
/logs/
directory or the Admin page):Not seeing any entries related to this in the logs
Reproduction Steps:
using a base URL of /request
It seems to have saved the changes however the landing page never shows up.
The text was updated successfully, but these errors were encountered: