Canvas deploys contain code changes that are intended to fix bugs, improve performance, and prepare for new features, but they do not affect customer workflows. These deploys take place every two weeks. Intended changes in workflow are noted in the Canvas Release Notes published monthly.
Deploy notes currently only include notable fixed bugs.
Sub-accounts are not accessible after being deleted.
Explanation: When a sub-account was deleted in an account, the sub-account still displayed in a user’s list of enrollments. Additionally, the sub-account could still be accessed via direct URL. Canvas code has been updated to remove access to sub-accounts after their deletion from an account.
Course Analytics Pagination
The course analytics page paginates additional students when a user scrolls to the bottom of the page.
Explanation: When a user scrolled to the bottom of the course analytics page, the page did not display more than 10 students. Canvas code has been updated to return additional paginated results with additional page scrolls.
URLs added to a conversation message do not affect any subsequent body content.
Explanation: When a URL was added to a conversation message, all additional content was appended inside the message action menu and displayed empty additional space. Canvas code has been updated retain proper space formatting between URLs and body content.
Message padding is retained outside the message text field.
Explanation: When a new message was created in Conversations, the text on the left side was getting hidden when the text wrapped from the previous line. Canvas code has been updated to correct padding around the message text field.
New Quizzes and Past Due Dates
New Quizzes with past due dates display missing and late statuses correctly.
Explanation: When a quiz created in New Quizzes had a past due date, the quiz did not display the missing or late statuses in the New Gradebook. This behavior also affected SpeedGrader. Canvas code has been updated to correct status behaviors according to due date.
Course Access and Restriction Settings
Course notifications are not sent unless students have access to the course.
Explanation: If a course was published with a start date in the future, or if a course had ended via section dates, and both scenarios included the setting to restrict students from viewing before and after the start date, students were still receiving content creation notifications for assignments and discussions. Canvas code has been updated to not send notifications unless students have access to the course.
Multiple Attempts and Take Quiz Again Button
Clicking the Take Quiz Again button multiple times does not affect quiz attempts.
Explanation: When a student was granted multiple attempts in a quiz, and the student clicked the Take Quiz Again button multiple times in a row, the quiz attempts were recorded incorrectly and could cause the quiz attempt to skip an attempt number. Canvas code has been updated to not affect the number of attempts if the button is clicked multiple times.