Details
Bug
Blocker
Description
In the event that a flashed message is stored within the user's session, but the user accesses a plugin URI and that plugin does not support displaying messages on its own, an error is thrown as the view does not exist.
To resolve, AppController must fall back to display messages through the main interface if the plugin does not support this capability.
Originally reported in the forums.
Activity
What appears to happen in some cases (not sure exactly how yet), a success message ("Feed was successfully removed") is flashed for the next URI, but when the widget is reloaded via the browser (/admin/widget/feed_reader/admin_main/index/1/), the feed reader inherits from AppController which attempts to set the success message within the context of the feed reader, but the feed reader is not equipped to handle the message so an error is thrown.
Likely solution is to ensure that AppController:setMessage() falls back to rendering message as if $in_current_view was set to false.
Cody Phillips (Inactive)
added a comment - What appears to happen in some cases (not sure exactly how yet), a success message ("Feed was successfully removed") is flashed for the next URI, but when the widget is reloaded via the browser (/admin/widget/feed_reader/admin_main/index/1/), the feed reader inherits from AppController which attempts to set the success message within the context of the feed reader, but the feed reader is not equipped to handle the message so an error is thrown.
Likely solution is to ensure that AppController:setMessage() falls back to rendering message as if $in_current_view was set to false. 
Steps to duplicate: