Hi azelenko,
I hope we're not getting ahead of ourselves here, but.....it looks like the 404 issues may now be fixed?
At least, in our dev Confluence instance, it seems that we are now able to successfully insert, edit & publish our macros using the new editor (and the feature switched version of the default Edit Macro dialog, that includes a <textarea> for editing the macro body).
(We're using AP.confluence.getMacroBody() to fetch the macro body when rendering, by the way).
Are you able to confirm? If so, this is great news.
Unfortunately that is only half the job done: we are still unable to access macro parameters (which is critical for our apps to function correctly). The AP.confluence.getMacroData() API is still returning undefined.
Can you confirm if the getMacroData() API is still being investigated/fixed to work with plain-text macros? (in particular, to provide access to macro parameters).
It is certainly starting to feel like we might finally be nearing the end of what has now been (for us) 7 months of worry and frustration with the new editor rollout. Hoping you can provide us with some good news.
Kind regards,
Scott
With custom macro parameters editor we see the same - macro body does not get saved in new editor calling AP.confluence.saveMacro