Bug #44602

Update YAML schemas to latest changes

Added by Bastian Waidelich about 8 years ago. Updated almost 8 years ago.

Status:
Resolved
Priority:
Should have
Assignee:
Bastian Waidelich
Category:
-
Target version:
TYPO3 Flow Base Distribution - 2.0
Start date:
2013-01-17
Due date:
% Done:

100%

Estimated time:
PHP Version:
Has patch:
No
Complexity:

Description

Currently

./flow configuration:validate --type Settings

and
./flow configuration:validate --type Objects

Return errors for Flow configuration.
The respective schemas need to be adjusted to recent changes

Files

composer.lock (36.2 KB) composer.lock Michael Klapper, 2013-01-17 17:44
#1

Updated by Bastian Waidelich about 8 years ago

  • Status changed from Accepted to Resolved
  • % Done changed from 0 to 100
#2

Updated by Michael Klapper about 8 years ago

I still get the following errors on a fresh composer based installation:
./flow configuration:validate --type Objects ... 1 errors were found: - TYPO3.Flow.TYPO3\Flow\Session\SessionInterface.factoryMethodName -> This property is not allowed here, check the spelling if you think it belongs here.

./flow configuration:validate --type Settings ... 5 errors were found: - TYPO3.Flow.session -> Property PhpSession is required - TYPO3.Flow.session.name -> This property is not allowed here, check the spelling if you think it belongs here. - TYPO3.Flow.session.garbageCollectionProbability -> This property is not allowed here, check the spelling if you think it belongs here. - TYPO3.Flow.session.cookie -> This property is not allowed here, check the spelling if you think it belongs here. - TYPO3.Flow.error.exceptionHandler.defaultRenderingOptions -> This property is not allowed here, check the spelling if you think it belongs here.

What should I do to solve this messages?

Cheers,
Mick

#3

Updated by Bastian Waidelich about 8 years ago

Michael Klapper wrote:

I still get the following errors on a fresh composer based installation [...]

Those are exactly the errors that this patch should fix. Are you sure you have the latest version including 911e281962d0c2312d0718daa29a8c8d44bce064 ?

#4

Updated by Michael Klapper about 8 years ago

For some reason I got an previous version of Flow by installing a fresh instance using composer.

However, I run composer update and validated the settings again - the configuration is valid!

#5

Updated by Gerrit Code Review almost 8 years ago

  • Status changed from Resolved to Under Review

Patch set 1 for branch 2.0 has been pushed to the review server.
It is available at https://review.typo3.org/17863

#6

Updated by Bastian Waidelich almost 8 years ago

  • Status changed from Under Review to Resolved

Also available in: Atom PDF