Make WordPress Core

Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#30207 closed defect (bug) (invalid)

Post Editor - Inconsistent switch back "Text" tab after "Save Draft"

Reported by: sujaysarma's profile sujay.sarma Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.0
Component: Editor Keywords:
Focuses: ui, administration Cc:

Description

If you are in the "Visual" editor tab when using the post editor, after clicking the "Save Draft" button, the editor randomly switches to the "Text" (html) tab.

WordPress: 4.0
System: Windows Server 2012 R2 / IIS

Change History (9)

#1 @azaozz
10 years ago

  • Keywords reporter-feedback added

Can't reproduce in 4.0 or trunk. A good way to test which editor is selected as default is to run getUserSetting('editor') from the browser console. Can be run on any admin screen and before and after switching editors, etc.

This setting is per user, per site. One way this might happen is if you're logged in from two different browsers at the same time, or two different people are using the same username/pass. Then if the editor is switched to Text and the post is saved in one browser, the other would get the same setting on saving/reloading the Edit Post screen.

Last edited 10 years ago by azaozz (previous) (diff)

#2 @sujay.sarma
10 years ago

  • Severity changed from normal to major

It says "tinymce" when in Visual mode and "html" when in Text mode.

This is a consistent repro for me now. It used to be at random a few days ago. Every single time after I hit "Save Draft", I get dropped into the html/Text view of the editor. This has got to the point of being so frustrating that I am having to use some other app to create the content and then copy-paste instead of doing it in-screen!

#3 @azaozz
10 years ago

This setting (together with few others) is stored in the wp-settings-# cookie, where # is your user ID. Perhaps there is some inconsistency in saving/updating that cookie. Good way to troubleshoot this is to delete any cookies starting with wp-settings- from your browser and try again. Alternatively you can delete all cookies for your site (note that doing this will log you out).

#4 @sujay.sarma
10 years ago

I had two such cookies. One for / and one for /wp-admin. Both were set to the html editor. I cleared the cookies and it worked for a while. After about half an hour or so the strange behavior started up again and remains consistent. Behavior is reset when I clear the cookie. So is this triggered by some kind of a timing issue?

I forgot to mention in the original post -- I am using Google Chrome as the browser. Don't ask me to try another one as this is the one I need to use.

#5 @johnbillion
10 years ago

  • Severity changed from major to normal

Thanks for the report Sujay.

Do you have any other sites on the same domain name but at different paths? eg. example.com and example.com/site1 or example.com/site2?

Is WordPress installed in a subdirectory of your site? eg. example.com/wordpress/wp-admin?

Is there anything else about your site configuration that is not a normal configuration? Do you have a persistent cache? Do you have any browser extensions installed which might be interfering?

Finally, and most importantly, can you reproduce the issue with all your plugins deactivated and with a default theme enabled?

#6 @sujay.sarma
10 years ago

Hello,
I have other WordPress installs on the same server - each one running in its own IIS app pool and IIS website. Each install also runs on its own domain. WordPress is the primary and only CMS for all of these websites and runs off the root folder (/) for all of them.

IIS is configured at mostly default settings, except for the changes for PHP handlers and what changes WordPress does via web.config.

Browser extensions - none

Other themes and plugins - the only theme I have is "Visual" (i.e., https://wordpress.org/themes/visual). I dont have the OOBE themes (Twenty *) installed. The only plugins I have installed are JetPack and Akismet.

#7 @helen
10 years ago

Is this still an issue?

#8 @sujay.sarma
10 years ago

  • Resolution set to invalid
  • Status changed from new to closed

I have since upgraded to WordPress 4.1 with JetPack 3.3. This is no longer an issue. Do go ahead and close the bug.

Thank you for checking back!

#9 @helen
10 years ago

  • Keywords reporter-feedback removed
  • Milestone Awaiting Review deleted

No problem, thanks for taking a look.

Note: See TracTickets for help on using tickets.