[feladat @ 84]
Bugfix. The function zone_count() now also counts zones an owner has
only partial access to, not just those zones the owner has full access
to. This fixes just the count, the zones a user has partial access to
are not (yet!) shown in the "list zones" page.
Bugfix. In the zone listing the "edit" button is now show for users
with access level 1. Untill now they were presented an overview of the
zones they could change, but there was no link for them to actually
edit the zone.
Bugfix. Some of the buttons in the "edit zone" interface that are of
no use to a user with access level 1 have been hidden.
Bugfix. Make sure a user with access level 1 with only partial access
to a zone cannot add new records to that zone. Only the zone owner
should be able to add new record.
Bugfix. If a user with access level 1 edits a record in a zone he has
only partial access to, an error was shown because of call to a non-
existing function in the PEAR:MDB2. This bug was most likely
introduced while migrating from PEAR:DB to PEAR:MDB2.
Bugfix. A user with access level 1 was able to delete all records of a
zone he has only partial access to. Some additional checks have been
added.
Bugfix. If a user with accees level 1 has partial access to one or
more zones starting with a certain character, but did not own at least
one entire zone starting with the same character, the character wasn't
clickable in the "list zone" page.
Interface. If no record or zone id is given for delete_record.php or
delete_domain.php, don't just die but echo a nice message. The i18n
files have not yet been updated to reflect this change.
Interface. If no master IP is given in delete_supermaster.php, don't
just die but echo a nice message. The i18n files have not yet been
updated to reflect this change.
[All fixes by Peter Beernink.]
README.i18n
Using a translation
-----------------------------------------------------------------------
All available translations can be found in the locale directory in the
poweradmin base directory. The Dutch translation for example, can be
found in locale/nl_NL. To review the status of the translation, you
can have a look at the nl.po file in the LC_MESSAGE directory.
If you want to use a translation, say the nl_NL, all you have to do is
edit inc/i18n.php file and change the $language variable to the desired
language, for example "nl_NL".
If this doesn't work, please try to do the following:
- cd /path/to/poweradmin/locale/$lang/LC_MESSAGES/
- msgfmt $lang.po -o message.mo
If that doesn't help either, most likely your system itself is not
setup properly. See <https://rejo.zenger.nl/misc/1176630442.php> maybe
of some help.
Adding a new translation
-----------------------------------------------------------------------
If you want to create a new translation you can do the following. For
example, if you want to create a Dutch translation:
- cd /path/to/poweradmin/
- mkdir -p locale/nl_NL/LC_MESSAGES/
- cp docs/template.pot locale/nl_NL/LC_MESSAGES/nl.po
- cd locale/nl_NL/LC_MESSAGES/
- vim nl.po
- msgfmt nl.po -o message.mo
Updating the translation template file
-----------------------------------------------------------------------
If creating a new translation and you are not sure if the template file
that was provided in the distribution, you may want to re-create the
template file. To do so, do the following:
- cd /path/to/poweradmin/
- xgettext --no-wrap -o docs/template.pot *.php inc/*.php
The last command updates the template file in docs/ directory.