Our self-developed plugin works fine. Now it was time to modify it. We have successfully tested the new plugin and uploaded. We always have uninstalled the old plugin and upload the new plugin. In the transition phase must be installed both plugins at the same time. This causes a problem. When we upload the new plugin will be uninstalled the old plugin. How can we solve the problem? The plugin names are different, the version number are also different. Is there somewhere still an ID, which I must change? I hope you can help me.
Thank you, it almost works. The new plugin is uploaded, but now I get an error message.
"There were errors loading this plugin. There is more information in the logs.
There was a problem loading the module descriptor. com.xx.xxxxxx.plugins.config.DefaultThemeService <br/> Can not overwrite an existing bean definition: theme Service"
The old plugin still works fine. It amazes me that the new plugin now can not be loaded. Just because I pluginkey in the atlassian-pluginfile.xml have changed? Do you have another idea? its tricky....
@Gustav Stresemann: I'm guessing here, but it sounds like you've used the Documentation Theme as a basis for a new Confluence theme.
In the Documentation Theme, the "Default Theme Service" and the "Velocity Helper" are important parts of the theme that allow the theme to be configured with or without content in the left hand navigation panel and in the page header and footer.
Here are the references to the items in the atlassian-plugin.xml file:
<component key="themeService" name="Default Theme Service" class="com.atlassian.confluence.plugins.doctheme.DefaultThemeService"> <description>Services to store and retrieve theme configuration information.</description> <interface>com.atlassian.confluence.plugins.doctheme.ThemeService</interface> </component> ... <velocity-context-item key="velocityHelper" name="Velocity Helper" class="com.atlassian.confluence.plugins.doctheme.DocThemeHelper" context-key="docThemeHelper"/>
In a more straightforward Confluence theme, these custom components may not be needed.
If you need similar functionality, try renaming the classes and also use different keys. For clarity, I'd also slightly change the descriptions too :)
Yeah, the problem will be the 'key' value for these. The actual implementation class name shouldn't be an issue, since class names don't cross plugin boundaries unless you explicitly tell them to. But the key names are set globally, so they need to be unique for every plugin. You will also then need to modify your .vm and .vmd files to use your new key names, so that if the old Documentation theme is uninstalled, your new theme will keep working.
Hi team, I’m Avinoam, a product manager on Confluence Cloud, and today I’m really excited to let the Community know that all customers can now try out the new editing experience and see some of the ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs