'Headlines End Date' Field No Longer Auto-populates
Release: Cheddar
We'll admit, when making changes to the CMS sometimes we'll get things wrong. What sounded like a good idea in development doesn't always translate well in real-world use. Cue: the headlines end date issue reported after the roll out of CMS Version 5.
By default, the headlines end date in a news post will defer to the post's archive date if a different date isn't entered. It sounded reasonable to have the headlines end date auto-populate with the chosen archive date. As it turns out, when the initially selected archive date gets changed, the headlines end date doesn't adjust to the new archive date. This function is by-design as clients will frequently use a different headlines end date than the archive date - this allows separate control over what displays in a news headlines feed vs a regular news feed.
Unfortunately some posts ended up not being displayed in headlines news feeds because originally input archive dates had already past, and the headlines end date was causing the post not to show in headlines feeds. We've switched the field back to it's original behavior: removing auto-population in the headlines end date, making the field always use the current archive date, unless a different date is manually added to the field.