We removed the option to add OpenID as third-party authentication, since that service was deprecated.
When you publish alink postwith a Chorus URL from a different community, we show the original source on home and hubpages (e.g., “From Eater LA”). We were showing that label on stories from the same community, but we’re not anymore.
Some folks reported seeing autosave errors when creating galleries with images from Merlin.
SoundCloud embeds don’t display for audiences on Apple News, but they won’t actually block a story from publishing there. We updated themessagesin the story editor to clarify that.
If you upload a video or thumbnail with_YTor_FBat the end of the file name, Chorus Video will autoselect the file on theappropriate platform card.
We removed the ability to star a group in legacy Chorus, since it doesn’t change anything.
You can now sort the editorial dashboard by last published date. We’ve had a lot of requests for original publish date and this is a step in that direction. (You can still search for status:published, too.)
We added a character count to thealt textfield based on your feedback. We’re planning to raise the limit from 255 characters in the future, but wanted to set better expectations in the story editor in the meantime.
If you schedule astreamand one of its stories at the same time, the stream will publish one minute later. This resolves an issue where streams and their stories were not showing up as related to each other.
Several people reported issues signing up for Chorus. After further investigation, we uncovered a bug withthird-party authenticationthat affected Google accounts without profile images. No faces required here, and the bug’s all fixed.
We’re making continuous improvements to our platform for accessibility. Contact forms, rating cards, and deks are now more accessible for people who use assistive technology. Learn more on theVox Product blogand check out ourbest practices guidefor making your stories available to all audiences.
We spiffed up some of the screens for resetting your password.
Chorus Video now saves the project number after you create a project to avoid duplication. You can still view and update it on the Details screen.
You can cut and paste objects within the body of a story, including images, embeds, and sidebars. That is, when there’s not a bug.
Searching for stories bycontributor(e.g.,by:“Marie Connelly”) wasn’t working properly.
On the Preview screen, the desktop option was showing the tablet preview before loading the full size.
Chorus Video now includes a project history sidebar. To see who created a project or when it was last updated, hit the Info button next to the Upload button on any project screen.
The Manage blog button in legacy Chorus was out to lunch. Sorry about that, site managers. Tacos on us!
We updated the split left and split right feature layouts to improve the spacing, color contrast, and logo alignment across all networks.
Images were not appearing in sidebars on Apple News.
Link posts were displaying an error message about streams failing to load. Say what?
If you change the first or last name on your account, you’ll see the changes immediately (or within 24 hours, if caching gets in the way).
If you add a drop cap to a paragraph that starts with a quote, the quotation marks and first letter of the sentence will be included.
Advertiser logos on sponsored mapstacks are more legible on mobile devices.
We’re planning to make extensive improvements to our audience design system in the coming months. These changes can affect feature stories withcustom styles. We added some warnings to the story editor to that effect.
Drop caps are now more visually consistent across browsers.
In Chorus Video, we simplified the language aroundgeo-restrictionsfor the Chorus player.
A bug was causing delays in publishing to Apple News. We fixed that up and added more capacity to this part of the platform.
A few folks were having trouble adding stories to streams.
If you tried to open a published story from the story editor, a bug was temporarily redirecting you to the homepage for your community.
The button for modifying drop caps on feature stories was displaying as a drop cap. So meta.
Drop caps weren’t rendering on shorter paragraphs. Sorry about that—donuts on us!
The version history icons in the headline, dek, and permalink fields kept getting smaller and smaller.
The edit button for lead art wasn’t responding.
The tweets section wasn’t displaying on a few published (and tweeted) stories.
Some error messages and tooltips were displaying twice in the story editor.
Gallery captions were displaying as code on Google AMP.
The site navigation screen in legacy Chorus wasn’t loading properly.
We rolled out the first major release ofChorus Video. If you’re working on video projects, please update your bookmarks tovolume.voxmedia.comso you don’t get stuck in the past.
You can now sort videos by the publish date in the story editor.
Recent studies have shown that Google usesauthor profilesand bios to evaluate content authority. We’ve updated our documentation to include more detailed recommendations from the search team.
When you’re sending a video to YouTube or Facebook, you’ll see the default status for your network instead of unlisted (unless that happens to be the default).
Version history was not displaying correctly on a few stories.
With the SEO team’s help, we learned that search images are more of a recommendation to Google than a guarantee of what will appear in search results. We’ve updated the search image tooltip to reflect this harsher algorithmic reality.
YouTube deprecated the ability to hide details from a video embed, so alas, we removed that option from the story editor.
When you’re adding a poll, a super long title or poll answer can block the story from publishing. We took a vote and you’ll now see a warning on the Finalize screen if you’re over the character limit.
Text fields in the story editor (e.g., headlines, tags, link sets) were spruced up to better suit our design system.
The video dashboard was throwing an “unauthorized” error for some users.
Historically, we’ve had a few reports of stories being stuck in a scheduled status even after being published. This was a status bug, not a scheduling bug, but it won’t happen anymore.