feat: trigger update_pseudo_materialized_fields on Post and Question admin save #3836
Conversation
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
…admin save When saving a Post or Question in the Django admin, this now triggers the update_pseudo_materialized_fields method to ensure all pseudo materialized fields (scheduled/actual close/resolve times, etc.) are properly updated. Fixes #3832 Co-authored-by: Luke Sabor <[email protected]>
hlbmtc
approved these changes
Nov 27, 2025
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.
This PR implements automatic triggering of
update_pseudo_materialized_fieldswhen saving Post or Question objects in the Django admin.Changes
save_modeloverride toPostAdminthat callsupdate_pseudo_materialized_fields()after savingsave_modeloverride toQuestionAdminthat gets the associated Post and callsupdate_pseudo_materialized_fields()This ensures that pseudo materialized fields (scheduled/actual close/resolve times, etc.) are properly updated whenever these objects are saved via the admin interface.
Fixes #3832
Generated with Claude Code