Closed (cannot reproduce)
Project:
Acquia Connector
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
9 Nov 2017 at 14:30 UTC
Updated:
21 Apr 2020 at 13:55 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
nikunjkotechaUsing variable in State to check if read_only status was set through code and conditions are met now, we unset read_only flag.
Comment #3
nikunjkotechaComment #5
nikunjkotechaWrong sequence of branches while creating patch :(
Corrected now
Comment #6
nikunjkotechaDidn't work :(
Comment #7
nikunjkotechaTrying again.
Comment #9
nikunjkotechaVerified with livedev on Cloud, should work now.
Comment #11
danepowell commentedIs this still an issue? If so can you please provide steps to reproduce? I'm not sure what's meant by a "fresh install" here. Normally when you enable Acquia Connector and Acquia Search for the first time they should automatically connect to the appropriate search core.
Comment #12
danepowell commentedClosing after a week of inactivity, per the contribution guidelines. Feel free to reopen if you can provide the requested information. Cheers.
Comment #13
nikunjkotecha@Dane: This would need testing in specific conditions, I reported for a project which uses ACSF and custom profile.
I would need to revert the patch and test on some environment with Acquia Cloud connectivity which is not possible for me now and this also requires custom code to be present, so I don't think it is straight forward
Steps:
* Add a custom module which uses acquia_search and adds an Index (config/install) which uses acquia_search.
* Install a new site on Acquia Cloud (ACSF) with a profile that enables the module during installation (using ACSF interface)
* Observe the Index status after site is installed
Comment #14
nikunjkotechaComment #15
danepowell commentedI still cannot reproduce this. If you are able to provide a failing test case feel free to reopen!
Comment #16
sanket1007 commented