Stop pulling news & events from the defunct legacy site #1070
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
alxbridge
force-pushed
the
support/fix-legacy-api-fetch
branch
from
3dec43e to
4fd91a9
Compare
kevinhowbrook
approved these changes
Jan 22, 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.
As the legacy site is no longer online, calls to its content from the
refetch_legacy_news_and_eventsfail, causing errors on pages whose templates render the legacy content. This fixes those errors by makingrefetch_legacy_news_and_eventsreturn an empty list instead, which will get things working until a longer-term code cleanup can take place.