Kelvin Hill_dvc7sv Specialist

@Tom CrowleySnap! I installed a plug-in to do the same thing. Can't remember now if there's more than one available. After allowing it to run for a while, it revealed little of interest, so I uninstalled it. As you predict, this will undoubtedly be lauded as another must-have feature. In truth, it's a nice-to-have bonus…

@Tom CrowleyI believe I noticed it on Monday, but it isn't of use to my company since we don't make our online material publically accessible. As such, I simply ignored it.

[MODERATOR NOTE: post edited to comply with Atlassian Community Rules of Engagement] @Joss deWytt, welcome. I'm intrigued by your "Time to level up!" comment. Were you suggesting that the many naysayers here should embrace the new editor as an advancement (i.e., the next level) of an editor around which oodles of serious…

[MODERATOR NOTE: post edited to comply with Atlassian Community Rules of Engagement] Everything Atlassian plans to do with Confluence Cloud is included in the Roadmap. Here is the link to the new-editor roadmap: https://confluence.atlassian.com/confcloud/confluence-cloud-editor-roadmap-967314556.html Regarding adding…

I'd also like to harp on about an issue I've already raised several times for which I have failed to get any traction at all. Everyone who exports pages to PDF will eventually face an insurmountable problem with the new editor. Why? Because new-editor content is pre-processed before being sent to the PDF-export engine, and…

I submitted a bug report yesterday about how it is possible to insert a Code Snippet macro into a panel macro (Info, Note, Success, Error, Warning), but only if you embed it within a list within the panel. If you attempt to add a Code Snippet macro directly into the panel (without a list), it simply drops below the panel.…

I'm doing my level-best to work within the startling limitations of the new editor, but there are some features that simply won't cooperate, and Atlassian isn't offering any suggestions or even acknowledging that there's a problem. All I need is a workaround. Perhaps you have found one. One such conundrum is with images.…

@Shrey @Avinoam While wishing to avoid revisiting a dead issue, I feel that Atlassian has missed a significant and easy win by failing to include a modified version of the DIV macro. So many issues like the one above could be resolved for serious editors by including a modified form of the DIV macro. Here's how it could be…

@Tom CrowleyI'm sure that'll be it, Tom. In the legacy editor, when we wanted to selectively modify the appearance of a macro or element in the PDF (including modifying one specific instance of a macro rather than all of them in the page), we used to enclose it in a DIV and apply a unique class to it. We were then able to…

@Tom CrowleyWe highly customise our PDF exports to include corporate branding and resolve a slew of undesirable formatting settings included by default. I apologise if you already know what I'm about to explain. While using the legacy editor, you can use Google Chrome's Inspect option to show the CSS classes and IDs added…

Duplicate post removed. The site was laggy and my post didn't appear after posting, so I posted a second time.

@Tom Crowley I've been busy trying to find ways to customise PDF output from a Fabric Editor page. It turns out that the export-to-PDF process for Fabric Editor pages is little more than a fudge. Earlier this afternoon, I had a one-hour Zoom video-conference with a Confluence Cloud Support Engineer in Bangalore to…

I hope it's OK to go off-topic here rather than post to the predecessor of this post. @Shrey @Avinoam The legacy macros were introduced into the Fabric editor over two weeks ago, and, after just checking, I see they are still present. We were informed that these useful macros were introduced in error. If so, why has this…

@James Dellow Great suggestions, thanks! I suspect the API is the way to go. I stumbled upon this suggestion in the Confluence Server questions: https://community.atlassian.com/t5/Confluence-questions/how-to-get-full-content-body-html-using-confluence-REST-API/qaq-p/710532 Thank you for your kind help.

@James Dellow I appreciate your suggestion, thanks. I also appreciate your explanation, thanks again. Sadly, neither actually helps me, sorry. We have been customizing the PDF-export process for many years using the tools described in the link you shared. That all works fine and dandy, but the unresolved problem we face…

@Tom Crowley @Jeannine Hooper-Yan Further to Tom's comment, I interpreted Jessica's LIKE as a nod and a wink to the functionality making a return in the near future. As a result, I liked it, too. #opaque-communication

@Jonno Katahanas Thanks for the clarification. Such feedback is genuinely appreciated. You're one of the good guys. It was evident that the Expand macro had been cosmetically tweaked, but I guess that didn't even register in my brain's appreciation zone because making any macro prettier is right down close to the bottom of…

If anyone would like to see the Status macro being used in a way that Atlassian wasn't expecting, check it out here: https://drive.google.com/open?id=1vgnxfKal8vbK0PpJ0JzD65y7fMCGkH4A If Atlassian doesn't want us to use legacy macros in the new editor, why are they still available? I wanted to share an animated GIF, but I…

@Jessica Taylor Thanks for the update. It's great to hear from you again. I hope the holidays were happy. We have been using the Expand and Status macros for a long time in the legacy editor. Aside from the cosmetic changes to the Status macro, has anything else changed? We haven't noticed any new functionality, so it…

@Tom Crowley You make a fair point, but I doubt the inattention to detail and the seeming disinterest in offering clarity is a matter of decency. I'm sure we can agree that decency is a personal attribute, and I suspect there is nothing personal about this trainwreck. What's going on here smacks of rigid enforcement of…

@Rory Apperson A fast typist? You and me both (but only if a fairly consistent 70 wpm is considered relatively fast). Or rather I used to be, but the latency I'm seeing in the Fabric editor (especially in table cells) has largely put paid to my touch-typing. I may as well type with one finger. And yes, a few extra…

@Tom Crowley That's how we insert content links, too. We don't have a problem with it because we achieve the same end result with a little extra work. The same cannot be said of the essential macros that have been removed, reinstated, and stand to be removed a second time. We cannot achieve the same end result without them…

@Avinoam No need to respond if you're too busy. @Shrey has already admitted that the useful legacy macros were re-introduced in error, here: https://community.atlassian.com/t5/Confluence-articles/2019-All-Wrap-ped-Up-Like-a-Present/ba-p/1235288/page/6

@Shrey I have liked your comment for its honesty despite my being thoroughly disappointed by its content (as, I'm sure, are many others). You said, "We are going to need to turn them off once again." I don't wish to point out the obvious, but every hour that they erroneously persist in the product is another hour than an…

I have just posted this message to another discussion thread: https://community.atlassian.com/t5/Confluence-Cloud-discussions/Discussion-page-for-users-affected-by-the-editor-change/td-p/1222979/page/2 I'm saddened to report that I'm convinced that the welcome availability of deprecated macros in the new editor is all a…

@Tom Crowley Oh, no! I'm saddened to report that I'm convinced this is all a horrible mistake. Check out the following page: https://confluence.atlassian.com/confcloud/section-macro-724765280.html (which was last modified on Dec 31, 2019). It says the SECTION macro has been removed, but if you check the new editor (as of…

@Robert Lauriston You ought to report this as a bug. You'll also need to be sure you indicate whether it is an issue with the legacy editor or the Fabric editor. There are many hundreds of active/open issues associated with Confluence editor bugs, but nothing will happen without a Jira. All the best!

@Tom Crowley My sweet delight at discovering that I have access to the deprecated macros in the new editor is fast turning sour. Thinking about Neha's response, I am concerned that the availability of the old macros in the new editor is a bitter mistake. It sounds like the intention was probably to render the old macros as…

As @David Gregory has suggested, it sounds like Neha is referring to pages that have been migrated from the old editor to the new editor. That would make sense, although I don't yet have access to the migration tool. Does anyone? Also, Neha's response does not address the issue of being able to insert deprecated macros…

@Tom Crowley It was kind of Neha to respond, but her reply sounds like she hasn't tested the editor for herself but has asked someone else for information. How can a macro be removed yet be carried over at the same time? I wasn't aware of the old macros being available in the new editor until you pointed them out…