I just activated a new Confluence instance for a customer but the way it looks and performs now I cannot sell it, is it possible to opt-out until the product is stable and up to speed?
@Henry Snijders @James Walker
You can contact support to have the old editor enabled on your instance.
See the comment on CONFCLOUD-65695 for more details:
Hi all, Thanks for all the feedback on this ticket. Given the amount of requests we've started to explore what a potential quick win may look like to re-introduce this. That being said, we still can't guarantee a time frame for this - we will make sure to update this ticket as we know more on our end. In the meantime, if you have the legacy template available - which most of you should have - you can keep using that to create new pages and still keep using this feature. If you don't have that template, you can reach out to support and we'll be happy to enable it for you. Thanks,Avinoam
Hi all,
Thanks for all the feedback on this ticket. Given the amount of requests we've started to explore what a potential quick win may look like to re-introduce this. That being said, we still can't guarantee a time frame for this - we will make sure to update this ticket as we know more on our end.
In the meantime, if you have the legacy template available - which most of you should have - you can keep using that to create new pages and still keep using this feature. If you don't have that template, you can reach out to support and we'll be happy to enable it for you.
Thanks,Avinoam
Hello Henry,
Thank you for reaching out! It's disappointing to hear that your Confluence Cloud instance isn't performing as expected. I would recommend raising a ticket with the Cloud Support Team directly, so that they can have a look at your instance and confirm if there's not anything else that can be done to improve your performance.
When you ask if you can opt-out, can you let me know exactly what you mean by that?
Regards,
Shannon
Henry,
Please disregard, I see now in your title you want to opt-out of the new editor; I hadn't seen that specific bit in your summary.
You might be able to to use the old editor by clicking the + (plus sign) in the left hand sidebar and selecting legacy editor template.
If you have any other issues, please be sure to send the Editor team your feedback by using the feedback option from the menu when clicking on your avatar in the bottom left-hand corner!
Thank you for your understanding.
Hi Shannon, I have/see no option to use the legacy template. I understand that things change over time but don't throw away the child with the bathwater (dutch expression ;-) in other words keep the good stuff. The main problem I am facing at the moment is that all the pages that were filled with excel tables with let's say 10 columns are now displayed in portrait view, I can overlook only 2 columns, and when i choose full width I get 2 columns with more space. It is a pity that with all the broad screens nowadays I can show 2 columns. De facto all previous work in this field will become useless.. probably same goes with displaying jira filter content in landscape.. (not tried yet). I was showing the previous view to my customer and he was very enthousiastic but now I cannot convince him to use confluence and jira..
Thank you for confirming - then it is likely not available on the Cloud instances anymore, as we are rolling out the new editor to instances and fewer old features will be available.
Can you clarify exactly how these Excel tables are inserted in your page? I assume by Excel you mean that you've embedded Excel sheets into the Confluence pages, and we're not dealing with Confluence tables. Would you be able to confirm that?
Please feel free to share any screenshots of the problem in UI, if possible. You can edit your data to anonymise it if needed.
The whole new editor is trash.
Now if only there were an option like that for creating new templates. The new editor is really awful, and I can't create a full page template at all.
At this point, I'd settle for an option to copy an old template.
Actually, that's a feature I think would be useful even not taking this terrible new editor into consideration.
Or hey, how about allowing us to convert an existing page to a template... without an add-on? That would work for me too.
Seriously, though, Atlassian, this new editing experience is as horrible as the new Jira experience. Both should be scrapped tout de suite.
Things that are still (Feb 2020) unusable: - Images have fixed sizes, with no ability to render as their native size. Makes any image with text blurry
- Exceedingly limited set of colours.
- Tables are 100% width
- Random jumping of the cursor to the top of the page when editing
- Macro addition screen doesn't contain all macros, try adding a /panel some time.
- Linking to attachments not possible without copy/paste the link from the browse attachments page.
- Randomly invisible blocks (macros? who knows) in the middle of the document that you only find by drag-selecting and then deleting
That's a few things just off the top of my head. For all I know there are actually workarounds for these things, but the interface is so counterintuitive in most circumstances that finding the workarounds or "correct" way to do things is exceedingly time consuming.
I am also fighting with the joy that is the new editor, and I think I have found a nice workaround:
Until Atlassian notice this ugly hack and deliberately disable it we should be in business for a trifle longer.
It seems that someone is in love with the new garbage, alas
Sadly, there may be new confluence instances that do not have a trace of the old editor!
@Daniel_M @Michael_Abbott,
Please take the time to review the whole thread before posting outdated solutions/workaround.
As mentioned in my comment below, you can contact support in order to have the old editor re-enabled into your instance.
For more details please see:
1) The comment on CONFCLOUD-65695:
2) The article How we roll out the new editor in Confluence:
Will the legacy editor eventually go away? Yes. However, the legacy editor will likely still be around for a bit as we understand that existing content needs to keep working. With that being said, eventually, we do plan on moving away from the legacy editor. We’re actively working as we rollout to understand what the eventual sunsetting process will look like and we’ll be asking you for how you think it should work so we can make it as smooth as an experience as possible, with ample communications and change management supporting material. We sincerely hope that this post helps to better inform everyone of what the rollout process looks like. Please reach out with any feedback so we can constantly continue improving the rollout experience! Thanks!Avinoam
Yes. However, the legacy editor will likely still be around for a bit as we understand that existing content needs to keep working. With that being said, eventually, we do plan on moving away from the legacy editor. We’re actively working as we rollout to understand what the eventual sunsetting process will look like and we’ll be asking you for how you think it should work so we can make it as smooth as an experience as possible, with ample communications and change management supporting material.
We sincerely hope that this post helps to better inform everyone of what the rollout process looks like.
Please reach out with any feedback so we can constantly continue improving the rollout experience!
Thanks!Avinoam
I hope this help clarifying.
Cheers,Dario
Dario, I beg to disagree: Michael Abbot's solution is not outdated: is a solution that does not require someone to get in touch with Atlassian's support only to get the old - and MUCH BETTER - legacy editor back.The new editor appears to be one more of the half-backed "solutions" Atlassian throws in our laps. How a toolbar that take away the option to make a text monospaced, or that give me less text colors than before can be called good?
You guys should spend more time listening to the customers, instead of thinking about escuses.
My experience in attempting to do this. Firstly I was asked
May we know the reason as to why you wish to opt out of the new editor?Any changes that you are currently having issues with?
I re-explained my frustration and referenced this issue for background.
I got:
Thanks for sharing your thoughts with us! This kind of feedback is really important to us, so we can keep tracking what do our customers need. I'll definitely bring this up to our product team. With the new editor, we are aiming for a simpler design and WYSIWYG.We do have a lot of feature requests with regard to the new editor and our product team is working on improving it. If you're interested, here's Confluence Cloud editor roadmap page that you can watch [ url deleted, for some reason putting it in causes this message to fail to post]The aim here is to give the transparency of the feature that will be rolled out on the new editor to our users. The old editor will soon be deprecated to make way for the new editor so the rolling back is not an available option.If you have more question and would like to communicate directly with our Product Manager, you can drop your feedback here on our community page:[ url deleted, for some reason putting it in causes this message to fail to post]Having said that, we definitely understand these issues have a major impact on you and your teams. We'll review it with our product management team. We need to assess with them on any possibility if we can review the rollback of the new editor for you in the interim. If we do go with this option which is to roll back to the old editor, we are just merely postponing the actual roll back until the cutoff date. The new editor will eventually fully roll out to all and there would no longer be a way to defer.As such, we will need to confirm again the following details just to ensure we are aligned. We would also like to get an understanding of the exact business impact this one feature loss has on your instance. Could you share with the missing major functionality that you have with the new editors that are blocking you from performing tasks and hugely affecting your business? Appreciate if you can share with us, in detail, how can we do better with the new editor and how can we improve to meet your business case? This is just additional feedback around the impact and severity this is having on your teams/business as we want to review this with our product manager and the team and see if there's anything we can help address for your case here.We do appreciate all your feedback here. The next steps are that we will compile the feedback and book in time to deliver/review with our product manager to assess. We will then follow up with you.
Thanks for sharing your thoughts with us! This kind of feedback is really important to us, so we can keep tracking what do our customers need. I'll definitely bring this up to our product team. With the new editor, we are aiming for a simpler design and WYSIWYG.
We do have a lot of feature requests with regard to the new editor and our product team is working on improving it. If you're interested, here's Confluence Cloud editor roadmap page that you can watch
[ url deleted, for some reason putting it in causes this message to fail to post]
The aim here is to give the transparency of the feature that will be rolled out on the new editor to our users. The old editor will soon be deprecated to make way for the new editor so the rolling back is not an available option.
If you have more question and would like to communicate directly with our Product Manager, you can drop your feedback here on our community page:
Having said that, we definitely understand these issues have a major impact on you and your teams. We'll review it with our product management team. We need to assess with them on any possibility if we can review the rollback of the new editor for you in the interim. If we do go with this option which is to roll back to the old editor, we are just merely postponing the actual roll back until the cutoff date. The new editor will eventually fully roll out to all and there would no longer be a way to defer.
As such, we will need to confirm again the following details just to ensure we are aligned. We would also like to get an understanding of the exact business impact this one feature loss has on your instance. Could you share with the missing major functionality that you have with the new editors that are blocking you from performing tasks and hugely affecting your business? Appreciate if you can share with us, in detail, how can we do better with the new editor and how can we improve to meet your business case? This is just additional feedback around the impact and severity this is having on your teams/business as we want to review this with our product manager and the team and see if there's anything we can help address for your case here.
We do appreciate all your feedback here. The next steps are that we will compile the feedback and book in time to deliver/review with our product manager to assess. We will then follow up with you.
This makes the whole experience more frustrating. Perhaps your support people need to start talking to each other.
The workaround of using an old page and copying it doesn't work for importing content, and hides the number of people who are actively unhappy with the new editor.
@James Walker ,
I have found your support ticket and I am leaving a comment for the SE in there.
However, just to clarify, do you still have the possibility to create new pages using the old editor or not at all?
I am asking because the confusion here can be due to the fact that having the old editor enabled is one thing, while opting out from the new one is another different thing, and in the support ticket you are asking for the second one.
In addition to the above, the #1 pain point for me are the blocks of text, the page layout sections. This is a must-have feature; I use it in every single page I create/edit, and it was removed in the new editor. The nagging prompts to convert my old pages to the new editor (and break them) make me worry for the day when I will be forced to the new editor (or more likely a new documentation solution).
Worth noting that in the 2 years since this comment was originally made the only thing that has changed is that tables can now vary their width, to one of 3 fixed widths, not to a size that perhaps makes sense to the page creator.
Most importantly:
- Images are still unusable if they contain text
- The linking of attachments is still the same very poor experience
- Editor is still very finicky with hidden content and forcing the cursor to strange places.
More things the "new and improved and generally so much less enjoyable" interface can't handle: tables inside table cells.
It looks like you're new here. Sign in or register to get started.
