5. 3. Atlassian Support’sanswers NI: A lot of the bundled system plugins of the 2.7.1 are unavailable in 3.0's plugin repository, but seems to work. Is this becouse they are built-in now?(attachedlist) Atlassian: „All of the plugins in the list are core plugins needed for basic functionality in Confluence. You do not need to worry about them. However, an exception to the Page Tree plugin - it has been bundled in Confluence since Confluence 2.8. Pay attention to this plugin, since you will get duplicate copy of this plugin after upgrading to 3.0.” - AzwandiMohd Aris(Support)
6. 3. Atlassian Support’sanswers NI: We are using a free download local install Confluence 3.0.0_01-Standalone to test the plugin's compatibility. We assume that if a plugin runs on a 3.0-Standalone, will run on our server that will be upgraded from2.7.1 to 3.0.Is there any difference between a 3.0-Standalone and the upgraded to 3.0 in terms of plugin compatibility? Atlassian: „there should not be any difference in the plugins in both of the local (fresh) installation and upgraded instance. In other words, the type of installation (fresh or upgraded) has no influence in the compatibility of the plugin.” - AzwandiMohd Aris(Support)
7. 3. Atlassian Support’sanswers Atlassian: „Yes. That's a fair assumption. It's basically the same code running the plugins. If you do run into problems or have further queries, feel free to contact our support team at https://support.atlassian.com/.Thank you for using Confluence 3.0.” - David Chui (Pluginspecialist, 3.0 development team)
