Pretty fooking pissed to be honest…..! Dashboard widgets STILL not working!
-
I have done a clean 2.0.3 install and can for the world NOT get the widgets from traffic graps to save settings.
I did it with the help of Widescreen package (install -> save widget settings -> uninstall) and it worked fine.
But widescreen package has been removed from the repository leaving ME with a dashboard not saving the settings….
And that pisses me of bigtime.
I wanted to install Squid, and inflated the disk in VmWare. It didnt work. I had to start all over again from scratch.
But I got so pissed that I gave up since the dashboard annoyed me so much that I reverted back to my "normal" setup.
GRRRRRRRRRR!!
-
We just did a fresh install of 2.0.3 on CF (customer machine) and cannot get the interface traffic widget to save. Hmmm.
On our office boxes it was saved by 2.0.1 and we have widescreen already on them so havent tried any changes.
2.0.3-RELEASE (i386)
built on Fri Apr 12 10:22:18 EDT 2013
FreeBSD 8.1-RELEASE-p13 4g -
Exactly and its super annoying!! Tried all thems and its the same. Tried 3 browsers and no difference!
Can we pls. get the widescreen package back so one can install it and then save settings, and then uninstall the package….? Then at least the widgets act like they should.
-
The widescreen package breaks things in other ways and had to be disabled.
The widget save issue is known on 2.0.x, and fixed on 2.1. It was a non-trivial fix and couldn't be backported to 2.0.x. If it's that big of a deal, you can always use a 2.1 snapshot.
-
Can you reinstate the widescreen package and then inform people to install, save settings on dashboard and then uninstall??
Then it works fine and is usable. And when uninstalled I dont see it breaking anything…
-
Widescreen is not coming back unless someone fixes the package.
-
DAMNIT!! :(
-
You can always host your own repo with the widescreen package in it. ;)
http://doc.pfsense.org/index.php/Creating_Your_Own_Package_RepositoryAlso you can edit the config.xml file directly which is probaby easier.
Steve
-
I like the solution. Its broken…, host your own shit....:D
I am not the only one with the problem and it needs fixing since ALL is looking at the dashboard from time to time.
Its release version and if the installation of the widescreen package can fix it, why not??
How do I get hold of the widescreen package for pfsense after its gone?
-
or use 2.1 where it's been fixed properly, which is by far the simplest solution.
Widescreen breaks more than it helps. The only reason it "fixes" this is because it overwrites base system files with its own copies that are broken in other ways but just happen to work for this one function. It's not a fix, it's a kludge that just happens to work.
-
Editing the widget section of the config file is not difficult if you don't want to run 2.1 yet.
<widgets><sequence>system_information-container:col1:show,captive_portal_status-container:col1:close,carp_status-container:col1:close,cpu_graphs-container:col1:show,gateways-container:col1:show,gmirror_status-container:col1:close,installed_packages-container:col1:close,interface_statistics-container:col1:close,openvpn-container:col1:show,interfaces-container:col2:show,ipsec-container:col2:close,load_balancer_status-container:col2:close,log-container:col2:close,picture-container:col2:close,rss-container:col2:close,services_status-container:col2:close,traffic_graphs-container:col2:show,wake_on_lan-container:col2:none</sequence> <traffic_graphs-config>WAN_graph-config:show,LAN1_graph-config:hide,LAN2_graph-config:hide,LAN3_graph-config:hide,WIFI1_graph-config:hide,WAN2_graph-config:show,LAN4_graph-config:hide,WANMODEM_graph-config:hide,WIFI2_graph-config:hide,refreshInterval=5</traffic_graphs-config></widgets>Steve
-
Thanks Stephen! What does it do??
-
I want graphs open for WAN and WAN2 on my dashboard when I open the page. If you look at the traffic graph widget line you can configure which ones are open by setting show or hide.
Backup the config.xml file. Edit the widget line. Restore the file.
??, Profit! ;DI guess you could also configure what order the graphs are in and where the widgets are on the dashboard but I've never tried that.
Steve
Edit: Actually I think you can edit the config.xml file on the machine and then force it to reload the config by making some change somewhere else. Never tried that either though. ;)
Edit2: Yes you can edit the file directly, no you can't change the order of the traffic graphs.
-
:D Thanks!
-
My widget sectiuon looks like this.
Only LAN and WAN are open. Rest is closed and stays closed no matter what…
<widgets><sequence>system_information-container:col1:show,gateways-container:col1:show,interfaces-container:col1:show,captive_portal_status-container:col1:close,carp_status-container:col1:close,cpu_graphs-container:col1:close,gmirror_status-container:col1:close,installed_packages-container:col1:show,interface_statistics-container:col1:show,ipsec-container:col2:close,load_balancer_status-container:col2:close,log-container:col2:close,picture-container:col2:close,rss-container:col2:close,services_status-container:col2:show,snort_alerts-container:col2:show,traffic_graphs-container:col2:show,openvpn-container:col2:none,wake_on_lan-container:col2:none</sequence>
<traffic_graphs-config>WAN_graph-config:show,LAN_graph-config:show,refreshInterval=1</traffic_graphs-config></widgets> -
And you have more interfaces than just WAN and LAN?
My own config file, at least the traffic graph section, has not altered for a long time. I would guess that the config file has not been updated since the widget became broken (2.0.2?).
Try adding the appropriate info to the traffic graphs section. You can always restore from a backup if it goes badly. ;)Steve
-
I know, but all the VLANS doesnt stay open if I try to save settings…..!
-
Hmm, well I don't know then. :-
What does your traffic graphs config section look like now? Did you force a config reload by hitting save on some random page (I used DHCP Server)?Steve
-
What do you mean??
-
After you've edited the config.xml file you must get pfSense to reload it for any changes to take effect. I did that by going to the first dhcp server settings page and, without making any changes, hitting save.
Steve
