fix(SFT-1656): neo fields #356
Open
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
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.
Fixes:
#336
#354
fix: refactored solution for "create new event" to use Craft core duplicate functionality instead of creating new event
https://solspace.atlassian.net/browse/SFT-1323
fix: removed our custom save field solution for Neo - it was breaking file uploads and neo fields in general in Craft 5 (even though I copied the functionality exactly from Craft core elements)
https://solspace.atlassian.net/browse/SFT-1656
chore: test neo field translations again
https://solspace.atlassian.net/browse/SFT-1525
chore: updated php-cs-fixer version and added a flag for config file in composer scripts
Closing #344 as no longer required.