[Bug] Allow advanced download option doesn't close settings pane
See original GitHub issueSelecting Allow advanced download
in the Settings under Advanced
somehow disables the functionality to save the settings.
The button turns blue, but is not clickable.
It does change the setting if you press the save button and manually reload the site with f5
. Pressing cancel rejects the changes.
Best regards.
Issue Analytics
- State:
- Created 3 years ago
- Comments:14 (14 by maintainers)
Top Results From Across the Web
Can't Download Anything on a Windows 10 Computer [Solved]
Step 1: Press Windows + X and then select the Settings option from the menu. Step 2: Select the Update & security setting...
Read more >Repair apps and programs in Windows - Microsoft Support
Select the Advanced options link under the name of the app (some apps don't have this option). On the page that opens, select...
Read more >Safari Downloads Not Working? 10 Troubleshooting Tips and ...
Having issues with downloads in Safari on your Mac? We'll cover how to troubleshoot lost, stuck, and missing Safari downloads problems.
Read more >What to do if you can't download or save files | Firefox Help
Reset the download folder · Type about:config in the address bar and press EnterReturn. · In the Search field, enter browser. · If...
Read more >Fix the common issues in fillable forms in Acrobat or Reader
(Check for the Standards panel button  in the Navigation pane.) If PDF/A was used, re-create the PDF without the PDF/A setting to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m thankful for your great support efforts! Now we at least know where to look when someone reports a bug with similar log files 😉
Sounds like a server-side issue (something had to have gone wrong in the saving of the config file). Do you see any container-side logs?
Also, if you can go into the Network tab in the Chrome DevTools, you should see the setConfig API calls going out. If you can paste the request payload over in the bottom of the Headers tab, that might point to what’s going on (maybe that JSON is malformed)
Alternatively, you can make an admin account and email me the credentials at IsaacMGrynsztein@gmail.com, so I can try it out on your instance myself and see if I can find anything weird.