When I press "Enable Replication" button and choose a checkbox "Replicaton Bind Group", fill some data, switch back to "Replication Manager", data from "Replication Bind Group" is still taken into account, when settings are saved. Settings only from one group of checkboxes should be used.
389-ds-base-1.4.0.20-20181221gitecdf6d8df.fc29.x86_64
See attached video
<img alt="Screencast_21-12-18_121612.webm" src="/389-ds-base/issue/raw/files/485eb699c6a90ae12765a4bae2232bf5734a1ae6c555dc0d19069f1f933e012d-Screencast_21-12-18_121612.webm" />
It is valid to use both, and it was by design to allow both settings. I suppose it confusing, but there is technically nothing wrong with it
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
I just realized I used 'checkbox' instead of 'radio button' in the description... Using radio buttons means that the choice is mutually exclusive. So perhaps the form should have all choices visible on the same panel?
You're right about the radio button definition. Showing both options can be confusing as well. Perhaps we need a tabbed panel? Need to think about this more...
Metadata Update from @mreynolds: - Issue assigned to mreynolds
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.0
This has been redesigned and should no longer be an issue. Fixed in master
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3167
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.