neosflow
(Markus Romainczyk)
September 22, 2016, 1:32pm
1
Settings.TYPO3.Flow.object.excludeClasses -> This property is not allowed here, check the spelling if you think it belongs here.
Settings.TYPO3.Flow.security.authentication.providers.Typo3SetupProvider.requestPatterns.controllerObjectName -> expected: type=dictionary, null found: type=string
Settings.TYPO3.Flow.security.authentication.providers.Typo3BackendProvider.requestPatterns.Flowpack\Neos\FrontendLogin\Security\NeosRequestPattern -> expected: type=dictionary, null found: type=string
Settings.TYPO3.Flow.security.authentication.providers.Flowpack.Neos.FrontendLogin:Frontend.requestPatterns.Flowpack\Neos\FrontendLogin\Security\NeosRequestPattern -> expected: type=dictionary, null found: type=string
olibur
(Oliver Burkhalter)
September 23, 2016, 8:48am
2
I think this post is about the same issue:
Hi,
I allways got one error (the last in the following list)
in Backend/Configuration/Settings
Now there are 4:
Settings.TYPO3.Flow.security.authentication.providers.Typo3SetupProvider.requestPatterns.controllerObjectName -> expected: type=dictionary, null found: type=string
Settings.TYPO3.Flow.security.authentication.providers.Typo3BackendProvider.requestPatterns.Flowpack\Neos\FrontendLogin\Security\NeosRequestPattern -> expected: type=dictionary, null found: type=string
Settings.TYPO3.Flo…
beheist
(Bastian Heist)
September 28, 2016, 7:30am
3
The last three errors are related to the new configuration format for Request Patterns in Flow 3.3. You can check that out here: https://github.com/neos/flow-development-collection/pull/130
Somebody™ can create a PR to https://github.com/Flowpack/Flowpack.Neos.FrontendLogin and fix that issue. The PR above describes how to change the format to the new one.
beheist
(Bastian Heist)
September 28, 2016, 7:34am
4
Hah, nevermind. Actually, there is already a PR for that: https://github.com/Flowpack/Flowpack.Neos.FrontendLogin/pull/12
So you can ignore that error for now, as the Package still works as expected, since the NeosRequestPattern class in the Frontend login package is also still expecting the old format. It will go away once that PR is merged.