[6.x] Support non-revisable fields in entries - #11252
Open
edalzell wants to merge 46 commits into
Open
Conversation
edalzell
changed the title
edalzell
marked this pull request as ready for review
December 13, 2024 19:43
Contributor
Author
|
I didn't see any tests for EntriesController nor TermsController, and honestly I was afraid to start them cuz I bet they need lots of setup. Happy to start one, with some guidance |
Member
|
Those are in Tests\Feature\Entries\StoreEntryTest, UpdateEntry, EditEntryTest, etc. |
edalzell
marked this pull request as draft
December 16, 2024 23:52
edalzell
marked this pull request as ready for review
December 20, 2024 22:51
This was referenced Jan 2, 2025
Contributor
Author
|
Don't understand why the tests are failing, cuz one of the runs DID pass. |
edalzell
marked this pull request as draft
January 27, 2025 21:55
edalzell
marked this pull request as ready for review
January 27, 2025 23:23
edalzell
changed the title
duncanmcclean
changed the title
edalzell
marked this pull request as draft
March 24, 2026 23:48
# Conflicts: # tests/Feature/Entries/EntryRevisionsTest.php
# Conflicts: # src/Http/Controllers/CP/Collections/EntriesController.php # tests/Fields/BlueprintTest.php # tests/Fields/FieldTest.php # tests/Fields/FieldsTest.php # tests/Fields/SectionTest.php # tests/Fields/TabTest.php # tests/Fieldtypes/NestedFieldsTest.php # tests/Fieldtypes/SetsTest.php
edalzell
marked this pull request as ready for review
March 25, 2026 18:19
# Conflicts: # tests/Feature/Entries/UpdateEntryTest.php
# Conflicts: # src/Fields/Field.php
This file contains hidden or 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
2 participants
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.
We have a feature were you can sponsor an orphan. The sponsorship happens in the background (through folks signing up online).
We also have revisions. The issue is that if we want to revert back to some previous orphan data, we might be restoring a version that doesn't have a sponsorship, which will cause problems.
So we'd like to set the sponsorship fields as non-revisable so they persist.