| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
1) For the translators, it should be better to do it consistently. Then
they only need to have 1 translation of "You must apply the changes in
order for them to take effect" and can translate each of the other
custom sentences individually.
2) The full-stop should always go at the end of the sentence, inside the
gettext(). There are some languages where the full-stop is not the same
as European. e.g. In Nepal we use the vertical bar for end of sentence.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) Get rid of the stristr() checks to "guess" if an apply button should
be used.
2) Change print_info_box() so it can take a button name of "close"
, "apply" or none to decide which button to show.
3) Delete function print_info_box_np_undo() - nothing calls it.
4) Add new function print_apply_box() to provide an easy wrapper for
print_info_box() with the parameters to be 'warning' level and 'apply'
button.
5) Change print_info_box_np() calls to just print_info_box() or
print_apply_box() as appropriate.
There is 1 direct call to print_info_box_np() from vpn_ipsec_mobile.php
remaining. That tries to make a "create" button. It was not working
before this change. It needs to be sorted out and fixed separately.
After this change there is no dependency on a string containing text
like "apply" to make the apply button appear.
Then we can work on re-engineering the internal code of
print_info_box_np() print_info_box() and print_apply_box() to fit
together however we like. It should be easy to preserving the current
API to print_info_box() and print_apply_box().
|
|
|
|
| |
Removed long commented out script
|
| |
|
|
|
|
|
|
|
|
|
| |
There are 3 sets of info. But when I put each in an infoblock then:
1) Only the first "i" icon works to open and close, and it opens and closes all 3 blocks of text.
2) The first 2 text boxes still have an "x" and they can be dismissed.
Do we want to enhance the supporting code for infoblock so that it can work with multiple infoblocks on the same page?
Or do we have a policy that there is only to be 1 infoblock on a page, and other 'info' text just has to not be in an infoblock?
|
| |
|
| |
|
|
|
|
| |
Remove unused variable $closehead
|
| |
|
|
|
|
| |
was the reason they were added, it was never finished and it's not being used
|
| |
|
| |
|
|\
| |
| |
| | |
NOYB/Services-DNS_Forwarder-Host_Overrides-Case_Sensitivity
|
| |
| |
| |
| | |
Host and domain names are not case sensitive. Maintain display case as entered.
|
|/
|
|
| |
are all pages and the "WebCfg" prefix implies they are pages.
|
| |
|
| |
|
|
|
|
|
| |
Any GUI script that loads the guiconfig.inc file will have access to
the autoloader.
|
| |
|
| |
|
|
|
|
| |
Mote: New ticket will be opened to provide IP address sorting
|
|
|
|
|
|
| |
- Remove personal copyright from people who assigned it to employer (ESF)
- Remove $Id$
- Remove extra spaces
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
'X' button suppressed in info text box
|
| |
|
| |
|
| |
|
|
|