Overview of merged pull requests¶
When configuring the PdoBackend to use an SQLite database it will be set up automatically upon connection.
Invoking the cache:setup command afterwards leads to an error:
General error: 1 table “cache” already exists
With this fix, the creation of cache tables is skipped for SQLite databases during setup.
This fix makes sure resource:clean will remove broken resources from the right collection.
The problem is that you save the SHA1 for a broken resource. Now think about the following case: You have two resources with the same SHA1, but from two different collections (persistent/temporary). The resource inside the temporary-Collection was removed and now you run the command.
It will detect the missing resource from the temporary-Collection and add the SHA1 to $brokenResources. Now when iteration over $brokenResources to get the PersistentResource you are using $this->resourceRepository->findOneBySha1($resourceSha1), which ignores the collection. So you can’t be sure to get the PersistentResource from the temporary-Collection that you actually want, it’s possible that you get the one from the persistent-Collection. This would result in deleting the wrong PersistentResource and not removing the broken resource but creating a new problem.
The fix just saves the identifier of the PersistentResource to $brokenResources and later detects the correct one agin by using $this->resourceRepository->findByIdentifier($resourceIdentifier).
` BUGFIX: Replacing suffixes appends, if nothing to replace <https://github.com/neos/flow-development-collection/pull/1741>`_¶
The UriConstraints behaves weird with replaceSuffixes on hosts: if the suffix to replace is not found, the replacement is appended to the host - instead of nothing happening.
In order to make https://github.com/neos/flow-development-collection/pull/1586 more approachable without actually setting a default value in Development.
Adds missing documentation that it is required to rename
Settings.yaml.example in order to
have working routing and see the “Welcome” page.
Thanks M.B. from our forum for bringing it up again.