define('DISALLOW_FILE_EDIT', true);
Yes, it’s a little counter-intuitive, but you just clear out all the text and save. The plugin should detect an empty hoop and remove it for you.
]]>Yes, this is 100% a good point. WordPress 4.9 introduces CodeMirror (the thing I’m using) into the Core software, and will include accessibility enhancements as you’ve described. I will be migrating over to their standard in the next major release, but that release is taking a while to write. Hopefully, I’ll have this out soon.
]]>I want first to thank you for putting this piece of code together. It wa sso frustrating not tu easily add hjavascript to some posts.
I am the chief editor of https://www.blindtec.com.br a podcast and blog which helps blind people to better living by using eficiently assistive technology.
And here comes my problem: I am also visually empaired. The editor you are using in the plugin is not accessible with screen readers. It seens the same editor used by json lint. The cursor is not tracked correctly, so I have to type all the scripts in notepad where I can navigate through the code in an accessible manner and then go to the script editor select all and delete, then select all from notepad and copy and past.
For intensive script editing sessions this is very very exaustive. I won’t ask you to reimplement all the editing boxes using another framework, although the wordpress visual editor component works like a breese. Instead, is it possible to give us a choice to use either this inaccessible component or a classic textarea? If this choice existed I would just switch to the classic component and my workflow would work as I need it to.
Thanks,
Marlon
Yes, the metabox for a single post is meant for the single view of that post.
To style a particular post on an archive type page (like the main blog page) you’d have to use the “Global” settings and carefully select the post’s classes.
(Sorry for the delay in response!)
]]>I probably didn’t explain my difficulty very well. I have been using Scripts n Styles for a month or two, happily thinking it was styling my posts, and it was, however only posts I view by clicking the DIRECT link to the post. None of my styles show up if I load the main page of my blog which displays several posts in reverse date order. If I click on the link to the specific post, great, there is all my styling, but if I load the main blog page, it’s all gone.
It kind of figures, I suppose, because how could any of the Styling intended for a single post apply to all the posts on the main blog page?
Was this the intention of Scripts n Styles? I mean it works fine for a page. Was it intended only for single pages? That would seem to be the case, but I’d like it verified, so I don’t keep beating my head agains a wall trying to get my styles to show up.
Please let me know. I like the plugin and it works fine for pages, just not posts. If it is supposed to work for posts, please let me know. Thanks!
Barry
]]>Barry
]]>Yeah, I thought about putting in a CodeMirror search feature, but the browser search works, so it’d be a lot of work for little utility. I personally find the rest of the plugin quite useful, sorry you don’t. If you’d like to implement the search feature, I’d consider the patch.
]]>Thanks for pointing this out. I will check on it.
]]>I have a update for this in my development branch. It’s not quite ready for release just yet.
]]>I love(!) this plugin.. but it would be great if the height of the codefield would be adjustable.. especially on the [age where one edits the themes or plugins.. for my self I now change “body .CodeMirror-scroll”
“max-height” to “auto” which makes it a usable workspace for me..
Basically, I thought Network Activation made sense at the time. Only a Super Admin can use the plugin; it’s not useful for blog admins in a MultiSite configuration. I had intended to use the “Network Activation” Flag to hide the plugin from individual blog plugin screens, so that blog admins wouldn’t be exposed to something they can’t use. This functionality seems to be in flux in the core code.
]]>I’m not familiar with “CirclePlayer.” There aren’t any options to check off: the plugin is fairly simple. What ever script you put in the box gets added to the page or site. Perhaps you are including the script from inside of jquery.jplayer.min.js (copy and paste the source code) directly into the scripts box? This is the only way I see you doing this with this plugin. Scripts n Styles can “enqueue” (include by location) WordPress included scripts like jQuery, but cannot enqueue external scripts (yet).
I took a quick look at the circleplayer tutorial: Perhaps you are having difficulty with the HTML part of it? WordPress’s editor tends to mangle markup for stuff like that. I’m sorry I couldn’t be more helpful; I’m just not sure what problem you are having. If you have the excellent Firefox plugin Firebug, check to make sure all your scripts are included properly on the theme side, then check that the html markup didn’t get mangled by WordPress.
]]>I’ve released 3.0.2 which fixes this bug. It should be available momentarily.
]]>