|
[
Permlink
| « Hide
]
Mark added a comment - 05/Feb/08 06:41 PM
This is not a minor bug for a company like Adobe. Being unable to properly display multimedia assets in our public facing wiki sites is creating some big problems for us. Can someone please advise on a timeline to fix?
This has also been noticed by others on the Confluence User mailing list:
http://forums.atlassian.com/thread.jspa?forumID=96&threadID=23076 We're hitting this problem, as are several of our clients with highly customised wikis
We have raised the priority of this issue and am currently considering it for scheduling into our next point release.
Dave,
Thank you very much. This is a very critical fix for us at Adobe. Can you provide a patch for us to test, and to use to move forward with our upgrade to 2.7.1, and to fix our external wiki that we already upgraded to 2.7.1? Thanks,
Garnet,
GIven that this is a regression that is causing issues for a fair number of our customers, we have scheduled this issue to be fixed in our next point release. We cannot say at this stage whether the fix can be offered as a patch. We will update you on this once we've come up with a fix. Please be assured that we are currently looking into this issue. Cheers, This is a bug in our renderer library: RNDR-24. The new version of the renderer library should drop into Confluence 2.7.1 and fix the problem.
1. Stop Confluence Fixed in stable and trunk by upping to new version of renderer.
Hi Mark,
That's odd. I just double checked the fix and it definitely works for me. I have clarified my comment above to make sure the procedure for replacing the jar is clear. Please check the html produced by Confluence to make sure the fix has gone in correctly. If the html contains <param name", then the fix has not been applied correctly. If the html contains <param name=" then the fix is applied correctly. (Note, the difference is the =). If the html does not have the broken param syntax and your swf files are still not loading then you must have a different problem, which may apply to a smaller subset of browsers. If so, please raise an issue at http://support.atlassian.com Cheers, Don,
Could you please specify the path to the atlassian-renderer-3.*.jar Thanks, Lily,
For a standalone install confluence-2.7.1-std/confluence/WEB-INF/lib is the correct location. Did you remove the existing confluence-2.7.1-std/confluence/WEB-INF/lib/atlassian-renderer-3.17.jar ? Lily,
Please check which version of atlassian-renderer is loaded in your classpath. You can see this by going to http://confluencebaseurl/admin/classpath.action Great to hear that the problem has been solved ! Thankyou Confluence Developers for addressing this issue promptly - wonderful work !!!
Ivan Would there be any issues with using this jar file with Confluence 2.6.2?
Lily, no it hasn't been tested against Solaris.
David, there could be issues using it with Confluence 2.6.2. If you can, I suggest upgrading to 2.7.1. Otherwise please contact support.atlassian.com and they will help you. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||