Sonarr version (exact version): 2.0.0.5228
Mono version (if Sonarr is not running on Windows): 5.8.0.108
OS: Synology DSM 6.2
Debug logs: Unable to generate
Description of issue: Whenever I make a change in settings, the following error appears, and it does not appear the change is saved: Couldn’t save naming settings. Changing log level to Debug or Trace doesn’t produce any logs in /usr/local/nzbdrone/var
No setting on the naming settings page shows an error message about it?
Changing log level to Debug or Trace doesn’t produce any logs in /usr/local/nzbdrone/var
You can check the log files right in the UI. They may be in a different location on disk. ((Trace logs)) would be the most helpful here, though getting information from the browser’s developer tools (Console/Network) may be helpful as well, particularly the request to config/naming.
attempting to save settings produces the following in System > Logs > Tables
Invalid request Validation failed:
-- Produces invalid file names
Browser trace produces the following using debug tools:
backbone.js:492 Uncaught TypeError: this.sync is not a function
at child.save (backbone.js:492)
at child.saveSettings (SettingsModelBase.js:15)
at triggerEvents (backbone.js:203)
at EA.trigger (backbone.js:146)
at child._save (SettingsLayout.js:230)
at HTMLButtonElement.bound (lodash.underscore.js:665)
at HTMLDivElement.dispatch (jquery.js:4670)
at HTMLDivElement.elemData.handle (jquery.js:4338)
save @ backbone.js:492
saveSettings @ SettingsModelBase.js:15
triggerEvents @ backbone.js:203
trigger @ backbone.js:146
_save @ SettingsLayout.js:230
bound @ lodash.underscore.js:665
dispatch @ jquery.js:4670
elemData.handle @ jquery.js:4338
jquery.js:9664 PUT http://192.168.68.68:8989/api/config/naming 400 (Bad Request)
Console > Network has the following under naming:
[{propertyName: "DailyEpisodeFormat", errorMessage: "Produces invalid file names"}]
0: {propertyName: "DailyEpisodeFormat", errorMessage: "Produces invalid file names"}
The Daily Episode format is listed as
{season:00}x{episode:00}
Changing that to something else doesn’t make the error go away
Something in your naming settings is invalid, the UI should indicate where the issue lies, if it’s with multi-episode format you may need to tweak the format or the multi-episode style.
Just updated the post - sorry. I caught that right as I posted.
That format looks fine and I tested it in 2.0.0.5228 successfully.
Not sure what it could be.
oh well - I’m feeling lucky, and switched to the develop branch. Issue solved.
Thanks anyway 
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.