TASK: Apply core migrations #52
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit imports the core migration log to the "extra" section of the composer manifest.
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.
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.
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.
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.
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.
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.
Rename "renderTypoScript" VH to just "render" 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 "renderTypoScript" VH to just "render" 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 removed TYPO3.ContentRepository:Folder node type by replacing it 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 node type and TS object names in NodeTypes.yaml and PHP code. 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 Neos\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.
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.
Adjust to updated date format for inspector date editor 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 updated folder name for TypoScript in site 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.
Adjust to renamed NodeLabelGeneratorInterface. 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.
Migrates the former HtmlEditor to CodeEditor 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 namespaces for ContentRepository related FlowQuery operations that were moved from TYPO3.Neos to TYPO3.TYPO3CR 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 setting TYPO3.Neos.modules.<moduleName>.resource 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.
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.
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.
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.
Rename node property type 'date' to DateTime 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.
Migrates ImageVariant to ImageInterface 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.
Migrates to new super type syntax in node type configuration 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.
Adjust "Settings.yaml" to use validationErrorTranslationPackage instead of translationPackage 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 to the renaming of the Object namespace in Flow 4.0
Adjusts code to package renaming from "TYPO3.Neos.NodeTypes" to "Neos.NodeTypes" 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.Neos.Kickstarter" to "Neos.SiteKickstarter" 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.Neos" to "Neos.Neos" 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.TYPO3CR" to "Neos.ContentRepository" 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.TypoScript" to "Neos.Fusion" 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 settings path from TYPO3.Setup to Neos.Setup to Setup 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.
Fix wronly renamed Neos.SiteKickstarter references. There was a replacement from "TYPO3.Neos" to "Neos.Neos"; which inadvertedly also got applied 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.TypoScript" to "Neos.Fusion" in Fusion 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.
Adjusts code to package renaming from "TYPO3.Neos.NodeTypes" to "Neos.NodeTypes" in Fusion 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.
Adjusts code to package renaming from "TYPO3.Neos" to "Neos.Neos" in Fusion 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.
Adjusts code to Kickstarter 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.
Allow to migrate Sites.xml 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.
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.
60 tasks
|
I guess we should tag / release the package before merging this? |
daniellienert
approved these changes
Dec 20, 2016
|
@gerhard-boden: After merging 1.1 into master, we have some merge conflicts. Would you please solve them? |
daniellienert
approved these changes
Dec 20, 2016
|
@daniellienert thanks for checking, conflict resolved |
gerhard-boden
force-pushed
the
apply-core-migrations
branch
2 times, most recently
from
72d0f08
to
92579fa
Compare
…Search into apply-core-migrations Conflicts: Classes/Indexer/Object/ObjectIndexer.php composer.json
gerhard-boden
force-pushed
the
apply-core-migrations
branch
from
92579fa
to
c3883c9
Compare
|
@daniellienert Post review: I had this in my composer.json: We were using dev-master due to the introduced compatibility with ES 2.x, thus we cannot go back on using flowpack/elasticsearch 1.1.x. This PR now broke our installation, because you switched from: Since there is not a release from dev-master before this update of requirement, how should we proceed? My suggestion is to make a release out of the version previous to this PR and tag it with "1.2.0" (for example) - the last version compatible with Neos 2.3 and Flow 3.3. @kdambekalns what do you think? |
|
I guess I was not entirely correct with my last comment. I have no problem with 1.1.x of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.