Wow, that video is a good example of a definite bug in the image implementation. Atlassian folks, is there an existing issue for this? If not, what is the best way for @Kevin Hill to report this bug?
How about @Pahniti Tosuksri and his linkable image request? There just has to be an existing bug for that.
I tried hunting down appropriate Jira issues for Confluence Cloud and was unable to, but perhaps someone else can find the right terms to use:
I'm glad you deleted my comment, it finally stopped the flood of emails telling me someone had clicked like just because I was asking for the option to expand-all before printing or exporting to PDF.
Just impressed Atlassian went an entire update without feeling the need to remove useful features. Bold, Italics and Underline are next to go I presume?
Our team has a very hard time with the "new" editor. Its a no-go that we can't add images next to each other any more. I just hope that the old editor stays as along as all features are done for the new editor. Atlassian should look at large confluence spaces of their loyal costumers then they would see they don't need to trivialize things, it used to be a production tool for professionals.
Its also very frustrating to see so many essential but trivial features such as "Admin View" and "Copy Permissions" go to premium.
@Jessica Taylor You just don't seem to grasp that you've removed a lot of features from a lot of different user types. It's not like you've just removed one chunk of functionality that affects a single user set that oh well, boo-hoo, sorry, go somewhere else. That would be understandable, although still not necessarily acceptable, because it would indicate a clear directional shift in the software. "We used to do X, now we do Y. If you use us to do X, well, that's a shame. Good luck with the migration." It would be a real crappy move, but it is purposeful and shows intent.
What you've done is just pare down a lot of features so that only the most basic of users are unaffected in some way (you've ruined image handling, for example - it's got to be a pretty basic page that isn't affected by that). There doesn't appear to be any direction for the software other than vague "improvements".
And instead of interacting with people on here, you just put a notification on our actual Confluence instance to lure us here so you can boast about your one and a half updates for non-premium users (hence the sudden resurgence in commenting).
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. Since lists and Code Snippets are unrelated, that must be either a bug or an oversight, so I reported it. My guess is that the developers were specifically asked to include support for Code Snippets within lists within panels, and no one considered any other scenario.
What suprised me, however, was that the support person responded to my ticket and simply advised me that Code Snippets are only supported in panels when they are are inserted into a list sitting within the panel. To me, that's like saying you can only sit on a chair if it has a cushion on it. If there's no cushion, you can't sit on the chair.
@Sue Wright - Status in the new editor is no longer a macro but rather an inline element instead of the previous status macro. You can use it by either typing "/status" into the page anywhere or by going in the top menu to the + and choosing status to insert.
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 we have no visibility of the resulting HTML tags, classes, and IDs being sent for conversion to PDF.
That is a significant issue because no one can customise a page element unless they know its HTML/classes/IDs. The new editor translates some elements to equivalents used in the legacy editor (for which we already know the HTML tags or can identify them by viewing the page source); however, for elements for which there is no legacy-editor equivalent (e.g., the new-editor Note Panel), we have no way of identifying what tags, classes, or IDs to use in the PDF stylesheet to customise it.
The only way around this problem is for Atlassian to provide some means of reporting the HTML being sent by the new editor to the PDF-export engine (after it has been pushed through whatever conversion process is now used). This isn't a huge ask; after all, a process is already in place to convert the page content and feed it to the PDF-export engine. All we need is a link to display the content (i.e., an export-to-PDF style option that displays the source to screen rather than sending it to the engine). We could then harvest all the tags, classes, and IDs necessary for customisation from that.
122 comments