Another New Editor complaint! Atlassian owes us an apology!

[Shawn Connelly]

I had come to the Atlassian forum hoping to learn that my untenable difficulties with the new Confluence editor were my error, but now I understand that this edit is truly a ridiculous mess.

Many of my co-workers are running into multiple issues with the new editor, since it became the default editing in the past two weeks. I have instructed them to use the old editor, but now I am very concerned because the old Blank Page icon now says that it's going away soon! When? I have no idea because even the warning was ineptly worded. Doesn't anyone at Atlassian check their work? It says, "In the upcoming weeks, the old editing experience will no longer be available as a..." ... what? If the warning wasn't so wordy, I'd know when it was going away!

Serious! I hope Atlassian is planning to hold off on deprecating the old editor because the new editor is almost unusable! Repeat, UNUSABLE!  

---

Some threads are calling for the product manager involved to be fired. Well, that's pretty severe. LOL

The real blame should be placed on the leaders who decided in the go/no-go decision to launch this inept editor. It would be more than just a single product leader that was involved in that stupid decision.

At the very least, Atlassian should issue a public apology for this gross lapse in judgement, return to the default old editor, and don't dare force a change on their paying customers until they can answer YES these three simple questions:

1. Is the new editor better in all respects?

2. Does the new editor solve a problem or problems?

3. Switching to the new editor will not cause customers any pain, with respect to  compatibility issues with the old editor?

How about it, Atlassian?

[Aleš Laňar]

Hello Victor,

I looked at screenshots. Do you have any login utils? Something like kerberos (you have to set FF for using kerberos) or any plugins in FF?

If you have plugins on FF browser, try to reinstall it. If it working on other browsers, maybe is problem in build of browser. I have a lot of problems with jira and confluence when somebody had a one Chrome build... So try CLEAN installation or upgrade you current version or disable all plugins in FF

[Steven F Behnke]

Could you post a screenshot of the error using the upload arrow in the comment field? You keep saying "not registered" but I can't remember ever seeing an error like that in this system.

If the issue wasn't tested on other machines with the same user account, this in most likely was a client machine issue. Creating a new 'Local User' on the machine gives you new cookies, browser configuration data, some temporary stuff, etc.

[Victor Urlapov]

Hi All,

Here`s the screenshot: http://gyazo.com/2c148aedf5b14cfea232e03d894a2b1e
We have russian localization pack installed. The translation is: errorMessage: "You are not registered. <a href=\"/login.action\">Register</a> here and try one more time."

It seem to be local machine problems, but this is quite strange that such thing happens only for Confluence.

[Deividi Luvison]

Hey Victor,

Can you ask to that user to check his browser setting in FF?

One idea is to un install firefox and then install it again, during the installation select the option, import setting from Google chrome.

If the problem disapears means that it was some browser setting/cache, if not, let me know :).

Thanks and Regards,

David|Confluence Support Engineer

[Victor Urlapov]

Hello, David.

Thanks for the answer.

User tried to re-install Firefox again and it did not help. The same behaviour persists with a small difference: if user intentionally goes to the ...login.action page and logs in, Confluence works for this session. But if he closes the browser and starts it again, he gets the message described above and has to go intentionally to login.action page again. Following Conf links from email, for example, does not work if he even passed through login.action page few moments ago.

We`ve tried another thing: created another local user on the machine and installed a clean FF for this user. As a result this did help and Confluence was working fine. Allowing to maintain session and allowing to work after browser was closed and started without intentionally visiting Conf log-in page.

MB there were similar situations you`ve seen or heard before regarding such Confluence behaviour?

Thanks!

[Deividi Luvison]

Is it possible to post a screenshot of that error so I can a better picture of what you are seeing?

I never saw that specific error before :(.

Thanks and Regards,

David|Confluence Support Engineer