Story editor showing raw html

[Thundercloud]

It seems like when you edit old stories you after the server upgrade get a look at the raw html of your story. Being able to fix the html is actually a good feature...but without the whitespace it it is kind of hard on eye for longer stories.

If we could get the option to switch between fixing the html and more user friendly edit mode it would be lovely.

[BronxWench]

I’m not able to replicate this. My editor is opening in the RTE without raw HTML showing for documents originally written in and uploaded from Word. I’m tagging @DemonGoddess and @manta2g regarding this.

[DemonGoddess]

I tried opening chapters in several old stories, and cannot replicate the issue.  Have you tried a force refresh since all the changes, and deleted your browser cache?

[Thundercloud]

I will see if clearing the browser cache can fix it.

[Thundercloud]

No luck with clearing browser cache. The javascript control in Firefox show the following error

Quote

Blocked loading mixed active content “http://www.adult-fanfiction.org/globals/ckeditor/ckeditor.js” ucpa.php

I suspect the problem might be that you are trying to load http data from a https connection. If you are using Chrome you won’t realize the problem since that browser has switch to https as fallback but other browsers will warn or block the request due to security reasons.

[DemonGoddess]

I actually think it may be something as simple as clearing your cookies.  With the migration, cookie tweaks and a few other things, cookies definitely need to be reset.  As to the blocked loading, you can fix that in your browser for the time being.

[Thundercloud]

Please fix the code so you load https//www.adult-fanfiction.org/globals/ckeditor/ckeditor.js instead of http://www.adult-fanfiction.org/globals/ckeditor/ckeditor.js    

It cannot be much work to search the code for all instances of http:// and fix these (unless it is safe content that only is available through a http site), and it is work that should be done sooner or later.

The restriction about loading mixed content was introduced for a good reason since mixed content is vulnerable to man in the middle attacks when the http connection be used to introduce tainted code into what the user believe is a secure connection. Technical savvy users knows how to disable the mixed content checking but these people also know why mixed content checks was added in the first place. People who are not web developers should not have to deal with things like this.