Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Any ideas why every 24 hours a user macro would stop working until it is saved again?

Nicole Manilal July 23, 2018

I have a status macro as below:

## Date created: 2018-06-11
## @Param Status:title=Status|type=enum|required=true|enumValues=NOTSTARTED,IN PROGRESS,AWAITING PEER REVIEW,COMPLETE|desc=Choose a Check Sheet status.

#if ( $paramStatus == "NOT STARTED" )
#set ( $color = "Grey" )

#elseif ( $paramStatus == "IN PROGRESS" )
#set ( $color = "Yellow" )

#elseif ( $paramStatus == "AWAITING PEER REVIEW" )
#set ( $color = "Red" )

#elseif ( $paramStatus == "COMPLETE" )
#set ( $color = "Green" )

#else
#set ( $color = "Grey" )
#end

<ac:macro ac:name="status">
<ac:parameter ac:name="colour">$color</ac:parameter>
<ac:parameter ac:name="title">$paramStatus</ac:parameter>
</ac:macro>

 

Once saved this macro works for 24 hours, however the next day you can still see the macro in place but when editing a document you are unable to change the status.  No error message it just appears to be locked.  To get it working again you need to go in as an administrator and hit save on the macro again.

If anyone has any ideas as to what could be causing this it would be much appreciated.

2 answers

0 votes
Nicole Manilal July 24, 2018

Hi Igor,

Thank you.  Yes, I have confirmed the bug from the console window of my browser.

So, you're saying I need to go back to version 6.6.4 in order to get rid of this bug?  I'm confused when you say "the exception is 6.6.4 and up" because I'm thinking 6.8.0 is up from 6.6.4 so shouldn't be a problem?

Just need to be sure that my course of action should be to install 6.6.4.  I'm assuming I'll have no issues going back from 6.7.1 to 6.6.4?  If you could confirm this that would be appreciated.

Many thanks

Nicole

Igor M.
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 30, 2018

Hello,

Sorry for the confusion.

Confluence 6.6.* branch is a specially designated enterprise release, as a result, if there is a bug discovered in 6.7.2, and a fix for it is introduced in 6.7.3, then that same fix will be backported to 6.6.* branch, into whatever version is the latest in said branch. 

So when I say that bug is fixed in 6.6.4 and up, it is referring to up within the branch of enterprise release, so 6.6.5 and 6.6.n... If you are not on enterprise release, then your only option is to upgrade to 6.8.0 or higher.

You can read more about enterprise release here

0 votes
Igor M.
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 23, 2018

Hello,

Could you specify which confluence version you are running? There is a known bug in 6.6.0 and later that results in user macros breaking until they are edited and saved, then they break again.

Fixed in 6.6.4 and 6.8.0 and up

Nicole Manilal July 23, 2018

Hi Igor, 

We are using 6.7.1 but this does look like what's happening.  Editing the macro (or re-saving it) fixes it for a while but then it becomes uneditable again.   

Can you confirm that this version also has this problem?  

Thanks

Igor M.
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 23, 2018

Hello,

All versions between 6.6.0 and 6.8.0 are affected, the only exception is 6.6.4 and up, due to it being enterprise release so the fix was backported from 6.8.0 to 6.6.4.

You can see notes in the bug that editing and saving macro fixes it for short time, so the symptom matches.

You can also check the bug on how to confirm it from Console window of your browser.

Regards

Igor

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events