I was unpleasantly surprised, that all my macros have stopped working after moving to Confluece 4.0. There is no options "Output format - Wiki markup" anymore.
What should I do? How to work it around? How to call a system macro in my XHTML (now) macro?
Thanks.
This should work:
## @noparams <ac:macro ac:name="info" > <ac:rich-text-body> $body </ac:rich-text-body> <ac:macro />
---
And then set the macro as "Escaped".
Just trying to understand your question properly, Alex - so you have a macro which, when rendered, includes in its content, an {info} macro?
Does your macro have a body? Is the contents of the {info} macro hard-coded, or configurable by the user?
If you want to convert wiki markup into XHTML, you can get a com.atlassian.confluence.content.render.xhtml.Renderer bean injected into your macro class, and then use that to convert a {macro} string in wiki markup into the corresponding rendered XHTML.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Sue - Confluence 4.0 is fairly unique in the scope of changes to Confluence in that we completely altered the storage format of Confluence from wiki markup to XHTML. In honesty, Confluence 4 is probably the biggest change to Confluence ever, and it's probably unlikely that things will change this much again.
We have lots of resources to help plugin developers prepare for Confluence 4.0 upgrades. This page is a good starting point: https://developer.atlassian.com/display/CONFDEV/Preparing+for+Confluence+4.0
If you have any specific questions or problems, please feel free to ask questions on this site and our community can help you out!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
i am also having issues with all of the macros, in the theme plugin that I developed, not working in Confluence 4.0. What is the quickest and simplest way to resolve the issue without having to re-write the code? My client is concerned about the cost of upgrading the theme plugin every time a newer version of Confluence is released. Are there always this many changes when a major release of Confluence is re-leased? What are your plans for the future? Will there be more major changes to how macros are developed?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, I found a part
it's my new body of the macro:
<ac:macro ac:name="info" >
text text text
<ac:macro />
it works partly - it draws a blue panel, but without the text inside. Need help.
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.