F
by
Andrew Nacin
0 (0 reviews)
Filtered HTML for Editors
Editors and Administrators can publish content with unfiltered HTML. Use this plugin to force filtering of HTML from Editors.
Filtered HTML for Editors ranks #33,319 among WordPress.org plugins with 10+ active installations, is #1,739 of 4,596 in the Security category, and was last updated Jan 1, 2011. Data from WordPress.org, refreshed twice daily — see methodology.
Tested up to WP 3.1.4 (Current: 7.1.2)
v1.0
Current Version v1.0
Updated 15 years ago
Last Update on 01 Jan, 2011
Refreshed 6 hours ago
Last Refreshed on
#1,739 of 4,596 in Security
Top 50% by installs
No update in over a year
Rank
#33,319
—
No change
Active Installs
10+
-33.3%
KW Avg Position
78
9 worse
Downloads
3.5K
+3 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 20
10+
20+
20,057
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 6 more installs to reach 20+
Rank Changes
Current
#33,319
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.0
- Last Updated
- Jan 01, 2011
- Requires WP
- 2.8+
- Tested Up To
- 3.1.4
- PHP Version
- N/A
- Author
- Andrew Nacin
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,758
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,009
LiteSpeed Cache
7M+ installs
#5
Akismet Anti-spam: Spam Protection
5M+ installs
#8
Wordfence Security - Firewall, Malware Scan, and Login Security
5M+ installs
#11
Really Simple Security - Simple and Performant Security (formerly Really Simple SSL)
3M+ installs
#17
Hostinger Tools
3M+ installs
#20
WPS Hide Login
2M+ installs
#27
Limit Login Attempts Security – Login Security, 2FA, Firewall, Brute Force Prevention
1M+ installs
#33
WP Super Cache
1M+ installs
#37
Frequently Asked Questions
Common questions about Filtered HTML for Editors
Unfiltered HTML is potentially dangerous. It allows users to include JavaScript, object embeds, and other code that has the potential to be malicious. The capability should only be given to trusted users. By default, WordPress provides the unfiltered HTML ability to Editors and Administrators. Use this plugin to prevent Editors from publishing unfiltered HTML posts. Administrators will not be affected.
By default, users with Administrator or Editor privileges are allowed to publish unfiltered HTML in post titles and content. WordPress is, after all, a publishing tool, and people need to be able to include whatever markup they need to communicate. Users with lesser privileges are not allowed to post unfiltered content.
This plugin won't help you. If you're running a WordPress network, then only super administrators can publish unfiltered HTML. All other users are considered untrusted, since they can be administrators on sites they register. There exists another plugin called Unfiltered MU that will provide the unfiltered HTML ability to editors and administrators in multisite. This can only be used in a closed network where these users are trusted.
You can add define( 'DISALLOW_UNFILTERED_HTML', true ); to your wp-config.php file. This will affect administrators as well. If you are running multisite, this will affect super administrators. If you do this, then this plugin will not have any affect.
This is a perfect illustration of the careful balance required between security and functionality. WordPress is, after all, a publishing tool, as said above. Video embeds, such as those with <embed> or <object> tags, are considered untrusted. Thus, on save they will be stripped out, unless the user has the ability to publish unfiltered HTML. If you're embedding a video from YouTube (let's say), then you shouldn't mess with the embed code anyway. For YouTube and other sites, take a look at automatic embedding of content through oEmbed, which was added to WordPress in version 2.9. We have a handful of oEmbed providers supported in core (again, a balance between security and functionality).
