-
Suggestion
-
Resolution: Unresolved
-
17
-
1
-
Hi everyone,
This is Sunny from the Confluence team. We know the DIV macro functionality has been critical to everyone here in formatting and configuring pages. As my colleague mentioned above, we have announced the deprecation of this macro March of last year. For transparency, after recent further discussions internally, we are currently still set in our decision to not include the DIV macro in the new editor when balancing performance of the editor vs the percentage of DIV macro users.
Thank you for your continued feedback. We have updated the status to reflect our current decision on the DIV macro, and we will provide any updates if we are able to include the DIV macro or additional similar functionality into our roadmap.
Best,
Sunny
Confluence
The Div macros will be removed as announced in: We're cleaning up the macro browser
Div macros contains some helpful features for content customisation and even workarounds:
eg. Removing links/disable links on pages as a workaround for this missing feature: CONFCLOUD-36736: Selectively Disable Attachment Preview
There's currently no alternative method at the moment for either features.
- is caused by
-
- Gathering Interest
- is cloned from
-
- Gathering Interest
- is related to
-
- Gathering Interest
- mentioned in
-
Page Failed to load
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
[CONFCLOUD-65774] Div macros removal feedback
We really need a DIV macro. My organization is moving from server to cloud, and this is going to be a huge gap for us that we're going to have to fill using something other than Confluence.
We counted on Confluence to allow us to have different classes of div to have content publish in different ways depending on how it was imported into our publishing tool.
Some div classes are conditioned to only show in PDF output, while others are conditioned to only show in HTML output, while others are conditioned to never appear in any output. (These are used for providing internal instructions for those who will be editing the document.)
We collaborated across all of our Engineering department on these documents in Confluence. The bare-bones Cloud editor is a crappy replacement for what we have been accustomed to on server.
Not providing any kind of alternative for this functionality is really frustrating, Atlassian. Please give us SOMETHING we can use.
Not offering a replacement for this seems pretty irresponsible on Confluence/Atlassian's part - not surprised though with how they've destroyed Bitbucket (we're moving to Github).
Our company was using div tags to filter content by customer. Our export scripts could then filter content by what's in the div tag class. For example, 3 tags we had were:
- Noexport (internal content-- no customer gets it)
- Boston (Boston [customer] specific content. We had a number of similar tags.)
- EU (European Union content, which doesn't apply to other regions. We had a number of similar tags for other regions.)
In our export script, it would filter out content based on tags that the exporting user chose, based on the customer. This meant that one page could serve many customers.
We would like something similar, effectively to label content by who should see it.
This seems to be the only way to control the PDF output for particular pages - it is ridiculous that EVERY page must output in EITHER Landscape or Portrait and that the insertion of Div tags seems to be the only ay to control this on a page by page basis.
Please do not remove useful features that people rely on to work around the shortcomings of the product
Like all the others said, this is a really bad choice. I have to say that the new editor is perceived very negatively overall in my company. The removal of this function is caused us a lot of issues.
Well this is annoying. I have pages that I can't reasonably export to PDF because headers and subsequent image get frequently separated by large amounts of whitespace.
I'll file this under my list of things that I assumed Confluence would support but that aren't even being considered for implementation.
Increasingly my perception is that Confluence is not being sufficently invested in.
Please bring back or provide alternatives.
These are blockers for us to move/migrate Confluence Cloud.