Plugin compatibility with Confluence 3.0
With the official release of Confluence 3.0, we will be testing our plugins against that version shortly. We will update the current compatibility status of each here once they are tested or we hear problem reports from users.
In the meantime, we recommend that before upgrading your production servers to Confluence 3, test all plugins on a staging server. This is particularly the case if you use Scaffolding or Reporting, as they are fairly complex and are the most likely to break with an upgrade.
In the meantime, we recommend that before upgrading your production servers to Confluence 3, test all plugins on a staging server. This is particularly the case if you use Scaffolding or Reporting, as they are fairly complex and are the most likely to break with an upgrade.
24
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The company .
-
Inappropriate?David, I notice that in addition to the tabs problem, if you edit the {card} on Rich Text, is moving the first line as part of the label line. In that way the format
of the first line is changed.
here is an example...
{card:label=Key Features}\* User friendly graphical
I’m confident
-
Inappropriate?David,
Do we have any sort of timeline in mind for getting a compatible version of scaffolding data?
Thanks,
Adam J -
Inappropriate?Nothing concrete to report, but hopefully within the next couple of weeks.
-
Inappropriate?Do you have any new update as when Scalffolding will release a compatible version to Confluence 3.0?
-
Inappropriate?We are having several problems with the reporting plugin with 3.0 as well. Problems both with reporting on data retrieved from scaffolding page and with report-info macro. I can provide details if it will help
-
Inappropriate?Scaffolding is great. I can't wait to start using Reporting in Confluence 3.0. Hoping that a Reporting update that's 3.0 compatible can be released soon.
Thanks! -
Inappropriate?Hi Guys,
Do you have a rough timeline for when a 3.0 compatible reporting plugin will be released? Do you need beta testers?
Thanks.
-
Inappropriate?I'm having problems with the Reporting and Linking plugins under Confluence 3.0.1. Could you please post an update as to when these plugins will be updated to be compatible with Confluence 3.0.x ?
-
Inappropriate?I'd love to see the redirect/alias plugin updated — I use it extensively.
I’m just waiting.
-
Inappropriate?Sorry to add on to the pile , but a few use the scaffolding plugin and the add row icon for edit.scaffold.action is a no show in Confluence 3.0.
JD
I’m JD
-
Inappropriate?About a month ago I was doing a fresh install of Confluence 3.0.0 and there was Linking Plugin in the Plugin Repository. I installed it with one click and happily used it.
Today I was doing another fresh install, and Linking Plugin was missing from the Plugin Repository. Was it removed during this time, or is something wrong with my installation?
I’m curious
-
The source of information for the Plugin Repository has changed in the last couple of weeks and we were a bit behind in updating the new location. I've done so now for Linking so it should show up in the Plugin Repository in the next hour or so. Thanks for the update! -
Thank you! Everything appears to be in order now! -
Inappropriate?is this now resolved in the latest update to the Composition Plugin?
-
I believe that the latest Composition Plugin supports Confluence 3.0. Some other plugins are still waiting for updates. -
Inappropriate?Hi all,
We've just released Linking 2.7.0, Tracking 2.5.0, Scaffolding 3.2.0 and Reporting 3.2.0. If you use this in Confluence 3.0, please upgrade them, in that order.
Linking and Tracking contain mostly compatibility fixes, but Scaffolding and Reporting have several new features as well. Check out the news items for a brief summary.
I’m thankful
-
Inappropriate?Reporting 3.2.0 installs correctly, but breaks when used with the message:
Error formatting macro: report-info: java.lang.NoClassDefFoundError: com/atlassian/confluence/mail/address/ConfluenceMailAddress in Confluence 2.9.
All dependencies have been upgraded as mentioned. Any tips?
I’m unsure
-
Inappropriate?Unfortunately, due to API changes in Confluence 3.0, Reporting 3.2.0 is only compatible with Confluence 3.0+. You will have to upgrade Confluence I'm afraid...
1 person says
this answers the question
-
Thats too bad. Guess I'll have to work around it for the time being then.
Btw. after dabbling with the new plugins I've been getting errors with the Linking plugin. Even after downgrading it to 2.6.8 I get the following message when using it:
Error formatting macro: link-page: java.lang.NoClassDefFoundError: com/atlassian/confluence/mail/address/ConfluenceMailAddress -
Inappropriate?Linking hooks in with Reporting, so if you still have Reporting 3.2.0 installed you will have problems in both. Also, it might be a good idea to restart confluence after you downgrade, in case any classes are lying around in memory.
-
Inappropriate?When will the "Composition Plugin" be compatible with Confluence 3.1?
(I upgraded to 3.1 instead of 3.0 to avoid its incompatibility with Internet Explorer 8: http://jira.atlassian.com/browse/CONF...)
I have a lot of {deck} and {card} content that is not being shown on pages after I upgraded my DEV environment from Confluence version 2.5.3 to 3.1. Only the content from the first tab is shown; the content from the other tabs does not even appear on the page.
FYI ...
01/04/2010
I uploaded the version 2.3.4 jar file (composition-plugin-2.3.4.jar) to my Confluence 3.1 installation via the "Plugin Repository" (to see what would happen) but the "Composition Plugin" version shows as 2.3.1 in the "Plugin Repository".
I’m frustrated
-
Hi Michael,
We are glad to announce Composition Plugin is compatible with Confluence 3.1 now.
http://community.customware.net/custo... -
Inappropriate?We've installed Linking 2.7.0, Tracking 2.5.0, Scaffolding 3.2.0 and Reporting 3.2.0 on our migrated Confluence 3.0.2.
But the links created by the reporting plugin are missing the tomcat context path. So clicking on those links leads in to 404 errors.
Is this bug known`?
thanx
Martin
-
oh i just fount the corresponding issue. hope that it will be fixed very soon:
http://greenhouse.customware.net/jira...
Loading Profile...

EMPLOYEE




