Widescreen package
-
I have a few questions regarding the widescreen package. Running it on a full 2.0 install.
1. Is there a way to modify how many columns show up on the dashboard? I would just like to have 3 columns and them be wider than the standard width (multiple interfaces and would like to view the info without scrolling over)
2. Where is the file location for the dashboard? -
Found my answers though I would like to go about it a different way. The auto-settings for figuring how many columns is a nice calculator, but it would be nice to have a selector at the top of the dashboard for how many columns you would like.
/usr/local/www/index.php
var numofcols = parseInt(currwidth/500); // one column is minimum 350px
-
I installed this package some time ago and found a bug that made some menu items (diagnostics -> limiter was very popular) disappear. Would be great to have this fixed for the future… furthermore an options dialog could be added to define more than 2 rows.
-
Yeah, didn't even notice it until now. Thanks for noticing it Plexus. Here is a list of each. One without the widescreen, the other with. The menu is missing more than that.
-
Does anyone know where the menu database is kept so I can add back the stuff that is missing from the menus?
-
Looks like they never bother to see if the pkg was compatible with the new menu in 2.0
Thats the old 1.2.3 menu.
I am reverting back until this is address.
-
Does anyone know where the menu database is kept so I can add back the stuff that is missing from the menus?
So I take it, no one who has read this can tell me where the menu file is stored in the file system? I haven't had any luck in trying to find it.
-
/usr/local/www/fbegin.inc
-
THANKS JIMP!!!! :D ;D :D
-
THANKS JIMP!!!! :D ;D :D
LostInIgnorance,
Can you share how you add the missing links?
Thanks!
-
I got it.
Thanks
-
Fixed :)
I even add it phpsysinfo and it works just fine :)
-
Posted pull request to file on GitHub, hopefully they will be committed.
-
Merged, thx.
-
I've had a similar problem which I was discussing here: http://forum.pfsense.org/index.php/topic,40570.0.html in the IPv6 forums. I took a look at the original fbegin.inc and compared it to the one from the widescreen package. They seemed to be quite different so I modified the original file with the layout changes that make it work with the widescreen package. I've uploaded a copy to take a look at and hopefully someone will add it to the latest version of the widescreen package.
Edit: Sorry, the version of fbegin.inc I had didn't have the DHCPv6 Relay link in the Services menu. I've reuploaded the new version.
-
I've had a similar problem which I was discussing here: http://forum.pfsense.org/index.php/topic,40570.0.html in the IPv6 forums. I took a look at the original fbegin.inc and compared it to the one from the widescreen package. They seemed to be quite different so I modified the original file with the layout changes that make it work with the widescreen package. I've uploaded a copy to take a look at and hopefully someone will add it to the latest version of the widescreen package.
Edit: Sorry, the version of fbegin.inc I had didn't have the DHCPv6 Relay link in the Services menu. I've reuploaded the new version.
How different is it?
I only found a few links missing.
-
It's not just the missing links but the way the file is written. I believe it uses the old fbegin.inc from version 1.2.3.
There is a few changes such as in the old one a line would like like this:$firewall_menu[] = array("Aliases", "/firewall_aliases.php");
where as in the new one it would look like this:
$firewall_menu[] = array(gettext("Aliases"), "/firewall_aliases.php");
There is also this part that checks if you have the correct user privileges and displays the appropriate link
if (!isAllowedPage("system_usermanager.php*")) $system_menu[] = array(gettext("User Manager"), "/system_usermanager_passwordmg.php"); else $system_menu[] = array(gettext("User Manager"), "/system_usermanager.php");
The changes aren't that big but I believe it's always good to use the most up to date version of the files.
-
That's the difference between fbegin.inc on mainline (what will be 2.1, the "ipv6" code people are using now) and 2.0 proper.
There isn't going to be a good way to just have one file do both without a bit of hacking things up and detecting the version. -
That's the difference between fbegin.inc on mainline (what will be 2.1, the "ipv6" code people are using now) and 2.0 proper.
There isn't going to be a good way to just have one file do both without a bit of hacking things up and detecting the version.jimp,
Do you think going away from the widescreen pkg is the best solution?
I am not the type that likes to look at 1000 of lines of code to try and compare and fix them :)
-
Until the widescreen package has a workaround for 2.1, it would probably be best to not use it. That is, unless you don't actually need any of the menu items that are missing…