chore(cms): deleted snippets (moved to diff repo) - #569
Merged
Conversation
These 9 template copies were reference-only records of djangocms-snippet content per this repo's "Save Snippets" convention. They now live in Core-CMS-Custom (TACC/Core-CMS-Custom#559) with no open PR here still editing them, so the local copies are redundant.
css-ad-hoc-styles.html and js-ad-hoc-scripts.html were held back from the prior commit because open PRs (#325, #535, #557, #562, #565, #566) still edited them here. Those PRs are being updated to drop their edits to these two files in favor of Core-CMS-Custom (TACC/Core-CMS-Custom#560), so the local copies can go too.
2 tasks
wesleyboar
changed the title
snippets (migrated to Core-CMS-Custom)
wesleyboar
changed the title
snippets (migrated to Core-CMS-Custom)snippets
wesleyboar
changed the title
snippetssnippets (migrated)
wesleyboar
changed the title
snippets (migrated)Unlike this PR's other deletions, these two were never migrated to Core-CMS-Custom (they're djangocms-snippet "template"-field templates, not manually-synced reference copies, per the original migration's notes). They're deleted here because #535 already deletes them independently — the external-post-link and redirect behavior they provide is now handled by Core-CMS itself.
This was referenced Aug 4, 2026
jarosenb
approved these changes
Aug 10, 2026
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.
Overview
Deletes manually-synced snippet templates which I migrated to TACC/Core-CMS-Custom.
Why?
Committing snippets to tup-ui results in complex syncing of live snippet changes tracked across multiple PRs. Easier to just save live snippet in one place. PRs will still be opened to TUP for
tup-cmscontainer code changes.Related
Migrated content to:
Updated outdated snippets:
Updated PRs that had edited the now deleted snippets:
Changes
redirect.html,news/open-external-post.html— never migrated to Core-CMS-Custom (they're djangocms-snippet "template"-field templates, not manually-synced reference copies); deleted here to match refactor: manage CMS assets, delete outdated assets #535, which already deletes them independently since Core-CMS itself now handles the external-post-link/redirect behavior they providedTesting
Core-CMS-Custom'stup/html/.redirect.htmlandnews/open-external-post.html's behavior still works via Core-CMS after refactor: manage CMS assets, delete outdated assets #535 merges.Notes
These files were reference-only copies (per this repo's "Save Snippets" convention) — the contents of live
djangocms-snippetinstances are unaffected.