{"id":64064,"date":"2014-04-04T11:10:18","date_gmt":"2014-04-04T11:10:18","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/stylebidet\/"},"modified":"2020-12-07T20:18:42","modified_gmt":"2020-12-07T20:18:42","slug":"stylebidet","status":"closed","type":"plugin","link":"https:\/\/ve.wordpress.org\/plugins\/stylebidet\/","author":203142,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_crdt_document":"","version":"1.0.0","stable_tag":"1.0.0","tested":"5.5.18","requires":"2.0.0","requires_php":"5.6","requires_plugins":"","header_name":"StyleBidet","header_author":"Lawrie Malen","header_description":"","assets_banners_color":"b2b2ab","last_updated":"2020-12-07 20:18:42","external_support_url":"","external_repository_url":"","donate_link":"http:\/\/www.verynewmedia.com\/","header_plugin_uri":"https:\/\/www.verynewmedia.com\/","header_author_uri":"https:\/\/www.verynewmedia.com\/","rating":5,"author_block_rating":0,"active_installs":10,"downloads":1247,"num_ratings":1,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"0.6.0":{"tag":"0.6.0","author":"indextwo","date":"2020-01-06 18:43:33"},"1.0.0":{"tag":"1.0.0","author":"indextwo","date":"2020-12-07 20:18:42"}},"upgrade_notice":{"1.0.0":"<p>If upgrading from previous versions of StyleBidet, the <code>Remove script tags<\/code> option is now locked into the <code>ON<\/code> position, as it will remove `` tags if any other option is enabled by default.<\/p>","0.6.0":"<p>Initial public release of StyleBidet.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":"1"},"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":2222053,"resolution":"128x128","location":"assets","locale":""},"icon-256x256.png":{"filename":"icon-256x256.png","revision":2222053,"resolution":"256x256","location":"assets","locale":""},"icon.svg":{"filename":"icon.svg","revision":2222053,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":2222053,"resolution":"1544x500","location":"assets","locale":""},"banner-772x250.png":{"filename":"banner-772x250.png","revision":2222053,"resolution":"772x250","location":"assets","locale":""}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.6.0","1.0.0"],"block_files":[],"assets_screenshots":[],"screenshots":[],"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[4657,356,180401,1216,1976],"plugin_category":[59],"plugin_contributors":[141018],"plugin_business_model":[],"class_list":["post-64064","plugin","type-plugin","status-closed","hentry","plugin_tags-clean","plugin_tags-css","plugin_tags-purify","plugin_tags-script","plugin_tags-style","plugin_category-utilities-and-tools","plugin_contributors-indextwo","plugin_committers-indextwo"],"banners":[],"icons":{"svg":"https:\/\/ps.w.org\/stylebidet\/assets\/icon.svg?rev=2222053","icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/stylebidet_b2b2ab.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"<!--section=description-->\n<p>As site designers, developers &amp; owners we all have clients &amp; editors who, even with the best of intentions, can make a hash job of editing a page or a post; for example, making a headline italic, and purple, and Papyrus (despite the site's overall aesthetic of non-italic cobalt-blue Open Sans everywhere else); or the oft-seen act of making <strong>all of the text red &amp; bold so that it all stands out all the time<\/strong>.<\/p>\n\n<p>What StyleBidet does is subtly take back some of that design control to ensure that sites look the way they were intended to. Via the handy Settings panel, you can optionally set StyleBidet to:<\/p>\n\n<ul>\n<li>Remove inline <code>style<\/code> attributes when saving &amp; displaying post content;<\/li>\n<li>Remove <code>&lt;style&gt;<\/code> &amp; <code>&lt;font&gt;<\/code> tags when saving &amp; displaying content;<\/li>\n<li>Remove <code>&lt;script&gt;<\/code> tags when saving &amp; displaying content;<\/li>\n<li>Remove the <strong>Text Color<\/strong> button from the WordPress Classic\/WYSIWYG Editor;<\/li>\n<li><strong>New!<\/strong> Remove inline <code>style\/font<\/code> attributes &amp; tags when saving &amp; displaying <strong>Advanced Custom Fields<\/strong>.<\/li>\n<\/ul>\n\n<!--section=installation-->\n<p>To install and run StyleBidet, all you need to do is:<\/p>\n\n<ol>\n<li>Click <strong>New Plugin<\/strong> &amp; search for 'StyleBidet', or download and then upload <code>StyleBidet<\/code> to your <code>\/wp-content\/plugins\/<\/code> directory;<\/li>\n<li>Activate the plugin through the <strong>Plugins<\/strong> menu in WordPress;<\/li>\n<li>Set up StyleBidet via <strong>Settings -&gt; StyleBidet Settings<\/strong><\/li>\n<li>Alternatively, you can configure StyleBidet with constants - see below.<\/li>\n<\/ol>\n\n<h4>Configure with constants<\/h4>\n\n<p>Instead of using the super-friendly settings page, you can optionally configure StyleBidet with constants in your code. This can be particularly helpful if you have a client who likes to poke around in the settings, or if you just want to set the options and forget about it.<\/p>\n\n<p>You can set these in your site's <code>wp-config.php<\/code> file or in the active theme's <code>functions.php<\/code> file - just remember that if you do the latter and then change the theme, your settings will be lost.<\/p>\n\n<h4>Set StyleBidet's Settings<\/h4>\n\n<p>You can define any or all of the settings below:<\/p>\n\n<pre><code>define('VNM_STYLEBIDET_SETTINGS', array(\n    'clean_output'      =&gt; true,    \/\/  Remove style &amp; font tags &amp; attributes from content at the point it is displayed\n    'clean_save'        =&gt; true,    \/\/  Permanently remove style &amp; font tags &amp; attributes from content at the point it is saved. \n    'remove_text_color' =&gt; true     \/\/  Remove the Text Color button from the TinyMCE editor\n));\n<\/code><\/pre>\n\n<p>'clean_acf'         =&gt; true,    \/\/  Remove style &amp; font tags &amp; attributes from ACF field content<\/p>\n\n<p>If you have left the Settings page visible (see below), you'll see a lock icon next to any options you have set in code, and the option can't be changed. If there are any options that you <em>haven't<\/em> pre-set, you can still toggle these on &amp; off and save your settings. If you've pre-set <em>all<\/em> of the options in code, then the <strong>Save Settings<\/strong> button will be disabled, and you should probably hide the StyleBidet Settings page at this point.<\/p>\n\n<p>To set just one option in code, for example:<\/p>\n\n<pre><code>define('VNM_STYLEBIDET_SETTINGS', array('clean_output' =&gt; true));\n<\/code><\/pre>\n\n<p>This will lock the <em>Remove style\/font tags &amp; attributes when displaying<\/em> option to enabled, but leave the rest changeable via the settings page.<\/p>\n\n<h4>Hide StyleBidet's Settings Page<\/h4>\n\n<p>The following will hide the settings page from wp-admin. This should only be done if you're adding the <code>VNM_STYLBIDET_SETTINGS<\/code> constant as above; or <em>after<\/em> you've ensured all of the settings are set &amp; working as expected.<\/p>\n\n<pre><code>define('VNM_STYLEBIDET_SHOW_SETTINGS', false);\n<\/code><\/pre>\n\n<!--section=faq-->\n<dl>\n<dt><h3>I added StyleBidet, but now all of my fancy styles have disappeared! What's going on?<\/h3><\/dt>\n<dd><p>If you're comfortable and happy adding plenty of custom styles to each and every post and page, then this plugin is most definitely not for you. It assumes that your website's styling really should be taken care of by your theme's stylesheet, and so ruthlessly removes anything else.<\/p><\/dd>\n<dt><h3>I installed this on a client's site and now they're complaining that they can't make all the text red &amp; purple anymore.<\/h3><\/dt>\n<dd><p>Hopefully this goes without saying, but if you're thinking of installing this on a client's site in response to their penchant for <code>creative additions<\/code>, you <em>really<\/em> need to check with your client first. This plugin was developed in response to clients making such changes and then realising they'd made a terrible mistake, unintentionally sullying the appearance of a site they'd paid good money to have designed. Always use this plugin responsibly and with client consent.<\/p><\/dd>\n<dt><h3>I installed this on my site and now a bunch of stuff looks weird \/ isn't animating \/ has disappeared.<\/h3><\/dt>\n<dd><p>Similarly to the point above: if you know or suspect that the site has a lot of inline <code>&lt;script&gt;<\/code> tags in the content for countdown timers, animating SVGs etc. then this plugin may not be the solution for you. Inline <code>&lt;script&gt;<\/code> tags generally aren't safe or a great idea, and StyleBidet will clean them out by default if <em>any<\/em> options are enabled.<\/p><\/dd>\n<dt><h3>The 'Remove script tags' button is locked. WTH?<\/h3><\/dt>\n<dd><p>Inline <code>&lt;script&gt;<\/code> tags generally aren't safe or a great idea, and StyleBidet will clean them out by default if <em>any<\/em> options are enabled. Because it does this by default, the <code>Remove script tags<\/code> option is locked to to <strong>ON<\/strong>, mostly just to let you know that it <em>will<\/em> be removing them.<\/p><\/dd>\n<dt><h3>I want to keep inline styling, but remove inline script tags. How do I do this?<\/h3><\/dt>\n<dd><p>As with the question above: this plugin may not be the solution for you. Inline <code>&lt;script&gt;<\/code> tags generally aren't safe or a great idea, and StyleBidet will clean them out by default if <em>any<\/em> options are enabled.<\/p><\/dd>\n<dt><h3>Does this work with custom post types?<\/h3><\/dt>\n<dd><p>StyleBidet will work with any post type that can either be displayed or saved.<\/p><\/dd>\n<dt><h3>Does this work with Advanced Custom Fields?<\/h3><\/dt>\n<dd><p>It totally does! As of version <code>1.0.0<\/code>, StyleBidet can optionally clean out your ACF text, textarea &amp; WYSIWYG fields.<\/p><\/dd>\n<dt><h3>Does this work with Gutenberg and\/or Classic Editor?<\/h3><\/dt>\n<dd><p>StyleBidet works with both! It was originally developed with the 'classic' WYSIWYG editor, and more recently updated to ensure it works with Gutenberg content.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>Removed dependency on htmlLawed and made all cleaning operations native;<\/li>\n<li>Added option for cleaning ACF fields<\/li>\n<\/ul>\n\n<h4>0.6.0<\/h4>\n\n<p>Initial public release of StyleBidet.<\/p>","raw_excerpt":"Tired of MS Word-pasted content and overzealous editors destroying your site styles with green Comic-Sans text &amp; purple backgrounds? Well not anym &hellip;","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ve.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/64064","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ve.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/ve.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/ve.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=64064"}],"author":[{"embeddable":true,"href":"https:\/\/ve.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/indextwo"}],"wp:attachment":[{"href":"https:\/\/ve.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=64064"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/ve.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=64064"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/ve.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=64064"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/ve.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=64064"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/ve.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=64064"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/ve.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=64064"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}