devshop_waiting_for_install_profiles.png

In step 4 it seems there should be an auto refresh after the tasks finish... this does not happen for me.

My fIrst try gave me:

warning: array_combine(): Both parameters should have at least 1 element in /var/aegir/hostmaster-6.x-1.9/sites/example.com/modules/devshop_hosting/devshop_projects/inc/create-wizard.inc on line 584.
warning: implode(): Invalid arguments passed in /var/aegir/hostmaster-6.x-1.9/sites/example.com/modules/devshop_hosting/devshop_projects/inc/create-wizard.inc on line 589.
warning: array_combine(): Both parameters should have at least 1 element in /var/aegir/hostmaster-6.x-1.9/sites/example.com/modules/devshop_hosting/devshop_projects/inc/create-wizard.inc on line 584.
warning: implode(): Invalid arguments passed in /var/aegir/hostmaster-6.x-1.9/sites/example.com/modules/devshop_hosting/devshop_projects/inc/create-wizard.inc on line 589.
warning: array_intersect_key(): Argument #1 is not an array in /var/aegir/hostmaster-6.x-1.9/sites/example.com/modules/devshop_hosting/devshop_projects/inc/create-wizard.inc on line 596.
warning: array_combine(): Both parameters should have at least 1 element in /var/aegir/hostmaster-6.x-1.9/sites/example.com/modules/devshop_hosting/devshop_projects/inc/create-wizard.inc on line 584.
warning: implode(): Invalid arguments passed in /var/aegir/hostmaster-6.x-1.9/sites/example.com/modules/devshop_hosting/devshop_projects/inc/create-wizard.inc on line 589.

After pushing a commit to my sandbox (http://drupalcode.org/sandbox/helmo/1868292.git/commit/74b9efa3032c5696f...) the error is gone but still no refresh.

If I refresh manually it seems OK. And I see the radio buttons to select a profile.

Besides the refresh... could we also disable the 'finish' button? That makes it more obvious the user really has to wait.

CommentFileSizeAuthor
devshop_waiting_for_install_profiles.png20.29 KBhelmo

Comments

jon pugh’s picture

Title: Create wizzard stuck » Steps 2 and 4 of Create wizard should automatically refresh.
Category: bug » feature

Yes, there should be. I haven't gotten to that point yet.

I've looked into how hosting_tasks.module does it and it is pretty complex...

Haven't had the time to address it, I am going to focus on functional bugs before I take another pass at the UX of project creation.

I merged in your changes, thanks a lot, again! If you want to take this issue I would welcome it! Hostmaster's javascript is a pain to work with.

Thanks

helmo’s picture

Status: Active » Postponed

Someday... the current changes make it clear what the user should do... fine for now.

jon pugh’s picture

Category: feature » bug
Priority: Normal » Critical
Status: Postponed » Active

Ok, the time has come.

This is a 1.0 release blocker for me, I haven't looked hard enough at the javascript for sites/platforms/servers, but those node pages do reload the page if a task goes green.

Can someone try to find this code so we can get it working on these pages?

On a side note... The time it hosting_tasks to ping the server the first time is much to long... but thats for another issue.

jon pugh’s picture

Issue tags: +Release-blocker

tagging

ergonlogic’s picture

I believe the relevant functions are in:

I think we'll need to add a local task list for this to work, rather than trying to refresh the page based on the task queue block.

jon pugh’s picture

Status: Active » Fixed

I built some new ajax refreshing code. This is done!

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