This should do it: https://github.com/pfsense/pfsense/pull/2186

Note that the code also needs some limit on the number of rows that can be added - there is a maximum of 10 time servers saved. So the Add button should be hidden once there are 10 rows shown.

WFM. (How well it counts, no idea, I don't keep track of these things, nothing widely off track…)

WFM ;)

'pkg info' shows the versions. Everything's up to date for the appropriate port. Like rrdtool is rrdtool12 port because newer than that adds absurd dependencies that aren't easily removable and there's no reason to go newer.

Just to be clear, my screenshot is something I modified to add the pfSense Red colour to the widget banners and Status: Dashboard.  I didn't do it to the Service Status & OpenVPN widgets, and they look drab and kind of wash together compared to the others.

console 13 just dumps back to console

pkg update -f

does fix it but might be more than the avg user would have realized

Thanks. It was just a label problem, but is now fixed.

@JeGr:

@NOYB Perhaps the menu or widget width should be enlarged by 1px instead of reducing even boundaries like (1200)?

max 1199 sets the boundary at 1200.  So transition happens at 1200 instead of at 1201.

@awebster:

I agree, the language should be clear: "check to enable".
There are numerous instances where the text is confusing because of a negation (not) or an exception (unless).

Yeah, I think part of the problem is that the guys coding don't have the same POV as the users, not blaming them, just a fact.

What I see in pfSense is some logic flaws in the text, the description fits the effect on the code behind the UI, but not what the user understands.

@awebster:

Keeping in mind that pfSense is used all over the world, and while a multilingual GUI would be cool, requires a huge translation effort; to date only Turkish and Portuguese (Brazil) appear as choices.  In the interim, simple direct english would be an asset, and it would make the translation effort that much easier for the people tackling the job.

The other part of the problems comes from how the translation is done. You have to install Github, fork the main branch, clone to your local disk, usr xgetext or in my case Poedit to correctly edit, generate the translation and compile it, then commit, do a pull request, sign the CLA. Some people might want to do the translation, but don't want to go through all these steps.

pfSense doesn't have a huge amount of text in it's UI, the PTBR translation I'm revising now will take probably a week to do… alone.

php full VERSION

http://www.apachelounge.com/viewtopic.php?t=6359

pfSense-memstick-2.3-ALPHA-amd64-20151203-1920.img.gz

pf2333_1.jpg
pf2333_1.jpg_thumb
pf2334_2.jpg
pf2334_2.jpg_thumb

@cmb:

So you went through the exact same process as me. :) "Hm, that looks easy" …to... "sheesh, wtf, screw this."

I just removed it from the front end.

Well yes… and - frankly, the entire code would benefit from complete rewrite. WTH was it done like this? (Not to mention, the config variable naming which made me waste about half an hour wondering where's actually the unbound part of the code that parses the DHCP configuration.)

looks better thanks

Well, there's some discussion in here regarding this: https://github.com/pfsense/pfsense/pull/2150

Changing to a drop-down or some other control type would be a ton of work and probably more confusing. At most I'd say the color/format of the buttons may change, and the format of the headers in between.

As for localization, the text in the package is already either run through bootstrap when building the controls or gettext directly, something should be able to extract it and do whatever is needed with it already.

@xbipin:

there still seems to be an issue with alias where there is FQDN used and no description so the firewall inserts a default description of entry added with date and time and when u mouse over this, the popup width isnt adjusted and things look weird and text overflows

I'll fix the overflow issue, but the default description was behavior that I believe was already happening so that should be a different request if it isn't desired.

edit: this overflow issue is fixed now.

Thanks JimP