This plugin is exposing vulnerable to Cross Site Request Forgery (CSRF). Do we have any updates on this problem?
]]>Has no effect with WP 6
]]>On WordPress version 5.2.5, Don’t Muck My Markup version 18, pages are still getting what WordPress thinks is clean HTML code. I’m using the stock Twenty Fifteen theme, and the whole site option. When I try to do an individual page instead of the whole site, WordPress still messes up my code. I tried this on both a post and a page.
]]>Can you give any suggestions on how to debug problems with this problem not working in custom themes? A description of why it breaks, or an example of how it should work? It’s hard to diagnose whether the plugin isn’t working because the plugin is broken or because my theme is broken. Thanks
]]>Hi,
I’ve been using this plugin (v1.7) for a little while and it worked as I expected. I edit a page now and my HTML tags are deleted. The page is marked for ‘no mucking!’, I add a <br>, then Update or switch to visual mode and the tag is deleted.
Beware! We discovered that this this plugin (v.1.7) when activated can cause javascript code to be altered and broken when it’s sent to the browser. We’re using it in WordPress v.4.9.9.
This plugin caused a browser javascript syntax error, which caused some of the page functionality to break. The WordPress page did not have the “Don’t Muck My Markup” switch turned on.
The character string && was being turned into &038;&. The full line of the original javascript code was if(list != null && list.length != 0) {, and this was being turned into if(list != null &038;& list.length != 0) {, causing the javascript syntax error.
With the plugin deactivated, the error does not occur. With the plugin activated, the error does occur, even though the “Don’t Muck My Markup” switch is turned off for the affected page.
The javascript was being sent to the browser via a PHP include() statement in the affected page.
So, this is just an FYI. It would be great if this issue could be fixed in future versions of this plugin.
]]>Hi,
I installed and activated the plugin, and tried to disable auto-formatting on a single page, but I keep getting auto generated <p> tags. So I’m think I did something wrong, or didn’t do enough to make it work.
It is a custom theme, so maybe there is something there?
Hope you can help!
]]>Hi,
I installed your plugin and checked the box ‘Disable auto-formatting for this page’ for a page.
2) added below code in bold in text mode
3) saved the page
4) changed editor to visual
5) changed back to text
6) the html has changed back to the one without the bold script
<div class="call_to_action_box">
<a class=" cta_button button large-btn "href="https://www.domain.com" <strong>onclick="trackOutboundLink('https://www.domain.com'); return false;"</strong>>Maak gratis SEO account</a>
<h2>Try free</h2>
</div>Martin, Im using an older version of the Roots theme, which is heavily modified. I imagine its something that I’ve done along the way, but your plugin doesn’t seem to be doing the trick.
How would I go about troubleshooting the filter sequencing?
]]>thank you!
]]>WP still keeps adding p and br after installation and activation for the hole site.
]]>It strips itemprop=”recipeIngredient”
]]>I installed the plugin and have checked the
“Don’t Muck My Markup” box on specific pages where I have some php coding”
But it doesn’t seem to have an effect — as soon as the “visual tab” is clicked, or if I open one of these pages and the visual tab is the default, the code is broken.
Am I not using it correctly?
]]>I think they made some changes to the editor in 4.3 that are not compatible with this plugin.
]]>Hello,
This is great plugin. Thanks a lot.
Do you have any idea how to make it work partially on particular page?
Is it possible?
Thanks
Disable auto-formatting for this ‘ . get_post_type(); echo $output; } function save( $post_id ) { if ( defined(‘DOING_AUTOSAVE’) && DOING_AUTOSAVE ) return $post_id; update_post_meta( $post_id, ‘_dont_muck’, isset( $_POST[‘dont_muck’] ) ? true : ” ); } function insertCSS() { // Only load this stylesheet if they’re on post.php inside the dashboard wp_enqueue_style( ‘admin.css’, plugins_url( ‘css/admin.css’, self::$plugin_url ) ); } static function checked() { // We’re not “caching” this in a static property because this method will be called potentially multiple times throughout the loop if ( get_post() ) { $checked = get_post_meta( get_the_ID(), ‘_dont_muck’, true); if ( ! empty( $checked ) ) return true; } return false; } } Fatal error: Class ‘Admin’ not found in /home/wordpress/wordpress/wp-content/plugins/dont-muck-my-markup/dont-muck-my-markup.php on line 38
]]>Hello,
Thank you very much for this plugin. It is a life saver.
Is there anyway I can toggle it globally? I would like it to be activated always on all pages and posts.
Thanks and cheers
Constantin
The plugin installed fine, activated fine, shows up on the edit page, but just doesn’t work/ The theme we are using is “Harmony Responsive”. I wish it worked well enough to say there is a bug, but…nothing.
]]>Received this error when trying to activate the plugin in WP 3.8:
Disable auto-formatting for this ‘ . get_post_type(); echo $output; } function save( $post_id ) { if ( defined(‘DOING_AUTOSAVE’) && DOING_AUTOSAVE ) return $post_id; update_post_meta( $post_id, ‘_dont_muck’, isset( $_POST[‘dont_muck’] ) ? true : ” ); } function insertCSS() { // Only load this stylesheet if they’re on post.php inside the dashboard wp_enqueue_style( ‘admin.css’, plugins_url( ‘css/admin.css’, self::$plugin_url ) ); } static function checked() { // We’re not “caching” this in a static property because this method will be called potentially multiple times throughout the loop $checked = get_post_meta( get_the_ID(), ‘_dont_muck’, true); if ( empty( $checked ) ) return false; else return true; } }
Please HELP! This is an important part of a production release.
Thanks
]]>