Hi!
We have been using balsamiq mockups together with confluence to document our requirements. However in the last versions of balsamiq mockup plugin, it s no longer possible to view a previous version of the mockup in the page history, instead a message saying "Mockup image file <mockup_name>.png (version -1) not found. Did someone delete it?"
Why is this not working anymore? I can find the old versions of the mockups when browsing the attachments on the page, but it s inconvient consider it is in the page history you want to see it (and could before).
/Roger
Hi Roger,
You are right, unfortunately the version number of mockups edited with version 2.2.10 has not been incremented, leading to the problem you have described.
However, the revisions created are not lost as you can see by looking the page history. The problem is that the page contain a macro pointing to an old version.
The only possible workaround at the moment is to delete the macro with the wrong version number and insert manually a new macro in the page with the following syntax: {mockup:Name|VersionNumber}.
For example if the name of the mockup modified is "Test" and the version you want to be displayed is 4, the placeholder should be {mockup:Test|4}. If you want to force to the last revision the syntax is {mockup:Test|-1}
The editor now will now be able to open the correct version.
Let us know if this fiox your issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi!
It s working now when creating new mockups which is great! However existing mockups created in the previous version of balsamiq still have the same error, and shows error msg: "Mockup image file <mockup_name>.png (version -1) not found. Did someone delete it?", in the history view."
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I contacted the vendor and they confirmed it was bug in their plugin. So hopefully it will be corrected soon.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey there, Roger.
I would definitely recommend you to contact the plugin vendor directly as they will be the best point of contact when you are facing some issues with the plugin usability. Kindly refer to the following:
This will help to speed things up on your side. Hope this helps.
Warm regards,
Danial
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.