We updated our Scroll PDF Exporter and Scroll HTML exporter plugins earlier this week, moving from version 3.3.0 to 3.3.1 (running Confluence 5.6.6). The update process itself appeared to go well and without error.
Shortly after the update, we realized that nobody could access the Space Tools interface for any space in that used the global look and feel (users would get a Java error during page render). Online research indicated that this issue could occur if plugins don't initialize properly. Knowing that the only recent change was the two Scroll plugin updates, we elected to restart Confluence. Our IT engineer was watching the Confluence logs during the shutdown process, and the only plugins that had messages were the Scroll plugins. It was un-registering the old plugin and registering the new plugin during shutdown.
This begs the question: It it necessary to restart Confluence after updating the Scroll HTML/PDF Exporter plugins?
Please sign in to leave a comment.