Bug #4409
closed
Submit button for Architecture creation doesn't close the form nor does it display the new architecture in the list
Description
Using the web ui to create a new architecture I noticed that the submit button does not give any indication that the record was created (the architecture does get created)... you have to reload the page in order to see the new record. The form doesn't close either, which is confusing to the user. Clicking the Submit button again tells me the name I chose has already been taken but the record is not listed.
Steps:
- Create a new architecture via the UI. Select a valid OS
- Click the Submit button
The attached screenshot shows that the form is still open and that the new record is not listed in the list to the left of the UI.
Files
| Screen Shot 2014-02-20 at 5.56.35 PM.png | View Screen Shot 2014-02-20 at 5.56.35 PM.png | 63.4 KB | Form is not closed after clicking Submit | ||
| Screen Shot 2014-02-20 at 5.57.27 PM.png | View Screen Shot 2014-02-20 at 5.57.27 PM.png | 58.5 KB | Name is already taken |
Updated by Ohad Levy over 11 years ago
- Project changed from Foreman to Katello
- Category deleted (
Web Interface)
I can't reproduce it with Core foreman, just when Katello is installed.
Do you see any JS errors?
Updated by Og Maciel over 11 years ago
I did not see any javascript errors. All requests and responses look normal.
Updated by Mike McCune over 11 years ago
FYI, same thing happens for me with users and not just Architectures.
Try to create a user, hit Submit and nothing happens in the UI. If you refresh the Users list it shows the newly created user.
Updated by Ohad Levy over 11 years ago
- Related to Bug #4490: Roles UI page messes up after scrolling added
Updated by Mike McCune over 11 years ago
- Category set to Web UI
- Assignee set to Brad Buckingham
Updated by Brad Buckingham over 11 years ago
Made changes in Katello (https://github.com/Katello/katello/pull/3769) which allow the Foreman two-pane to work properly. It looks like the 'id' that Katello was using for the Content menu was interfering with Foreman. The id used was 'content'.
Updated by Brad Buckingham over 11 years ago
It looks like the source of the conflict is that Foreman two-pane uses #content, which conflicted with the plugin using the same id in the menu.
E.g.
./two-pane.js:46: $('#content').html(response.responseText);
./two-pane.js:66: $('#content').html(response.responseText);
./two-pane.js:109: var form_content = $("#content form.well", response);
./two-pane.js:117: $('#content').replaceWith($("#content", response));
Updated by Brad Buckingham over 11 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset katello|commit:63afa801936cff8db1c6b0db7310aaf75046e3ef.
Updated by Eric Helms almost 11 years ago
- Translation missing: en.field_release set to 13