WraithKenny

It’s stored in the post meta data table. The key for the metadata is “_SnS”

As for the plugin that’s not mine, it’d have to be re-written a bit to support multiple instances. And while they’re at it, probably use the built-in version. That isn’t a small task tho; I’m currently re-writing Scripts-n-Styles to do the same, but it’s not ready yet. The advantage is, that if we use the built-in CodeMirror, it should work with multiple instances, and also be disabled via user-settings. I’m hoping to have my update out by WordPress 5.0

I’ve looked into this, and it appears there is a check in HTML Editor Syntax Highlighter that looks to see if any element already has the css class CodeMirror and won’t start the plugin if so. The plugin looks to support only 1 CodeMirror instance per page.

For those who find this via Google Search, first deactivate “WP REST API” if active.

Then deactivate “Yoast SEO,” and reactivate it.

(Yoast plus outdated REST equals corrupted cookie or something. Reactivating clears it up.)

Hello,

Sorry. This plugin is generally pretty stable and bug free, so I don’t check very often.

Could you elaborate on where in the admin you are getting this error? Settings page, posts page, etc? Plugin version?

The plugin expects a snippet of Javascript, so it writes the opening and closing tags for you. If you want to write your own tags, close the script tag first, so you can reopen them, and after your closing tag, open it back up to prevent another error.

</script>
<script src=”https://tokbox.com/embed/embed/ot-embed.js?embedId=xxxxxxx-xxxxx-xx&room=DEFAULT_ROOM”></script>
<script>

Hi, I’m the author of the Scripts n Styles plugin. What kind of clash is happening? It might be a conflict in the versions of CodeMirror, which is now bundled with WordPress Core. I’ll put it on my list to investigate whether SnS is causing the issue or not.

1. Install WP
2. Active Twentyfifteen Theme
3. Install and activate WooCommerce
4. Install and activate this plugin
5. Attempt to edit any theme or plugin files via the code editor
6. Wait until the error returns.

I haven’t tested it since 3 months ago, but those were the steps.

Your client may have a calendar plugin in their browser that alters css on the page. That might have corrupted the data sent when they saved the attachment. (It’s weird, because WP should sanitize that, but maybe not.) The second part about the editor stripping out the strong tag actually makes sense. You can maybe poke around in phpMyAdmin if available and fix the broken reference for that attachment.

Of course, this is purely a guess, but it’s somewhere to start.

https://caniuse.com/#feat=object-fit

https://developer.mozilla.org/en-US/docs/Web/CSS/object-fit

You might have to add your user as a user on that site. (As a super-admin, you can edit the site, but I believe it checks if you are a member when making the dropdown.)

If the file is loaded, then it’s a problem with the javascript in the file.

This plugin wasn’t designed for that purpose, but if you want to, you can do the following

1. In the scripts area, close the script tag
2. insert your html,
3. Reopen the script tag (to prevent unbalanced tags in the source code)

</script>

<!-- Your snippet here. -->

<script>

That’ll create two unused (empty) script tags but it won’t cause any errors.

(A future version of this plugin will support arbitrary tags, but as it’s a free plugin developed during my off-hours, I have a hard time finding time.)

You don’t need to do all of that.

1. just close the script tag,
2. add your html,
3. then reopen the script tag.

</script>

<script type="application/ld+json">
...
</script>

<script>

This plugin wasn’t designed 8 years ago for that purpose, but to add simple scripts and simple css without having to edit the theme. If you are going through the hassle of editing the plugin, you should just add the JSON tag to the theme.

JSON-LD actually stands for “JavaScript Object Notation for Linked Data” so your gripe about the name doesn’t really make sense to me. JSON isn’t really even a script, it’s object notation, and it’s a *JavaScript* notation. When I wrote this plugin in my free time 8 years ago, JSON-LD was literally just being invented. I had no idea that the word “script” would confuse you 8 years later.