Hi Bob

Thanks for the quick reply. we've created CONF-26003 to track the specific issue of setting the html-migration plugin to disabled by default.

Thanks. No, its not resolved and continues to be a major problem for people upgrading to 4.x. Coding wise it is simple enough to change to disabled. I suspect it was just an oversight on the original implementation.

Hi Bob

It sounds like this issue is resolved, but we've created a improvement request for you to see if Confluence can be shipped with the html-migration plugin disabled by default.

Thanks.

Not sure what you mean by solved? I looks like you enabled the unsecured html macro which will make pages work, but its use cannot be controlled.

Hi Bob,

sorry, I was on the wrong track, my issue was solved as shown in screenshot. Thanks for you help!

Michael

hi Bob,

that's what I did:

• html-migration is enabled
• edit a page and insert html code via "Insert Wiki Markup"
• result is shown in html_1.png
• html-migration is disabled
• edit a page and insert html code via "Insert Wiki Markup"
• result is shown in html_2.png

My question now is how can I after disabling the html-migration option bring Confluence to something like a refresh to get all existing html macros to work?

Once the macro gets migrated, it can't be unmigrated. Can you copy the body and use insert wiki markup to create a new macro? Note that the html2 macro provided by the plugin is equivalent to html but will not be affected by this. I will be releasing a new 4.x specific html plugin in the near future as well.

We also face that issue after migration from 3.5.13 to 4.2.8 in test. When disabling the html-migration module it works for all newly created html macros. But how do we get the exiting to work again? Thanks!

The problem is that on 4.x, the Atlassian supplied HTML macros system plugin ships the html-migration module enabled. This should be shipped disabled. The workaround is to have the administrator go in and manually disable that module. Please fix this as it causes problems with anyone installing the plugin until they find out about the work around.