• Type: Bug
• Resolution: Fixed
• Priority: Low
• Fix Version/s: 4.2
• Affects Version/s: 4.2
• Component/s: None
• Labels:

  • affects-server
  • plugins
• Environment:

  4.2-beta2

1. 

   bonfire-screenshot-20120322-193439-107.png

   94 kB

   22/Mar/2012 11:34 AM

2. 

   upm-4.1.png

   78 kB

   28/Mar/2012 11:54 PM

[CONFSERVER-25001] Some bundled plugins are listed under "User-installed Plugins" in UPM

Collapse comment: Joe Clark added a comment - 03/Dec/2012 12:08 AM

Joe Clark added a comment - 03/Dec/2012 12:08 AM

Hi Jurriaan,

It's a bug in Confluence that can only be fixed with a code change. There's no need to re-open this ticket. The problems in Confluence 4.3.x are tracked at CONF-26253. You should vote/comment and/or watch that issue for future updates.

Regards,
Joe.

Expand comment: Joe Clark added a comment - 03/Dec/2012 12:08 AM

Joe Clark added a comment - 03/Dec/2012 12:08 AM Hi Jurriaan, It's a bug in Confluence that can only be fixed with a code change. There's no need to re-open this ticket. The problems in Confluence 4.3.x are tracked at CONF-26253 . You should vote/comment and/or watch that issue for future updates. Regards, Joe.

Collapse comment: Deleted Account (Inactive) added a comment - 01/Dec/2012 7:21 AM

Deleted Account (Inactive) added a comment - 01/Dec/2012 7:21 AM

Hi,

This tickets is marked resolved in 4.2. However, we are still experiencing this in 4.3.1. In CONF-26253, this is experienced in 4.3 as well. Could you please comment on how this is fixed or how we can fix this in 4.3+ instances? Otherwise, this ticket should be regarded as not fixed and hence reopened?

Regards,
Jurriaan van Reijsen
The Courseware Company - Dutch Atlassian Expert

Expand comment: Deleted Account (Inactive) added a comment - 01/Dec/2012 7:21 AM

Deleted Account (Inactive) added a comment - 01/Dec/2012 7:21 AM Hi, This tickets is marked resolved in 4.2. However, we are still experiencing this in 4.3.1. In CONF-26253 , this is experienced in 4.3 as well. Could you please comment on how this is fixed or how we can fix this in 4.3+ instances? Otherwise, this ticket should be regarded as not fixed and hence reopened? Regards, Jurriaan van Reijsen The Courseware Company - Dutch Atlassian Expert

Collapse comment: Joe Clark added a comment - 02/Apr/2012 10:31 PM

Joe Clark added a comment - 02/Apr/2012 10:31 PM

I tested 4.1 vanilla. It's not a UPM bug - the behaviour for marking plugins as User installed vs. System plugins hasn't changed between UPM 1.x and 2.x. The problematic plugins are all new plugin components in Confluence that haven't been bundled correctly.

Expand comment: Joe Clark added a comment - 02/Apr/2012 10:31 PM

Joe Clark added a comment - 02/Apr/2012 10:31 PM I tested 4.1 vanilla. It's not a UPM bug - the behaviour for marking plugins as User installed vs. System plugins hasn't changed between UPM 1.x and 2.x. The problematic plugins are all new plugin components in Confluence that haven't been bundled correctly.

Collapse comment: Anatoli added a comment - 02/Apr/2012 10:24 PM

Anatoli added a comment - 02/Apr/2012 10:24 PM

Joe, what version of 4.1 did you test? We backported UPM to 4.1 so this bug must have been backported too.

Expand comment: Anatoli added a comment - 02/Apr/2012 10:24 PM

Anatoli added a comment - 02/Apr/2012 10:24 PM Joe, what version of 4.1 did you test? We backported UPM to 4.1 so this bug must have been backported too.

Collapse comment: Joe Clark added a comment - 28/Mar/2012 11:54 PM

Joe Clark added a comment - 28/Mar/2012 11:54 PM

I don't think this is new in 4.2 - 4.1 had a similar problem:

Presumably these plugins are just missing the descriptor that marks them as a system plugin.

Expand comment: Joe Clark added a comment - 28/Mar/2012 11:54 PM

Joe Clark added a comment - 28/Mar/2012 11:54 PM I don't think this is new in 4.2 - 4.1 had a similar problem: Presumably these plugins are just missing the descriptor that marks them as a system plugin.