Item12606: Configure does not track local pending changes.

The issue is that the N pending changes button is rendered by the server side. It requires a post of the configuration form to update the button.

The initial "solution" since reverted due to performance concerns was to post the config form on each changed field, resulting in significant server I/O, possibly 100K per change.

The button needs to be updated with javascript, and the client code needs to better track changed fields. A possible compromise would be to update the button on any change to state "pending changes" without a count. Clicking the button sends the changes to the server for validation, and updates the button.

-- GeorgeClark - 18 Oct 2013

This is not going to get fixed with the current configure; it is just far too complex.

I'm treating this as a sub-problem of Item12605 and marking it as a duplicate, as it's part of the same problem.

-- CrawfordCurrie - 25 Apr 2014

Commenting is disabled while not logged in