feat(TimeMachine) include FTM content as rendered html Refs: #30937 #30952
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.
Proposed Changes
This update resolves an issue where changes related to TimeMachineDate were not reflected in the Rendered field, which generates the HTML output. Previously, the Contentlets field responded to these changes, but the same functionality was not applied to the Rendered field.
The update introduces two key improvements:
The TimeMachineDate is now passed to the same function used to process Contentlets, ensuring that changes also affect the Rendered field.
This function handles validation of contentlets, checking if they are scheduled for future publication or if their validity has expired. This ensures consistent behavior across fields.
The VTL layer contained logic for handling TimeMachine, which is now obsolete. All necessary validation is centralized within the updated function.
This PR fixes: #30937