BOUNTY: Web GUI reprogramming
-
Some warnings during install, but it worked perfectly.
And no cosmetic errors.
-
nice saved me some work ;)
~~Sorry guys been really busy recently. Just finished a project I was working on so will try and get a PR of this into 2.2 as 2.1.1 seems to be released (at least my box is telling me an update is available for the last few days).
I can submit a PR but I don't know whether it will be accepted. Its been in master for ages but I think that will become pfsense 3, which I guess is a loooonnngggg way off~~
Edit master branch is 2.2 so shouldn't be too long until its ready. Its already live in the the 2.2 snapshots! - https://forum.pfsense.org/index.php?topic=74154.15
-
Some warnings during install, but it worked perfectly.
Yes, you are right.
Turns out:
-
I could check for "pfsense_ng_fs" theme folder before patching, and remove it, but that would assumes nobody modified the theme after the patch and could lead to unwanted data loss.
-
I could check for existance of backup'd "index.php.orig", diff and count diff'd lines, and if 0 erase the backup file, but it would assumes, again, that "index.php" file didn't change during update.
As assumptions are bad, I suggest people who don't fully understand the patch should go through the revert part of the README before upgrading pfSense and launching the patch again.
If you already applied the patch and already upgraded to let's say pfSense 2.1.1 or 2.1.2, then just patch index.php file and remove pfsense_ng folder inside /usr/local/www/themes/pfsense_ng_fs folder, i.e. /usr/local/www/themes/pfsense_ng_fs/pfsense_ng
Sorry for that, I should spend more time understanding the subtilities of cp CLI and / :-)
-
-
Could I ask my by now famous noob questions?
On my second pfSense, I did not have the wide gui before (I do have it on my first pfSense which is still on 2.1). On my second pfSense, I am on 2.1.2 already (due to a problem with my quad nic I upgraded). What would be the procedure to get the widescreen on this 2.1.2? Install the last one from Charlie (the link above) and then the patch from Justincase? Or something else?
Thank you for your answer ;D
-
@Hollander
This patch will modify some files to implement previous solutions by @jimp and @charlie0440:
https://github.com/melomac/widescreen_fsNo need to do anything else than following patch instructions.
-
how do I get or install the bootstrap themed one?
It looks great….. -
Works great, thanks for the contribution!
-
I ask myself, if Kelsen is continuing his work on the metrolab-like theme. I'd really like to have a new fresh approach with a side menu and a possible fluid/responsive layout that could work on mobile devices, too. Sometimes, a mobile phone or tablet is all you have with you and when the s… hits the fan and you can just check your FW remote it just makes the difference.
-
Hi, Unfortunately I abandoned this project due to lack of time, my last attempt to change the theme resulted in the screenshot below, with my customizations.
It's a accordion effect using css3, there are no code customization besides the login page.
-
@kelsen: To me this is looking very promising and nice. Would be a shame to abandon that theme now. Me thinks it only needs some polish (and perhaps other colors ;) ) but otherwise, this would seem like a very decent approach for widescreen monitors.
-
Is anybody running a working widescreen on 2.1.4??
I need this since I am upgrading to 2.1.x to get the latest Snort and I love my 2.0.3 widescreen….
-
Anybody aware if this works in 2.1.4???
-
this patch:
https://github.com/melomac/widescreen_fsworks fine on pfSense 2.1.5 RELEASE
-
Hi, Unfortunately I abandoned this project due to lack of time, my last attempt to change the theme resulted in the screenshot below, with my customizations.
It's a accordion effect using css3, there are no code customization besides the login page.Hello Kelsen,
Any update on this theme? It is awsome
-
Hi techguy,
I'm not working anymore on this theme, but if I remember well I've done a package or at least I can upload the files If u want to try. I'll update this post with the link probably tomorrow.