Problem/Motivation
Hi team,
I am trying to connect using acquia connector, using my email creds.
Steps to reproduce
- Go to admin/config/system/acquia-connector/setup
- Enter Acquia Subscription email address and password on step1
- Selecting the subscription in step 2
- I see an error in step 3, and do not see the page.
The error is
Fatal error: Cannot use object of type Drupal\acquia_connector\Helper\Storage as array in docroot/modules/contrib/acquia_connector/src/Form/SetupForm.php on line 196
Version of module - 8.x-1.12
Core - 8.3.4
Proposed resolution
Do not re-use the same variable for both the Form State data array and the Storage class object during form submission.
Remaining tasks
- Add some tests around the Set-up form that will surface any uncaught exceptions like this in future
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | acquia_connector-setup_form_error-2892891-9.patch | 1.42 KB | chop |
Comments
Comment #2
danepowell commentedI'm also seeing this issue with 8.x-1.12, core 8.3.5
Comment #3
danepowell commentedBumping priority, since it's impossible to use the module if we can't connect it to a subscription.
Comment #4
irek02 commentedI created an internal Acquia ticket to address this issue.
Comment #5
stevenlafl commentedI am seeing this as well.
Comment #6
arosboro commentedIt's possible to connect if you get the error and then go to manual configuration
Comment #7
chop commentedI've just hit this and am rolling a patch. It's all here
docroot/modules/contrib/acquia_connector/src/Form/SetupForm.php
at line 187:
but at line 196:
I'm sticking in a breakpoint to find the correct object property to check and rolling a patch now.
Comment #8
chop commentedupdating title and refining summary
Comment #9
chop commentedThis patch makes two changes to the
\Drupal\acquia_connector\Form\SetupForm::submitForm()method:\Drupal\acquia_connector\Helper\Storageobject.$form_stateto the\Drupal\Core\Form\FormStateInterface::getErrors()method, as this method does not accept any parameters.Comment #10
chop commentedI've lodged a support ticket with Acquia, and pointed them to this issue and patch for review.
Comment #11
chop commentedComment #12
adammaloneSimple patch, applies cleanly against 8.x-1.x HEAD and fixes the issue raised.
Comment #13
chop commentedWe've now tested this against 3 separate Acquia Subscriptions, all with the same results.
The patch applied fixes the issue. The issue however is not found in the older 8.x-1.10 version of Acquia Connector. Currently I can reproduce on 8.x-1.12 and 8.x-1.x-dev.
Comment #15
irek02 commentedThe patch made it into the latest release of Acquia Connector. chOP and everyone else, thank you very much!