In general I wouldn’t recommend editing files that way and just disable it with the well known DISALLOW_FILE_EDIT or DISALLOW_FILE_MODS constants, that are checked within the map_meta_cap() function. But anyway it’s interesting to see if we can find a way to exclude files from the theme editor. Here are some ideas: There doesn’t seem to … Read more
Both initial creation and updates for the posts pass through wp_insert_post_data (among other filters). You can modify post_content item in array passed to make the replacement you need, before it proceeds on to be saved in database. Update Code pasted from comments add_filter( ‘wp_insert_post_data’, ‘rm_wp_insert_post_data’, ’99’, 2 ); function rm_wp_insert_post_data ( $data , $postarr ) … Read more
You can disable the visual editor entirely in your profile settings. If you need to disable it on a per page basis, take a look at this answer. Using text mode may not solve the empty paragraph problem, the wpautop filter is applied to the content regardless of how the content is edited. You can … Read more
This is caused by wptexturize and the use of a standard <div> to contain your code. See https://developer.wordpress.org/reference/functions/wptexturize/ Instead, markup code as code: Text enclosed in the tags <pre>, <code>, <kbd>, <style>, <script>, and <tt> will be skipped. This list of tags can be changed with the no_texturize_tags filter. Note that the HTML block just … Read more
The Codex (JavaScript in Posts) covers exactly this scenario; including javascript in a post on a one-off basis. So whether your javascript worked in the past or not is irrelevant, the best approach now is to use the practise described in the Codex. These are the steps that I followed: 1 – Save the javascript … Read more
[*] A few years down the track, but hopefully someone else will find this solution useful… Although my issues trying to get this sort of thing to work in WordPress were slightly different, hopefully this solution will work for you too. Firstly, the issue with tags not being allowed to contain multiple block level elements … Read more
Here is an example of How to Update kses and TinyMCE to allow select data-* attributes in WordPress. Reference add_action( ‘after_setup_theme’, ‘x_kses_allow_data_attributes_on_links’ ); function x_kses_allow_data_attributes_on_links() { global $allowedposttags; $tags = array( ‘a’ ); $new_attributes = array( ‘data-foo’ => array(), ‘data-bar’ => array(), ); foreach ( $tags as $tag ) { if ( isset( $allowedposttags[ $tag … Read more
Turns out this has something to with the way a Multi-site intall handles unfiltered_html capabilities between Super Admins and Admins. The problem was resolved using the Unfiltered MU plugin, however, beaware of the warning stated on the plugin page.
I’d say it’s impossible… For one, there’s no hook inside the file /wp-admin/theme-editor.php. And last but not least, if you try one of this, it dumps an error: /wp-admin/theme-editor.php?file=css%2Fstyle.css&theme=twentyeleven /wp-admin/theme-editor.php?file=css/style.css&theme=twentyeleven Case you find a workaround, this code injects a link to the desired file: /** * Adjust the if(‘Twenty Eleven’ == sel) to your theme … Read more
The list of allowed elements and attributes is stored in the global variable $allowedposttags which is set in wp-includes/kses.php. To override it create a simple mu plugin with the following content: <?php # -*- coding: utf-8 -*- /** * Plugin Name: Enable placeholder attribute for input elements in post tags. * Version: 2012.07.18 */ add_action( … Read more