For us, I found first writing the text in MS Word then ‘saving as’ out to a UTF-8 text file, then pasting THAT text into WP works best. Or, you can add a filter to the functions (or roll your own plugin; or use old plugin) to basically turn off some of the conversion funk in WP boxes.
No worries. I’ve been doing webdev since 1994, using WP since 2004, and have been managing our web servers since 1996. 🙂
So, we run a lot of high traffic news portals as well as our company B2B sites. We run WP with server side caching, and so well aware of WP behaviors. So, a ‘static’ page still has cookies loaded via PHP, and content is still added via the handler even with so-called static pages. A normal site visitor would not see an edit button. This is why you don’t see edit buttons for TIME magazine (running on WP VIP platform).
We’ve never had this issue on our sites, so I guess I was trying to give you some level of comfort there.
Personally I find injected ‘edit with pagebuilder’ buttons annoying in WP, and have always thought so — but I have this issue with all platforms going back to first version of Canvas (to date myself a little bit more).
So, to chime in – it *would* be nice to have option to remove pesky “edit this page” items when logged in for the admin user, even if via a filter hook in t he WP API.
I guess they did give you possible solution for that, so if ultra paranoid that would be the best way to go. Still, I’ve never seen a client make note of a “why is there and edit button on the photo on your home page …”
Or, put yet another technical way: proper caching plugins make a static copy of the ‘public’ DOM/render, which would be considered the rendered page with a ‘subscriber’ or ‘anonymous’ role/cookie level; not an admin level state. So, technically unless the cache method is ‘misconfigured’ — a static version of a page/post would never render with the user role/cookie state of superuser, admin, editor or author. With those user role/levels, an ‘edit’ button would not render with the DOM, and so never be part of a static page rendered and stored for public consumption.
Easily tested, by the way, through mechanisms like “fetch and render” tools like Google, Chrome Incognito mode, etc.
