tinymce-spellcheck
TinyMCE Spellcheck
TinyMCE Spellcheck adds the spellcheck button back to the editor in WordPress 3.6 and up.
Proof Health
Open evidenceCommercial opportunities need traceable source links before they are treated as build-worthy.
86.7% of this page's analysis has direct source links.
0 rows here require auditable proof before promotion.
0 rows have source counts but still need direct links.
Related Opportunities
1 marketSource Evidence
Open evidence explorerSince WP v3.9, span classes are added in the code: users show bugs, compatibility pain that may indicate a product gap.
Buyer: site owners and agencies · Wedge: detect failures around grammar before they cost the buyer time, revenue, or trustHopefully the author will take back this plugin to life: users show bugs, missing feature, support pain that may indicate a product gap.
Buyer: site owners and agencies · Wedge: detect failures around grammar before they cost the buyer time, revenue, or trustGreat!!! And Dead!!: users show bugs, support, migration pain that may indicate a product gap.
Buyer: site owners and agencies · Wedge: detect failures around grammar before they cost the buyer time, revenue, or trustWorst Plugin Ever: users show bugs, compatibility, support pain that may indicate a product gap.
Buyer: site owners and agencies · Wedge: detect failures around grammar before they cost the buyer time, revenue, or trustFrontend Editor: users show missing feature, support pain that may indicate a product gap.
Buyer: site owners and agencies · Wedge: detect failures around grammar before they cost the buyer time, revenue, or trustNot supported gutenberg: users show bugs, support pain that may indicate a product gap.
Buyer: site owners and agencies · Wedge: detect failures around grammar before they cost the buyer time, revenue, or trustTinyMCE Spellcheck: Great but for which languages?: users show missing feature, setup pain that may indicate a product gap.
Buyer: site owners and agencies · Wedge: detect failures around grammar before they cost the buyer time, revenue, or trustCan This Be Updated This to WordPress 4.2 ?: users show compatibility pain that may indicate a product gap.
Buyer: site owners and agencies · Wedge: detect failures around grammar before they cost the buyer time, revenue, or trustFor future update: Allow options for admins to disable functions in profile edi: users show missing feature pain that may indicate a product gap.
Buyer: site owners and agencies · Wedge: detect failures around grammar before they cost the buyer time, revenue, or trustNo Longer Works with Product Data WooCommerce 2.1: users show compatibility pain that may indicate a product gap.
Buyer: site owners and agencies · Wedge: detect failures around grammar before they cost the buyer time, revenue, or trustCompetitor Context
8 shownRepeated Themes
0 shownNo repeated plugin-level themes have been generated yet.
Collected Signals
20 shown from 28 collectedITS NO LONGER WORKING: neutral conversation with limited structured signal.
Evidence: ITS NO LONGER WORKING Hello everyone, I have been using this plugin for months but it has today just stopped proof reading the things I wrote. When I click on the ABC, it says everything is okay even though there is spelling mistakes. Hello everyone, I have been using this plugin for months but it has today just stopped proof reading the things I wrote. WhenNot supported gutenberg: users show bugs, support pain that may indicate a product gap.
Evidence: Not supported gutenberg Hello.Error message – proofreading service: users show bugs pain that may indicate a product gap.
Evidence: Error message – proofreading service Hello, trying to proofread causes the following error message: There was a problem communicating with the Proofreading service.Where I can find Setting page in WP 4.7.3?: users show missing feature pain that may indicate a product gap.
Evidence: Where I can find Setting page in WP 4.7.3?Hopefully the author will take back this plugin to life: users show bugs, missing feature, support pain that may indicate a product gap.
Evidence: At least for those who are supporting this work, would ne nice they don’t love the face due its author loss of interests.Frontend Editor: users show missing feature, support pain that may indicate a product gap.
Evidence: Frontend Editor There was a topic on this but it was prematurely closed before it ever got resolved.Works nice, even for german language: users show missing feature pain that may indicate a product gap.
Evidence: Works nice, even for german language You will find the settings in your USER Profile!Adds " " everywhere: users praise quality, which suggests what competitors already do well.
Evidence: Adds " " everywhere Everything worked great but it kept adding ” ” throughout my article’s HTML which I had to go back and delete.Can This Be Updated This to WordPress 4.2 ?: users show compatibility pain that may indicate a product gap.
Evidence: This is a great little plugin that I’ve been using for over 1 year, but I’m a little afraid to use it now with all of the current and future developments of WordPress (more and more JavaScript).TinyMCE Spellcheck: Great but for which languages?: users show missing feature, setup pain that may indicate a product gap.
Evidence: TinyMCE Spellcheck: Great but for which languages?Button there – but does nothing: users show setup pain that may indicate a product gap.
Evidence: Button there – but does nothing We have TinyMCE advanced and the TinyMCE Spellcheck plugin installed.proofreading settings not there: users show missing feature, support pain that may indicate a product gap.
Evidence: proofreading settings not there Hi, I cannot find the settings dialog for proofreading.Worst Plugin Ever: users show bugs, compatibility, support pain that may indicate a product gap.
Evidence: It screwed up spacing with a <span> tag listed every other word for nonexistent errors.Awesome: users praise quality, which suggests what competitors already do well.
Evidence: Awesome It is the best plugin of its kind that I have found.You help me a lot!: users show bugs, support pain that may indicate a product gap.
Evidence: You help me a lot!Idea is good, but WP 3.9 breaks it: users show bugs pain that may indicate a product gap.
Evidence: Idea is good, but WP 3.9 breaks it Great to have a non-Jetpack spellchecker and the basic functionality works great.Since WP v3.9, span classes are added in the code: users show bugs, compatibility pain that may indicate a product gap.
Evidence: Since WP v3.9, span classes are added in the code Since the latest update and the update of WP 3.9, I have noticed the plugin adds this class to each highlighted word: <span class="hiddenSpellError"> This never happened on the earlier version, is there anyway to find a solution to this?Dosen't work in WordPress 3.9: users praise reliable, which suggests what competitors already do well.
Evidence: https://wordpress.org/plugins/tinymce-spellcheck/ The plugin works again in the new version.Great!!! And Dead!!: users show bugs, support, migration pain that may indicate a product gap.
Evidence: Great!!!Works great!: users praise reliable, quality, which suggests what competitors already do well.
Evidence: Works great!