When migrating an entire platform the submit button in the pop up with the sites does not appear to actually do anything, even though it actually submits the form.

Probably should at least close the pop up to signal that the action has been recieved?

Comments

SimmeLj’s picture

Oh, and it's actually on alpha13, couldn't choose it in the dropdown for some reason, it wasn't there.

adrian’s picture

it closes and reloads the page on my local dev copy.

Anonymous’s picture

Status: Active » Postponed (maintainer needs more info)

It works for me too on Google Chrome. What browser are you using?

omega8cc’s picture

That happens with Safari, even with Safari 5 on Leopard (not Snow). It just hangs and looks like the web server is very busy etc. but this is JavaScript hanging, imo. I have to close the window and open the URL again, and sometimes I have to close Safari and start it again to pass those "locked" JS state (it can lock also on the tasks block AJAX refresh - spinning wheel never stops).

An today I got another (but not sure if related) report about non-active (greyed out) submit button on create site form in Safari 3, while in FF it works for the same user.

3rdLOF’s picture

Adding to this the submit button in the Site creation form in Safari 4.0.5. It remains grayed out and unresponsive. JS debugger spits out this error on that page:

hosting_site.form.js: Line 64

TypeError: Result of expression '$(input_id).parent().text().trim' [undefined] is not a function.

Not sure how this affects the button.

Using alpha14 install from yesterday.

I also noticed that in this form the Client auto-fill field for the email reveals a bit of the ajax progress wheel. This, by all means, unimportant as functionality is not affected. A layout thing.

SimmeLj’s picture

Sorry for responding a year later to this, totally forgot about it, the mail I used on Drupal.org got borked (thanks Google Apps).

Anyhow, it became very apparent today that this is still an issue, and I know have a much better understanding of the underlying problem. I'm managing an Ægir instance which is currently hosting 865 sites on one of the platforms. And it goes without saying that responding to the AJAX request that's made when pressing the final submit button in the migration process, takes time when 865 migration tasks has to be created. This is _scary_ when it takes 20 minutes for the page to respond without any feedback.

If the submit button brought the user to a batch page or something instead it'd be awesome. Or at least showing a spinner and disabling the submitbutton.

We are currently on RC1, so I do not know if this is fixed in 1.4. If so feel free to close this issue.

steven jones’s picture

Version: 6.x-0.4-alpha3 » 6.x-1.5
Status: Postponed (maintainer needs more info) » Patch (to be ported)

Fixed in f544c0d0b93a917de0ebfd19ea11f41ca212fb17 in 6.x-2.x, using batch API for the submission of the form additionally. Will test and backport.

steven jones’s picture

Status: Patch (to be ported) » Fixed

Tested and backported.

Status: Fixed » Closed (fixed)
Issue tags: -submit, -form, -migration

Automatically closed -- issue fixed for 2 weeks with no activity.

  • Commit f544c0d on 6.x-2.x, dev-ssl-ip-allocation-refactor, dev-1205458-move_sites_out_of_platforms, 7.x-3.x, dev-588728-views-integration, dev-1403208-new_roles, dev-helmo-3.x by Steven Jones:
    Issue #913228 by Steven Jones: Fixed Unresponssive submit button in...

  • Commit f544c0d on 6.x-2.x, dev-ssl-ip-allocation-refactor, dev-1205458-move_sites_out_of_platforms, 7.x-3.x, dev-588728-views-integration, dev-1403208-new_roles, dev-helmo-3.x by Steven Jones:
    Issue #913228 by Steven Jones: Fixed Unresponssive submit button in...