<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>5.0.7 — Panopto Community</title>
        <link>https://community.panopto.com/</link>
        <pubDate>Fri, 19 Jun 2026 10:35:54 +0000</pubDate>
        <language>en</language>
            <description>5.0.7 — Panopto Community</description>
    <atom:link href="https://community.panopto.com/discussions/tagged/5-0-7/feed.rss" rel="self" type="application/rss+xml"/>
    <item>
        <title>[RESOLVED] Notification of an Issue affecting Moodle Builds released in April 2026</title>
        <link>https://community.panopto.com/discussion/2941/resolved-notification-of-an-issue-affecting-moodle-builds-released-in-april-2026</link>
        <pubDate>Mon, 01 Jun 2026 16:34:20 +0000</pubDate>
        <category>Bug Reports</category>
        <dc:creator>Miroslaw Domski</dc:creator>
        <guid isPermaLink="false">2941@/discussions</guid>
        <description><![CDATA[<p><strong>Who is impacted/who has the potential to be impacted? </strong></p><p>Any Moodle/Panopto customers who upgrade to the latest version of Moodle<br />
that was released in April of 2026.  This issue specifically impacts those<br />
using the TinyMCE, Student Submission tool, and ATTO plug-ins.</p><p><strong>What is the impact/potential impact?</strong></p><p>If a user goes to a course and selects add activity Panopto Video<br />
or follows the student submission workflow and selects a video, after clicking<br />
the insert button the user is directed to log-in again.  This essentially<br />
breaks core workflows associated with creating/submitting content.</p><p><strong>How can this be mitigated?</strong></p><p>Ideally customers should hold-off on installing the latest version<br />
of Moodle until after we have released a fix.</p><p><strong>When will this be fixed? </strong></p><p>We are actively working on a fix to this issue and hope to release<br />
a hotfix by the middle of this week (i.e. w/c 2026-06-01).</p><p><strong>Any data cleanup or other actions required to mitigate the issue<br />
after the bug is resolved?</strong></p><p>No</p>]]>
        </description>
    </item>
   </channel>
</rss>
