I'm having an issue with Users/Admins saving updates to their Account Settings.
Whenever we click the Update Settings button we get the following error:
"Default theme not specified."
This happens on both User & Admin accounts. I can successfully save changes when I access the account through Manage Users in the Admin tab.
Can't Update Account Settings - Default theme not specified
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Can't Update Account Settings - Default theme not specif
What version of fusion are you running?
As far as I can tell this string isn't anywhere in the 2014 fusion.
As far as I can tell this string isn't anywhere in the 2014 fusion.
Re: Can't Update Account Settings - Default theme not specif
I'm running version 2014R1.0
Any thoughts?
Any thoughts?
Re: Can't Update Account Settings - Default theme not specif
I think I may have identified the issue.
In /usr/local/nagiosfusion/html/account/main.php
Its checking for a default theme value in this code:
If I comment out these lines, it saves fine.
Can you verify if this is a bug or something unique to my installation?
In /usr/local/nagiosfusion/html/account/main.php
Its checking for a default theme value in this code:
Code: Select all
if(have_value($default_theme)==false)
$errmsg[$errors++]=$lstr['BlankDefaultThemeError'];Can you verify if this is a bug or something unique to my installation?
Re: Can't Update Account Settings - Default theme not specif
Go to Admin -> Manage System Config, then for the "XI User Interface Theme" select "XI 2014" even if it is already selected, then click Update Settings.
Then try to update your individual user settings.
There was an identical line in my Fusion system but in another file that was commented out, so it might have just been missed there, although I cannot reproduce the behavior.
Then try to update your individual user settings.
There was an identical line in my Fusion system but in another file that was commented out, so it might have just been missed there, although I cannot reproduce the behavior.
Former Nagios employee