New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move Flow/Neos specific classes to Neos namespace #49
Comments
With the release of Neos 3 and Flow 4 this change is getting bigger. |
Neos and Flow are not in the TYPO3 namespace anymore. This change is breaking as surf configurations might override tasks which have moved to the new namespace. Related: TYPO3#49
Flow 4.0 has now the Neos namespace and needs a different fully qualified name for the commands. This change is breaking as the default Flow version is now set to 4.0 and configurations might need to be adapted. Resolves: TYPO3#49
Neos and Flow are not in the TYPO3 namespace anymore. This change is breaking as surf configurations might override tasks which have moved to the new namespace. Related: TYPO3#49
Flow 4.0 has now the Neos namespace and needs a different fully qualified name for the commands. This change is breaking as the default Flow version is now set to 4.0 and configurations might need to be adapted. Resolves: TYPO3#49
Flow 4.0 has now the Neos namespace and needs a different fully qualified name for the commands. This change is breaking as the default Flow version is now set to 4.0 and configurations might need to be adapted. Resolves: TYPO3#49
Neos and Flow are not in the TYPO3 namespace anymore. This change is breaking as surf configurations might override tasks which have moved to the new namespace. Related: TYPO3#49
Flow 4.0 has now the Neos namespace and needs a different fully qualified name for the commands. This change is breaking as the default Flow version is now set to 4.0 and configurations might need to be adapted. Resolves: TYPO3#49
Neos and Flow are not in the TYPO3 namespace anymore. This change is breaking as surf configurations might override tasks which have moved to the new namespace. Related: TYPO3#49
Flow 4.0 has now the Neos namespace and needs a different fully qualified name for the commands. This change is breaking as the default Flow version is now set to 4.0 and configurations might need to be adapted. Resolves: TYPO3#49
Neos and Flow are not in the TYPO3 namespace anymore. This change is breaking as surf configurations might override tasks which have moved to the new namespace. Related: TYPO3#49
Flow 4.0 has now the Neos namespace and needs a different fully qualified name for the commands. This change is breaking as the default Flow version is now set to 4.0 and configurations might need to be adapted. Resolves: TYPO3#49
Are there any plans yet when the new version of Surf shall be released to support deployment of Flow 4.0 applications? How is deployment of these updated (Flow 4.0) applications possible in the meantime? |
@P34CH I'm a bit busy right now to finalize the change but I hope to get it done soon. For now you just need to replace two tasks to deploy Flow 4.0 right now:
|
@Sebobo Thanks very much for your reply! I'm still getting an error, after I added your snippet to my deployment script configuration:
At first a create a new SimpleWorkflow. Afterwards I add your snipped, then I link this workflow to my deployment. Next I create a node, add this node to a new application and assign this application to the deployment as well. Do you have any hints where/how I might fix this issue for deploying my Flow 4.0 application with surf? |
@P34CH you should one time delete your surf cache on the target system. |
The text was updated successfully, but these errors were encountered: