Feature add fields #46
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
… are used in a post are validated.
To avoid DB issues, the save of the post, posttranslate and field are placed in a dbtransaction.
Had to change the order in wich models are saved.
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.
New Features:
Admin can add custom fields.
Admin can define field type of custom field
Admin can add additional validation rules
Admin can add categories to fields.
Fields which have no category are used on all posts
when a field has a category, this field is only used on posts which have the same category.
By default only the fields with values are displayed below a post.
Improvements:
Added transactions when saving a post to avoid database inconsistencies.