Loading Profile...
Mockup changes are not reflected in XWIKI page.
While using Balsamic with XWIKI, I've found that when I make changes, the changes are saved in the attachment (i.e. a new revision is created), but the XWIKI page does not display the updates ... it seems to show the previous revision of the mockups. If I hit refresh on the browser, the new imaje shows, but if I re-edit the mockup, I'm returned to an editor of the previous version of the mockup.
This can really be an issue if I am attempting to make multiple updates to a mockup. Basically, you lose the previous changes that you made to the mockups because you are editing a previous revision of the mockups.
I have confirmed that this is some sort of caching issue that I believe to be within the Balsamic code running in XWIKI. Basically, if I clear all offline content, then when I edit, I get the latest revision of the mockup. So, how can I get this to work without deleting all offline content?
Any help would be appreciated.
This can really be an issue if I am attempting to make multiple updates to a mockup. Basically, you lose the previous changes that you made to the mockups because you are editing a previous revision of the mockups.
I have confirmed that this is some sort of caching issue that I believe to be within the Balsamic code running in XWIKI. Basically, if I clear all offline content, then when I edit, I get the latest revision of the mockup. So, how can I get this to work without deleting all offline content?
Any help would be appreciated.
I’m frustrated
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
-
Inappropriate?Hi Johnnie, sorry you hit this issue. It's a caching issue with the browser which I thought I had fixed. Do you perhaps use https to serve your XWiki pages? Does a shift+reload always load the latest version of the mockups when you edit it?
I will take a look at trying to reproduce the bug locally and get back to you with what I find out. In the meanwhile, if you could send me an email with your configuration details (version of XWiki, app server used, the browser you're using, version of Mockups for XWiki, that sort of thing), I'd appreciate it.
I’m eager to get this resolved
-
Inappropriate?To answer your questions:
- We do not use https to server our XWiki pages.
- We are using an older release of Internet Explorer v6.0.2800, but I noticed that when using the latest release of firefox, I don't see the issue where when I edit I get the previous revision in the Mockup editor. However, even with firefox I still see the issue where I have to hit "refresh to see the updated WIKI page.
- Shift+reload (F5) does not load the latest version of the mockups. The only way I have been able to consistently load the latest version of the mockups is to delete my temporary internet files.
- I have Xwiki v1.3
- Server is Jetty v6.1.6rc0
- Internet Explorer v6.0.2800
- Balsamiq Mockups v1.5.24
Thanks for your help.
I’m thankful
-
Inappropriate?Giacomo,
I think you could fix this issue by modifying your macro displaying the image. If you modify the URL generated to access /xwiki/bin/viewrev/Space/Page/image.png?rev=$attach.version Then you will have a unique link to the specific image version thus fixing the cache issue.
From the user's point of view, CTRL-Reload should force a reload of the image. -
Inappropriate?Hi there, just a quick note to tell you that I'm still investigating this issue. I hope to have some more info later today or tomorrow.
-
Inappropriate?Hi there, quick update. I was able to reproduce both issues, which only ever happen in IE. :(
I'll report back after googling for a solution
-
Inappropriate?Ok, I've fixed half of the problem (the most critical half I think). Now when you edit an existing mockup, you should always get the latest data back (the solution was to add some well-placed "Cache-control:no-cache" and "Expires:-1" headers).
I still haven't figured out the other issue, but it's similar: the browser caches the image and doesn’t update it.
Ludovic, here's a snippet of my macro code:
#macro(mockup $name)
#set($mockups=$xwiki.mockups)
#set($hasEdit=$xwiki.hasAccessLevel('edit'))
#set($png=false)
#set($xml=false)
#set($png=$doc.getAttachment("${name}.png"))
#set($xml=$doc.getAttachment("${name}.bmml"))
#if($png and $xml)
<div align="center">
{image:${name}.png|halign=center|alt=$name}
As you can see, I use the {image} macro to fetch the attachment. How would you change this to always get the latest version of the image?
BTW Ludovic, thanks so much for chiming in, I'm really impressed that you found this discussion, it's an honor! :)
Johnnie, if you'd like to try what I've done so far you can get the new JAR here: http://www.balsamiq.com/products/mock...
I’m happy half of it is solved at least
-
Inappropriate?Hi Giacomo,
You can use this for your image
This should force your image link to be the one with the most recent version1 Comment
Add a comment
This solves the problem
-
I think something got lost in the getsatisfaction posting...can you perhaps repost it without the lt; and gt; characters? -
Inappropriate?Giacomo,
Thanks for the compliment. I happen to follow references to XWiki and found this one and since I like balsamiq very much as a user and happened to know the answer I just chimed in :)
Ludovic
I’m happy
-
Inappropriate?Here it is:
img src="$doc.getAttachmentURL($png.filename, "download", "rev=${png.version}")" alt="$name" /1 Comment Add a comment
This solves the problem
-
That worked like a charm Ludovic, merci beaucoup! :)
-
Inappropriate?Hi Johnnie, please find a version of Mockups for XWiki which fixes both of your bugs here: http://www.balsamiq.com/products/mock... (it's version Next.40) - I will be merging these changes into the official 1.5 branch on Tuesday.
I’m happy when quality goes up!
-
Inappropriate?Hi,
I've got similar problem on my browser.
After editing mockup, image is not refreshed on my wiki page.
I use XWiki Enterprise 1.9.1.21780 version and Balsamiq Version: 1.6.30 - 07/14/2009 09:46 (XWiki).
Should I instal other version of Balsamiq?
I’m frustrated
1 Comment Add a comment
This solves the problem
-
Could it be a caching issue? What happens if you SHIFT+refresh in the browser?
-
Inappropriate?Nope, it didn't help.
The real problem is that when I edit that mockup and save it again it shows the right one, but if I visit the same page couple of days later it again shows the older one. I tried it in IE 8.0, Chrome and Firefox 3.5.
I’m confused
1 Comment Add a comment
This solves the problem
-
that's very strange. I'll take another look and might email you if I need help debugging.
-
Inappropriate?I might have found the problem. If a mockup is edited by couple users it shows last version of a image saved by first creator.
For examle:
User A - create mockup A nad png A,
User B - edits mockup and creates png B
All users would see png A unless they current User edit and save mockup in a current session. -
Inappropriate?Hi Giacomo,
I think you already had a similar issue and you solved it by making the macro insert a URL to the most recent version of the image using the URL with "downloadrev" and the latest image version number as the parameter.
Couldn't it be that the user is using an older version than the one with the fix ? -
Inappropriate?Hi Giacomo,
After installation of Balsamiq Version: 1.6.45 - 10/13/2009 12:45 (XWiki) everything is working and we don't have problems with mockups images in Wiki any more. Thanks for your time ;-)
I’m in very good mood :-D
EMPLOYEE
