Software update, and what it means to users
Added a Rich Text Editor.
Yeah, I know. About time, huh?
News post outlining the details with other associated links.
What this means to the user-
Say you used Word to export to html so you could upload a chapter. You'll notice that the display is actually showing all the extra crap code that Word tends to insert, which a core function file not only cleans out, but the archive doesn't allow.
To fix this, the user simply needs to edit the story, select the chapter in the dropdown, and then click edit chapter. That's it.
This allows the RTE to properly clean OUT the extra code which the archive doesn't support. This also preserves all that formatting that was there to begin with.
This is the most typical issue I've seen with this new update, is how it garbles the visual appearance of a Word html insert.
For the clean up project
What this means for ME, is that I'm going through books and buffy subdomains where I've already repaired stories. I'm doublechecking that the repaired stories were not affected. So far, they haven't been. However, because I already fixed in the one subdomain, and am almost done with record repair in buffy, where there are newer updates (after I've gone through and fixed) with issues, I'm fixing those too, as I can.
It would be VERY helpful if for these newer story adds, if the users themselves simply followed the above instructions. Save me very much in way of time, and allow me to proceed with the db repair itself.
Finally, the stories which were posted with what we all know as the "wall'o'text", that's a user's choice. I'm not the site beta, I'm not fixing the records to make it so formatting choices are different and more palatable to the majority of us. That's on the USER, not me.
Yeah, I know. About time, huh?
News post outlining the details with other associated links.
What this means to the user-
Say you used Word to export to html so you could upload a chapter. You'll notice that the display is actually showing all the extra crap code that Word tends to insert, which a core function file not only cleans out, but the archive doesn't allow.
To fix this, the user simply needs to edit the story, select the chapter in the dropdown, and then click edit chapter. That's it.
This allows the RTE to properly clean OUT the extra code which the archive doesn't support. This also preserves all that formatting that was there to begin with.
This is the most typical issue I've seen with this new update, is how it garbles the visual appearance of a Word html insert.
For the clean up project
What this means for ME, is that I'm going through books and buffy subdomains where I've already repaired stories. I'm doublechecking that the repaired stories were not affected. So far, they haven't been. However, because I already fixed in the one subdomain, and am almost done with record repair in buffy, where there are newer updates (after I've gone through and fixed) with issues, I'm fixing those too, as I can.
It would be VERY helpful if for these newer story adds, if the users themselves simply followed the above instructions. Save me very much in way of time, and allow me to proceed with the db repair itself.
Finally, the stories which were posted with what we all know as the "wall'o'text", that's a user's choice. I'm not the site beta, I'm not fixing the records to make it so formatting choices are different and more palatable to the majority of us. That's on the USER, not me.