* Provide another option validationGroups.
* Allow each validation entry to be executed only for matching
validation groups.
* Necessary for the same reason as documented in flow documentation. It
should be possible to execute different validation rules for the same
name or class, only at some points, e.g. at a specific action.
Migrate bootstep names.
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Migrate usages of the path [TYPO3][Flow][Security][Authentication] to
[Neos][Flow][Security][Authentication]
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Migrate name for the media image size cache
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjusts code to package renaming from "TYPO3.Fluid" to
"Neos.FluidAdaptor".
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjusts code to package renaming from "TYPO3.SwiftMailer" to
"Neos.SwiftMailer".
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjusts code to Neos\Flow\Utility\Unicode adjustment
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjusts code to package renaming from "TYPO3.Media" to "Neos.Media"
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjusts code to Imagine Renaming
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjusts code to Eel Renaming
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjusts code to cache extraction
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjusts code to package renaming from "Neos.Flow.Utility.Files" to
"Neos.Utility.Files" and other extractions of the "Utility" packages.
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjusts code to package renaming from "TYPO3.Flow" to "Neos.Flow"
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjust to the renaming of the Object namespace in Flow 4.0
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjust to the renaming of the Resource namespace and class in Flow 4.0
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjust "Settings.yaml" to new "requestPattern" and "firewall" syntax
(see FLOW-412)
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Add "escapeOutput" property to existing ViewHelpers to ensure
backwards-compatibility
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Warn about removed ReflectionService dependency from AbstractViewHelper
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjust "Policy.yaml" to new syntax
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Rename the "resource" argument of the security.ifAccess ViewHelper to
"privilegeTarget"
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
This migration does not actually change any code. It just displays a
warning if a TypeConverters canConvertFrom() is
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Change TYPO3\Flow\Persistence\Doctrine\DatabaseConnectionException to
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Change entity resource definitions from using _ to \
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Check for globally defined role identifiers in Policy.yaml files
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Rename FLOW3 to TYPO3 Flow
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Move all code to PSR-0 compatible directory structure, remove
Package.xml,
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Replace DataNotSerializeableException with DataNotSerializableException.
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Replace FileTypes use with MediaTypes use.
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Rename form.textbox to form.textfield
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjust to the major changes in FLOW3 1.1 when coming from 1.0.
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Changes path to export and changed Mail-Interface
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
