With the recent changes to the left panel sizing for changesets (i.e. to use 1 column), the format of the right edit pane runs together a bit. This commit is to change some of the grid usage to take advantage of the increased size of the right pane. In a future commit, we'll address the sizing of the jeditable text field and area; however, wanted to get this initial change in.
…ion when one is not assigned or being selected
…ng synced during changeset promotion
The login/logout notices were being generated, but not displayed. This was used to the flash.now which expects the notice to be displayed immediately as part of the same request; however, these actions are both redirects, so notice should be displayed on next request. In order to address this, removed the '.now'. In additional, removed the check to see if the response is for an ajax request. This is not really necessary, since we are ultimately handling the notices the same for all cases, except redirects which we want to display on next request.
Removing the UserSessions::invalid from the invalid login attempt flow. Prior to this change, the flow was similar to: POST user_session -> redirect_to invalid_session_url -> redirect_to new_user_session_url After this change, the flow is: POST user_session -> redirect_to new_user_session_url This removes the additional redirect in the middle of the flow. This change also moves the flash/notice to the failed auth controller and uses flash direct vs AppController::errors. Since this controller does not inherit from AppController (and it should not), it cannot use that method. That is not, however, a problem since we simply want to display a notice and not persist it.
…ame for different products now. product's candlepin id (cp_id) is now being prepended to content label specified by the client.
… was not specified
These actions were removed from the former 3-level reoute under environments, index & create remain the same.
While working on subscription file upload, observed a js error in notices. The issue being encountered is that we were looking for notices details in the file upload response; however, since that request is not a true ajax request, there was no detail to be retrieved. That said, notices was not checking to see if the variable was defined before using it.
This commit addresses the issue where after a subscription upload via the UI (successful or unsuccessful) the spinners continue after the action has completed. This is an issue of the ajaxComplete not being triggered after the action and may be related to file uploads not truely being treated as ajax requests. In order to address this, we are going to trigger ajaxComplete manually. This commit also addresses an issue where on subscription upload error where we would attempt to render the subscriptions partial without valid data causing an ugly haml error to be shown. In order to address this, we are purposely rendering "nothing", so that the user may select a different manifest, if desired, for upload.
Fixing an error in the distributions partial that was causing incorrect behavior when there are multiple distributions in the list... Prior to this change, selecting one of the distros would highlight all vs just the desired one.
it now only breaks the current command and prints a message.