Commit 226709e
committed
ACPT-1599: Fixing DeploymentConfig resets & reloads every time new key that wasn't previously set
Fixing problem ACP2E-2198.
```
[Progress: 861 / 864]
Disabling Maintenance Mode:
In ResourceConnection.php line 162:
[DomainException]
Connection "default" is not defined
```
The root cause of problem is that the `Disabling Maintenance Mode` part of the install uses the first created DeploymentConfig object created in the process, which doesn't get updated, while before that runs, different part of the install that writes to the config is using the second DeploymentConfig object that was created by Laminas ServiceManager. The reason why this happens is because Intercepters use ObjectManager::getInstance to get the ObjectManager to find PluginList. This causes the plugins to use the first DeploymentConfig object which was created for the first ObjectManager. Other objects that use ObjectManager::getInstance may have this problem as well.
This commit adds a workaround in main loop of Installer that calls DeploymentConfig::resetData() on the original DeploymentConfig.1 parent 3e03cf2 commit 226709e
1 file changed
+16
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
12 | 12 | | |
13 | 13 | | |
14 | 14 | | |
| 15 | + | |
15 | 16 | | |
16 | 17 | | |
17 | 18 | | |
18 | 19 | | |
| 20 | + | |
19 | 21 | | |
20 | 22 | | |
21 | 23 | | |
| |||
175 | 177 | | |
176 | 178 | | |
177 | 179 | | |
178 | | - | |
| 180 | + | |
179 | 181 | | |
180 | 182 | | |
181 | 183 | | |
| 184 | + | |
| 185 | + | |
| 186 | + | |
| 187 | + | |
| 188 | + | |
182 | 189 | | |
183 | 190 | | |
184 | 191 | | |
| |||
327 | 334 | | |
328 | 335 | | |
329 | 336 | | |
| 337 | + | |
| 338 | + | |
| 339 | + | |
| 340 | + | |
| 341 | + | |
330 | 342 | | |
331 | 343 | | |
332 | 344 | | |
| |||
381 | 393 | | |
382 | 394 | | |
383 | 395 | | |
| 396 | + | |
| 397 | + | |
| 398 | + | |
384 | 399 | | |
385 | 400 | | |
386 | 401 | | |
| |||
0 commit comments