Balsamiq Community Discussion

Balsamiq for Confluence - no macro metadata error


#1

We have just loaded the confluence cloud Balsamiq Add-On which has loaded correctly and is registered in the confluence settings area.

Upon opening a page for editing and selecting the Balsamiq plug-in i get a dialogue pop up reporting “no macro metadata”

Any ideas?


#2

Hi @shaunf and so sorry for the snag.

This “no metadata” error message is actually caused by a bug that affects multiple Atlassian add-ons. Atlassian support is investigating it and you can follow along (and vote for it) on this page.

In the meantime, would you like to work on Mockups 3 for Desktop?

It uses the same editor and file format that Mockups 3 for Confluence Cloud, and comes with a 30-day free trial. You can download it on this page.

I can also give you a Mockups 3 for Desktop trial extension in case you’ve already used a trial, just let me know via support@balsamiq.com.

Sorry again for the trouble. Please let us know if you need anything else, we’re here to help!


#3

Are there any updates on this issue? We are getting the “no metadata” error


#4

Hi @Aaron and sorry for the trouble.

I’ve just sent you an email as it may be easier to troubleshoot that way but I noticed that the related Atlassian ticket is still “in progress” for now.

We’ll do our best to help!


#5

I tried with Chrome + MS Edge. Neither worked


#6

Thanks @Aaron.

Has this issue been happening for a while? I only ask because I have seen a couple of instances of this happening, and then it miraculously working again. This could be something on Atlassian’s side, but I want to be sure.


#7

We just installed the plug-in to evaluate it. It has never worked


#8

Ugh, I’m sorry, Aaron. What a terrible first run.

If you have time this week, and want to give it another shot, install it and let us know if the problem persists. Totally understand if you don’t have time, but we’d love a chance to troubleshoot with you.


#9

Our team has moved onto another tool, thanks for the offer to troubleshoot but it’s no longer necessary


#10

Fair enough, Aaron. Good luck to you and the team. :slight_smile: