Bug #5659
closedDashboard widgets disappear and are unrecoverable if the column is blank in their configuration
100%
Description
Not sure how the column was blank in the config but at one point blank must have been assumed to be "col1" and that has since changed. If the widget has, for example, system_information::open
the system information widget will disappear. If other widgets such as IPsec suffer the same fate, they are also missing from display and the Available Widgets panel. Fixing the specification to be system_information:col1:open
will bring it back, likewise for other widgets.
Granted this particular firewall has been through a lot over changes over the years, but when the problem presented the widget config was:
<sequence>system_information::open,services_status::open,openvpn::open,undefined::close,undefined::close,undefined::close,ipsec::open,traffic_graphs::open,gateways:col2:open,interfaces:col2:open,log:col2:open,interface_statistics:col2:open,thermal_sensors:col2:open,smart_status:col2:open,[object Object]:col2:open</sequence>
Cleaning that up a bit it all worked when I changed it to this:
<sequence>system_information:col1:open,services_status:col1:open,openvpn:col1:open,ipsec:col1:open,traffic_graphs:col1:open,gateways:col2:open,interfaces:col2:open,log:col2:open,interface_statistics:col2:open,thermal_sensors:col2:open,smart_status:col2:open</sequence>
Updated by Anonymous almost 9 years ago
Added code to assign a temporary display column if that information is missing from the config.
At one time this was part of the upgrade_config script, but it looks like it was removed.
Updated by Anonymous almost 9 years ago
- Assignee changed from Anonymous to Jared Dillard
Updated by Anonymous almost 9 years ago
- Status changed from Confirmed to Feedback
- Assignee changed from Jared Dillard to Jim Pingle
Tested by deleting column information from <sequence> and rebooting. All widgets display correctly.
Updated by Anonymous almost 9 years ago
- % Done changed from 0 to 100
Applied in changeset 72eaefaf1fc991d5949daadbac5ae50ed1d3ad5f.
Updated by Jim Pingle almost 9 years ago
- Status changed from Feedback to Resolved
Looks good now.
FYI- you can test a lot easier by editing config.xml live either with viconfig, or by editing the file and then running "rm /tmp/config.cache" which forces the GUI to reload the config from disk.