freeipa/install
Petr Vobornik 9c4b004076 Fixed inconsistency in enabling delete buttons
https://fedorahosted.org/freeipa/ticket/1640

On the HBAC Rules page, where the rules are listed, if no rule is selected, the "Delete" button is not enabled, and cannot be clicked on.
But edit a Rule, and Delete button is enabled in the available sections - regardless of, if an object is selected to be deleted or not, or even if there is no object to be selected to delete.

One can click on this button...but then - there is no message indicating that something should be selected for deletion for this button to do anything.

Notes:
 * fixed association_table_widget and association_facet
2011-09-09 22:43:19 +00:00
..
conf enable proxy for dogtag 2011-08-29 17:54:49 -04:00
html Fixed browser configuration pages 2011-08-17 17:28:25 +00:00
migration Fixed broken links in ipa_error.css and ipa_migration.css. 2011-08-11 13:38:36 +00:00
po ticket 1669 - improve i18n docstring extraction 2011-08-24 23:13:16 -04:00
share Let Bind track data changes 2011-08-31 16:46:12 +02:00
tools Fix permissions in installers 2011-09-07 13:02:43 +02:00
ui Fixed inconsistency in enabling delete buttons 2011-09-09 22:43:19 +00:00
updates Add additional pam ftp services to HBAC, and a ftp HBAC service group 2011-08-24 15:21:41 -04:00
configure.ac ticket 1650 - compute accurate translation statistics 2011-08-18 14:25:58 +02:00
Makefile.am rename static to ui 2011-01-20 14:12:47 +00:00
README.schema Add some basic rules for adding new schema 2010-08-27 13:40:37 -04:00

Ground rules on adding new schema

Brand new schema, particularly when written specifically for IPA, should be
added in share/*.ldif. Any new files need to be explicitly loaded in
ipaserver/install/dsinstance.py. These simply get copied directly into
the new instance schema directory.

Existing schema (e.g. in an LDAP draft) may either be added as a separate
ldif in share or as an update in the updates directory. The advantage of
adding the schema as an update is if 389-ds ever adds the schema then the
installation won't fail due to existing schema failing to load during
bootstrap.

If the new schema requires a new container then this should be added
to install/bootstrap-template.ldif.