{"id":1579,"date":"2004-12-15T00:30:05","date_gmt":"2004-12-15T00:30:05","guid":{"rendered":"https:\/\/wordpress.org\/plugins-wp\/spell-checker\/"},"modified":"2005-06-23T14:17:00","modified_gmt":"2005-06-23T14:17:00","slug":"spell-checker","status":"closed","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/spell-checker\/","author":6753,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.18","stable_tag":"trunk","tested":"","requires":"","requires_php":"","requires_plugins":"","header_name":"Spelling Checker","header_author":"Brian \"ColdForged\" Dupuis","header_description":"","assets_banners_color":"","last_updated":"2005-06-23 14:17:00","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"http:\/\/www.coldforged.org\/spelling-checker-plugin-for-wordpress\/","header_author_uri":"http:\/\/www.coldforged.org\/","rating":1,"author_block_rating":0,"active_installs":20,"downloads":22928,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["installation","faq","description"],"tags":[],"upgrade_notice":[],"ratings":{"1":"1","2":0,"3":0,"4":0,"5":0},"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.16","1.17","1.18","Alpha-0.8","Alpha-0.8.1","Alpha-0.9","Alpha-0.9.1","Beta-1.0","Beta-1.11"],"block_files":[],"assets_screenshots":{"screenshot-1.jpg":{"filename":"screenshot-1.jpg","revision":"1539161","resolution":"1","location":"plugin","width":784,"height":655}},"screenshots":{"1":"Fear the beauty."}},"plugin_section":[],"plugin_tags":[83,107,5540],"plugin_category":[44],"plugin_contributors":[90653],"plugin_business_model":[],"class_list":["post-1579","plugin","type-plugin","status-closed","hentry","plugin_tags-admin","plugin_tags-comments","plugin_tags-spelling","plugin_category-discussion-and-community","plugin_contributors-coldforged","plugin_committers-coldforged"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/spell-checker.svg","icon_2x":false,"generated":true},"screenshots":[{"src":"https:\/\/ps.w.org\/spell-checker\/trunk\/screenshot-1.jpg?rev=1539161","caption":"Fear the beauty."}],"raw_content":"<!--section=installation-->\n<ul>\n<li>The easiest way to install the plugin is to use the One-Click Install option \nof the WordPress Plugin Manager. <\/li>\n<li>Otherwise, install the spell-plugin.php file \nin the 'wp-content\/plugins' directory and the rest in a directory you create \ncalled 'wp-content\/spell-plugin. <\/li>\n<li>The plugin must be enabled from the plugins \npage, then ''you must visit the Spell Checker options page at least once'' \nbefore the plugin will be finally enabled. Follow the appropriate link in the \nSpell Checker entry of the Plugins page.<\/li>\n<\/ul>\n\n<!--section=faq-->\n<dl>\n<dt>How do I use it?<\/dt>\n<dd><p>On the \"Write Post\" page there should be a new button called \"Check Spelling\". \nClick it. You will get a new window that performs the spelling checking. Note \nthat you must have Javascript enabled for this to work. You must also have the \n\"aspell\" executable on your hosting machine for this to work as that is the \nspelling service provider used.<\/p><\/dd>\n<dt>How do I enable people to spell check their comments?<\/dt>\n<dd><p>Adding the ability for your readers to check the spelling of their comment text \nhas never been easier, though it may reduce your enjoyment of their \ninadvertently incorrect spellings. Simply modify your comments template to call \nthe following function somewhere within it (this inserts the necessary \nJavascript for opening the spelling checker window):<\/p>\n\n<p>'spell_insert_headers();'<\/p>\n\n<p>For default WordPress installations, you need no parameters. If for whatever \nreason your textarea is a different id than the default \"comment\" id, you can \nspecify that id as a parameter to this call, for example:<\/p>\n\n<p>'spell_insert_headers(\"differentcommentid\");'<\/p>\n\n<p>Now, the only thing left to do is insert the following code where you want the \n\"Check Spelling\" button to appear:<\/p>\n\n<p>'spell_insert_comment_button();'<\/p>\n\n<p>For more flexibility you can specify the following parameters to this function:<\/p>\n\n<ul>\n<li>$button_class - If so desired, you can apply a class specifier to the \nresulting button. Leaving this as the default causes no class to be specified. \nFor instance, to specify a class of \"buttonclass\", simply specify \"buttonclass\" \nas the first parameter to the function. <\/li>\n<li>$tabindex - To enhance usability, you can specify a tabindex to include in the \nbutton declaration. If undeclared, no tabindex is specified. Note that if you \ndon't wish to specify a class you must pass an empty string as the first \nparameter. As an example to specify a tabindex of 4 with no class, call the \nfunction as follows: <\/li>\n<\/ul>\n\n<p>'spell_insert_comment_button( '', \"4\" );'<\/p>\n\n<p>For more flexibility you can add words to the dictionary so that they are not \nmarked as misspelled. By default only people who are registered users of your \nblog and are logged in ''and'' have a user level greater than 8 can add words to \nthe dictionary. This is a security feature so that people can't add nonsense to \nyour dictionary. People who do not meet these requirements will simply not have \nan \"Add\" button on the form. You can modify this behavior with the from the \nSpell Checker options administration page.<\/p><\/dd>\n<dt>FAQ<\/dt>\n<dd><p>Q. I get an error when try to check the spelling and it says something \nlike \"The required field 'name' is missing.\" What do I do? \nA. That indicates that the language setting you have selected -- it defaults to \nen_US -- is not appropriate for your aspell installation. Just going by \neyeballing statistics, my first suggestion would be to try setting the language \nto \"english\" (don't copy the quotes, just the word) and if that still causes \nproblems, cut it back to \"en\". If neither work ask you hosting provider for the \nappropriate setting for their aspell installation.<\/p>\n\n<p>Q. I get blank windows in the spelling checker box. Why? \nA. It's likely you either don't have the 'aspell' executable or the path to it \nis not correctly configured. To find out, get a shell to your host and perform a \n\"which aspell\". If it tells you there is no such thing install it if possible. \nIf it provides a path (something like '\/usr\/local\/bin\/aspell') then open the \nSpell Checker options administration page and make sure the path matches. When \nyou first install the plugin, this is precisely how the plugin determines the \nlocation of the aspell executable.<\/p>\n\n<p>Q. I get errors in Internet Explorer that say something like \"Error: Object \nexpected\" on Line 44. \nA. This is another case of an aspell path problem. See the previous question for \ndetails.<\/p>\n\n<p>Q. I don't get a button. Instead it says something about \"safe_mode\". \nA. Servers that run PHP in safe_mode sometimes do not allow execution of \nexecutables in certain ways. Unfortunately, this plugin requires the execution \nof the aspell executable to do its work. Until the author figures out a way \naround it, there is no support for hosts that run PHP in safe_mode. Sorry. The \ncurrent version checks for safe_mode and refuses to even try to run, just to \nsave some support questions.<\/p>\n\n<p>Q. I don't see an \"Add\" button on my checker! \nA. By default you must be logged in to your WordPress installation and the user \nyou log in as must have a user level of 8 before you see an \"Add\" button. You \ncan modify this behavior with the from the Spell Checker options administration \npage.<\/p>\n\n<p>Q. My \"Add\" button grays out and changes to \"Adding...\" when I add a word and \nthen never comes back. \nQ. I get a failure when adding a word to the dictionary. \nA. Something is probably not configured correctly for your particular \"aspell\" \ninstallation. I gave a best first approximation of the command to add words to \ndictionaries, but aspell has many versions and may have a different set of \nparameters for you. First, check in the \"wp-content\/spell-plugin\/\" directory for \na file called \"add_failed.out\". It should have some data for you. Try to \ndetermine what happened and perhaps experiment with your aspell installation and \ndetermine the correct parameters.<\/p>\n\n<p>Q. It doesn't work! I get the \"Spell check in progress...\" indication in the \npopup window, but then just a blank page. \nA. This is a permissions problem with the personal dictionary. Open the Spell \nChecker options administration page and change the location of the personal \ndictionary to be a place where the ''Apache web server can write.'' Note that to \nspecify, for instance, your home directory, you must provide the full path to \nthat directory, as the web server generally runs under a different user id.<\/p>\n\n<p>Q. I get failures (of various kinds) when trying to add a word to the dictionary \nand I'm running WordPress 1.2.1. \nA. If you leave the options at the default -- especially the security option \nthat users must be logged in to the blog in order to add words -- you will \nlikely fail to add words in WordPress 1.2.1. This is a problem with a relative \npath in the wp-admin\/auth.php file that the plugin uses to log you in. To fix, I \nhighly recommend you upgrade to 1.2.2 as soon as possible.<\/p>\n\n<p>If all else fails and you never wind up with an aspell personal dictionary (by \ndefault created at \"wp-content\/plugins\/spell\/aspell.personal\") or you determine \nthat your version of aspell doesn't support creation or merging of personal \ndictionaries -- yes, this ''does'' happen -- there's one last thing to try. Open \nthe Spell Checker options administration page and enable the \"Enable manual \npersonal dictionary handling for broken aspell installations\" option. This will \nturn on some functionality that will circumvent the aspell personal dictionary \ncreation and merging functions and handle that inside the plugin.<\/p><\/dd>\n<dt>Special thanks<\/dt>\n<dd><p>This code is merely a mild reworking of the \n[http:\/\/sourceforge.net\/projects\/spellerpages Speller Pages] project on Source \nForge to work within the confines of the WordPress plug-in framework. All credit \nfor the actual spelling checker goes to them. The method of getting the \nfunctionality into the interface without code changes was inspired by the \n[http:\/\/www.nosq.com\/technology\/2004\/10\/runphp-wordpress-plug-in\/ RunPHP] \nplugin. Options administration inspired by \n[http:\/\/www.unknowngenius.com\/blog\/wordpress\/spam-karma Spam Karma].<\/p><\/dd>\n\n<\/dl>\n\n<!--section=description-->\n<p>The Spelling Checker plug-in for WordPress provides a built-in facility for \nspelling checks on posts from within the administration pages as well as \nspelling checks on comments via simple calls added to your templates. It \nrequires no changes to the WordPress code-base to use, you merely drop it in to \nthe plug-ins folder and enable it in the interface. This version has been tested \nin both WordPress 1.2.1 as well as WordPress 1.5 Strayhorn.<\/p>","raw_excerpt":"The Spelling Checker plug-in for WordPress provides a built-in facility for \nspelling checks on posts from within the administration pages as well as  &hellip;","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/1579","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=1579"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/coldforged"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=1579"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=1579"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=1579"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=1579"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=1579"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=1579"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}