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
Hey – I won’t be of much help as I haven’t used Xamarin in quite some time. Based on what I remember, if it requires a specific Android API then you may be able to use that method that Android supports to back-fill APIs to older platforms (you do something like set your API to 23, and then set your target to 15 and it tells the compiler to pack in the newer APIs to your app – something like that).
]]>taxonomy_template filter is also not working.
Please give me some solution.
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
]]>