Multisite / Subsite spell checker seems to not work. I am not sure if I miss some settings.
I have checked the spell checker in network dashboard and its working fine, but when I tried it in the subsite it is not working. I click Entire Site / Spell check my Website its not doing anything at all.
]]>Hi,
At the moment your plugin has 11 cases where you use “%%%s”, e.g.
class-wpsc-dictionary.php
$wpdb->prepare('SELECT id, word FROM ' . $table_name . ' WHERE word LIKE "%%%s%%"', $search)While this is fine at the moment, it is an undocumented “feature” that should be removed in the future.
The wpdb::prepare() documentation notes that percentage wildcards cannot be inserted directly into the SQL, and instead the complete LIKE string should be provided via the arguments, e.g.
$wpdb->prepare('SELECT id, word FROM ' . $table_name . ' WHERE word LIKE %s', '%' . $wpdb->esc_like( $search ) . '%')It’s undocumented because the “%%” should only provide a single literal percentage sign, and not cause the following “%s” to be unquoted.
]]>your pricing page is broken. your contact form is broken. let us know.
]]>Getting a new error after recent update.
PHP Fatal error: Cannot redeclare tgmpa() (previously declared in /wp-content/plugins/wp-spell-check/lib/class-tgm-plugin-activation.php:2126)
This is being declared in my theme also. I would guess other themes have this since it is for TGM Plugin Activation library? Unsure if there is a better way, or if the theme should be calling it differently.
Also this
WordPress database error Column 'keyword' cannot be null for query INSERT INTO 'wp_dzci_spellcheck_ignore' ('keyword', 'type') VALUES (NULL, 'page') made by wpscx_error_reporting
Which probably isn’t a fatal error.
Just to let you know.
Where is the spell check tacking place. Within my WordPress insstllation or within your cloud?
Is there any external ressource loaded / used or everything within my WordPress installation?
]]>Any idea what this warning might be coming from?
PHP Warning: Division by zero in /wp-content/plugins/wp-spell-check/admin/wpsc-results.php
Using PHP 7.1.33
Not a big deal, seems to work fine. Just saw this in the error log on the server.
Thanks for any help you can provide.
I can’t post a screen shot but when I finally got the plug in to run (first attempt took down my whole site. I had to install one of the vanilla WP themes to get it to be able to start).
But now it’s been running, but isn’t doing anything. Just says:
Errors found on Post Content: 0 Posts scanned: 0/115
Pages scanned: 0/82
Last scan took 0 Minutes
Scan in Progress A scan is currently in progress for . Estimated time for completion is 9 seconds . Click here to see scan results. ?
I get the little green spinning wheel but no posts or pages are being checked.
]]>I’m seeing these errors in debug.log repeatedly
[23-Nov-2019 00:53:21 UTC] PHP Notice: Undefined index: page in /nas/content/live/wdwnt/wp-content/plugins/wp-spell-check/admin/wpsc-class-admin.php on line 19
[23-Nov-2019 00:53:21 UTC] PHP Notice: Undefined index: page in /nas/content/live/wdwnt/wp-content/plugins/wp-spell-check/admin/wpsc-class-admin.php on line 20
[23-Nov-2019 00:53:21 UTC] PHP Notice: Undefined index: page in /nas/content/live/wdwnt/wp-content/plugins/wp-spell-check/admin/wpsc-class-admin.php on line 21
[23-Nov-2019 00:53:21 UTC] PHP Notice: Undefined index: page in /nas/content/live/wdwnt/wp-content/plugins/wp-spell-check/admin/wpsc-class-admin.php on line 22
[23-Nov-2019 00:53:21 UTC] PHP Notice: Undefined index: page in /nas/content/live/wdwnt/wp-content/plugins/wp-spell-check/admin/wpsc-class-admin.php on line 23
[23-Nov-2019 00:53:21 UTC] PHP Notice: Undefined index: page in /nas/content/live/wdwnt/wp-content/plugins/wp-spell-check/admin/wpsc-class-admin.php on line 25
[23-Nov-2019 00:53:21 UTC] PHP Notice: Undefined index: page in /nas/content/live/wdwnt/wp-content/plugins/wp-spell-check/admin/wpsc-class-admin.php on line 27
[23-Nov-2019 00:53:21 UTC] PHP Notice: Undefined index: page in /nas/content/live/wdwnt/wp-content/plugins/wp-spell-check/admin/wpsc-class-admin.php on line 220Hi,
The WP spell check is able to detect the wrong spell in normal WordPress Gothenburg editor but when I installed the Elementer pro plugin after that I am using the Elementer editor for the writing of my blogs or any posts. But if any wrong word or any mistake I am doing in this editor it is not detecting now. So my kind request you to give me the solution as to how to fix it or any other better plugin is there which will work universally?
Advanced Thanks
Prakash
Hello I’ve found an issue, could you please have a look and fix it.
I did a speed test via https://gtmetrix.com and in the results I see:
The following requests are returning 404/410 responses. Either fix the broken links, or remove the references to the non-existent resources.
https://www.bfscapital.com/wp-content/plugins/wp-spell-check/css/wpsc-sidebar.css
this css is with 404 error
]]>So I installed the WP-Spell and activated it and it redirected me to the website but I got an error message. “This page isn’t working suntsu.com is currently unable to handle this request.HTTP ERROR 500”
When I tried to get back into WP I get the same message.
Not happy to be locked out of my website and WP Admin???
Please help.
James
]]>I’m looking at the free version right now, but it seems to think that I have the pro version (not yet).
On every page, admin and non-admin, at the top, I see the following:
Warning: fopen(/home4/gamethrall/public_html/sanenew/wp-content/plugins/wp-spell-check-pro/wpspellcheckpro.php): failed to open stream: No such file or directory in /home4/gamethrall/public_html/sanenew/wp-includes/functions.php on line 5568
Warning: fread() expects parameter 1 to be resource, boolean given in /home4/gamethrall/public_html/sanenew/wp-includes/functions.php on line 5571
Warning: fclose() expects parameter 1 to be resource, boolean given in /home4/gamethrall/public_html/sanenew/wp-includes/functions.php on line 5574
]]>How can I use UK English and not the automatically loaded US?
Regards
Drachsi
Caused fatal errors upon activation.
Please, guys, make sure it works when you upload the plugin at WordPress repository.
I was literally about to buy your plugin, anyway I had deactivated it last night (the free version).
I was working on a blog and I saw some words marked in RED I was like WTF these were incorrect spelling mistakes but then I went into the code.
You plugin literally add code into the post / page saying there is a spelling mistake. I have a website with around 300 posts / pages. I now have to go through ALL of them to make sure your code isn’t residual left there. Sure if I fix the spelling mistake its gone but if I do a sitewide search for mistakes it now means its potentially every page. Here are 2 examples:
1. <span class=”hiddenSpellError wpgc-passive” style=”background: #59c033;”>can be</span>
To make it WORSE your product embedded code into Visual Composer code…. it does not appear in search so now I have to go through every page line by line to manually remove your code UNLESS you can find a solution.
[vc_single_image <span class=”hiddenSpellError wpgc-complex” style=”background: #a3c5ff;”><span class=”hiddenSpellError wpgc-complex” style=”background: #a3c5ff;”><span class=”hiddenSpellError wpgc-complex” style=”background: #a3c5ff;”><span class=”hiddenSpellError wpgc-complex” style=”background: #a3c5ff;”>image</span></span></span></span>=”10735″ img_size=”large” add_caption=”yes” alignment=”center” qode_css_animation=”” css=”.vc_custom_1533125371709{padding-top: 5px !important;padding-bottom: 5px !important;}”]
Why would you not just design this smarter and keep the info in a database instead of populating code in the page itself. Contact me ASAP
]]>After completing a “Entire Site” scan (Pro version), the Spell Check screen goes entirely blank (not a wp-admin white screen as sidebar and rest of the site still works). After a Page Title scan (or similar), the scan completes, page is visible, but no spelling errors are returned on the screen. The spell check table is there and it says “25 items” above the table, but there are no actual rows. Looking at the wp_spellcheck_words table in the DB, 25 results are there, but nothing is shown on the page.
With WP_DEBUG enabled, the errors below are thrown (note that the actual install directory has been replaced with <INSTALL_DIR> in the log).
This seems very similar to the errors shown at https://plugintests.com/plugins/wp-spell-check/latest (although I am using PHP v5.6.35)
[26-Apr-2018 04:38:09 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.www.ads-software.com/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in <INSTALL_DIR>\wp-includes\functions.php on line 4147
[26-Apr-2018 04:38:09 UTC] PHP Stack trace:
[26-Apr-2018 04:38:09 UTC] PHP 1. {main}() <INSTALL_DIR>\index.php:0
[26-Apr-2018 04:38:09 UTC] PHP 2. require() <INSTALL_DIR>\index.php:17
[26-Apr-2018 04:38:09 UTC] PHP 3. require_once() <INSTALL_DIR>\wp-blog-header.php:13
[26-Apr-2018 04:38:09 UTC] PHP 4. require_once() <INSTALL_DIR>\wp-load.php:37
[26-Apr-2018 04:38:09 UTC] PHP 5. require_once() <INSTALL_DIR>\wp-config.php:129
[26-Apr-2018 04:38:09 UTC] PHP 6. include_once() <INSTALL_DIR>\wp-settings.php:305
[26-Apr-2018 04:38:09 UTC] PHP 7. wp_enqueue_style() <INSTALL_DIR>\wp-content\plugins\wp-spell-check\wpspellcheck.php:50
[26-Apr-2018 04:38:09 UTC] PHP 8. _wp_scripts_maybe_doing_it_wrong() <INSTALL_DIR>\wp-includes\functions.wp-styles.php:165
[26-Apr-2018 04:38:09 UTC] PHP 9. _doing_it_wrong() <INSTALL_DIR>\wp-includes\functions.wp-scripts.php:47
[26-Apr-2018 04:38:09 UTC] PHP 10. trigger_error() <INSTALL_DIR>\wp-includes\functions.php:4147
[26-Apr-2018 04:38:09 UTC] PHP Notice: wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.www.ads-software.com/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in <INSTALL_DIR>\wp-includes\functions.php on line 4147
[26-Apr-2018 04:38:09 UTC] PHP Stack trace:
[26-Apr-2018 04:38:09 UTC] PHP 1. {main}() <INSTALL_DIR>\index.php:0
[26-Apr-2018 04:38:09 UTC] PHP 2. require() <INSTALL_DIR>\index.php:17
[26-Apr-2018 04:38:09 UTC] PHP 3. require_once() <INSTALL_DIR>\wp-blog-header.php:13
[26-Apr-2018 04:38:09 UTC] PHP 4. require_once() <INSTALL_DIR>\wp-load.php:37
[26-Apr-2018 04:38:09 UTC] PHP 5. require_once() <INSTALL_DIR>\wp-config.php:129
[26-Apr-2018 04:38:09 UTC] PHP 6. include_once() <INSTALL_DIR>\wp-settings.php:305
[26-Apr-2018 04:38:09 UTC] PHP 7. wp_enqueue_script() <INSTALL_DIR>\wp-content\plugins\wp-spell-check\wpspellcheck.php:51
[26-Apr-2018 04:38:09 UTC] PHP 8. _wp_scripts_maybe_doing_it_wrong() <INSTALL_DIR>\wp-includes\functions.wp-scripts.php:267
[26-Apr-2018 04:38:09 UTC] PHP 9. _doing_it_wrong() <INSTALL_DIR>\wp-includes\functions.wp-scripts.php:47
[26-Apr-2018 04:38:09 UTC] PHP 10. trigger_error() <INSTALL_DIR>\wp-includes\functions.php:4147
[26-Apr-2018 04:38:09 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.www.ads-software.com/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in <INSTALL_DIR>\wp-includes\functions.php on line 4147
[26-Apr-2018 04:38:09 UTC] PHP Stack trace:
[26-Apr-2018 04:38:09 UTC] PHP 1. {main}() <INSTALL_DIR>\index.php:0
[26-Apr-2018 04:38:09 UTC] PHP 2. require() <INSTALL_DIR>\index.php:17
[26-Apr-2018 04:38:09 UTC] PHP 3. require_once() <INSTALL_DIR>\wp-blog-header.php:13
[26-Apr-2018 04:38:09 UTC] PHP 4. require_once() <INSTALL_DIR>\wp-load.php:37
[26-Apr-2018 04:38:09 UTC] PHP 5. require_once() <INSTALL_DIR>\wp-config.php:129
[26-Apr-2018 04:38:09 UTC] PHP 6. include_once() <INSTALL_DIR>\wp-settings.php:305
[26-Apr-2018 04:38:09 UTC] PHP 7. wp_enqueue_style() <INSTALL_DIR>\wp-content\plugins\wp-spell-check\wpspellcheck.php:52
[26-Apr-2018 04:38:09 UTC] PHP 8. _wp_scripts_maybe_doing_it_wrong() <INSTALL_DIR>\wp-includes\functions.wp-styles.php:165
[26-Apr-2018 04:38:09 UTC] PHP 9. _doing_it_wrong() <INSTALL_DIR>\wp-includes\functions.wp-scripts.php:47
[26-Apr-2018 04:38:09 UTC] PHP 10. trigger_error() <INSTALL_DIR>\wp-includes\functions.php:4147
[26-Apr-2018 04:38:09 UTC] PHP Notice: wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.www.ads-software.com/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in <INSTALL_DIR>\wp-includes\functions.php on line 4147
[26-Apr-2018 04:38:09 UTC] PHP Stack trace:
[26-Apr-2018 04:38:09 UTC] PHP 1. {main}() <INSTALL_DIR>\index.php:0
[26-Apr-2018 04:38:09 UTC] PHP 2. require() <INSTALL_DIR>\index.php:17
[26-Apr-2018 04:38:09 UTC] PHP 3. require_once() <INSTALL_DIR>\wp-blog-header.php:13
[26-Apr-2018 04:38:09 UTC] PHP 4. require_once() <INSTALL_DIR>\wp-load.php:37
[26-Apr-2018 04:38:09 UTC] PHP 5. require_once() <INSTALL_DIR>\wp-config.php:129
[26-Apr-2018 04:38:09 UTC] PHP 6. include_once() <INSTALL_DIR>\wp-settings.php:305
[26-Apr-2018 04:38:09 UTC] PHP 7. wp_enqueue_script() <INSTALL_DIR>\wp-content\plugins\wp-spell-check\wpspellcheck.php:53
[26-Apr-2018 04:38:09 UTC] PHP 8. _wp_scripts_maybe_doing_it_wrong() <INSTALL_DIR>\wp-includes\functions.wp-scripts.php:267
[26-Apr-2018 04:38:09 UTC] PHP 9. _doing_it_wrong() <INSTALL_DIR>\wp-includes\functions.wp-scripts.php:47
[26-Apr-2018 04:38:09 UTC] PHP 10. trigger_error() <INSTALL_DIR>\wp-includes\functions.php:4147
[26-Apr-2018 04:38:09 UTC] PHP Notice: wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.www.ads-software.com/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in <INSTALL_DIR>\wp-includes\functions.php on line 4147
[26-Apr-2018 04:38:09 UTC] PHP Stack trace:
[26-Apr-2018 04:38:09 UTC] PHP 1. {main}() <INSTALL_DIR>\index.php:0
[26-Apr-2018 04:38:09 UTC] PHP 2. require() <INSTALL_DIR>\index.php:17
[26-Apr-2018 04:38:09 UTC] PHP 3. require_once() <INSTALL_DIR>\wp-blog-header.php:13
[26-Apr-2018 04:38:09 UTC] PHP 4. require_once() <INSTALL_DIR>\wp-load.php:37
[26-Apr-2018 04:38:09 UTC] PHP 5. require_once() <INSTALL_DIR>\wp-config.php:129
[26-Apr-2018 04:38:09 UTC] PHP 6. include_once() <INSTALL_DIR>\wp-settings.php:305
[26-Apr-2018 04:38:09 UTC] PHP 7. wp_enqueue_script() <INSTALL_DIR>\wp-content\plugins\wp-spell-check\wpspellcheck.php:54
[26-Apr-2018 04:38:09 UTC] PHP 8. _wp_scripts_maybe_doing_it_wrong() <INSTALL_DIR>\wp-includes\functions.wp-scripts.php:267
[26-Apr-2018 04:38:09 UTC] PHP 9. _doing_it_wrong() <INSTALL_DIR>\wp-includes\functions.wp-scripts.php:47
[26-Apr-2018 04:38:09 UTC] PHP 10. trigger_error() <INSTALL_DIR>\wp-includes\functions.php:4147
[26-Apr-2018 04:38:09 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.www.ads-software.com/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in <INSTALL_DIR>\wp-includes\functions.php on line 4147
[26-Apr-2018 04:38:09 UTC] PHP Stack trace:
[26-Apr-2018 04:38:09 UTC] PHP 1. {main}() <INSTALL_DIR>\index.php:0
[26-Apr-2018 04:38:09 UTC] PHP 2. require() <INSTALL_DIR>\index.php:17
[26-Apr-2018 04:38:09 UTC] PHP 3. require_once() <INSTALL_DIR>\wp-blog-header.php:13
[26-Apr-2018 04:38:09 UTC] PHP 4. require_once() <INSTALL_DIR>\wp-load.php:37
[26-Apr-2018 04:38:09 UTC] PHP 5. require_once() <INSTALL_DIR>\wp-config.php:129
[26-Apr-2018 04:38:09 UTC] PHP 6. include_once() <INSTALL_DIR>\wp-settings.php:305
[26-Apr-2018 04:38:09 UTC] PHP 7. wp_enqueue_style() <INSTALL_DIR>\wp-content\plugins\wp-spell-check\wpspellcheck.php:55
[26-Apr-2018 04:38:09 UTC] PHP 8. _wp_scripts_maybe_doing_it_wrong() <INSTALL_DIR>\wp-includes\functions.wp-styles.php:165
[26-Apr-2018 04:38:09 UTC] PHP 9. _doing_it_wrong() <INSTALL_DIR>\wp-includes\functions.wp-scripts.php:47
[26-Apr-2018 04:38:09 UTC] PHP 10. trigger_error() <INSTALL_DIR>\wp-includes\functions.php:4147
[26-Apr-2018 04:38:09 UTC] PHP Notice: wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.www.ads-software.com/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in <INSTALL_DIR>\wp-includes\functions.php on line 4147
[26-Apr-2018 04:38:09 UTC] PHP Stack trace:
[26-Apr-2018 04:38:09 UTC] PHP 1. {main}() <INSTALL_DIR>\index.php:0
[26-Apr-2018 04:38:09 UTC] PHP 2. require() <INSTALL_DIR>\index.php:17
[26-Apr-2018 04:38:09 UTC] PHP 3. require_once() <INSTALL_DIR>\wp-blog-header.php:13
[26-Apr-2018 04:38:09 UTC] PHP 4. require_once() <INSTALL_DIR>\wp-load.php:37
[26-Apr-2018 04:38:09 UTC] PHP 5. require_once() <INSTALL_DIR>\wp-config.php:129
[26-Apr-2018 04:38:09 UTC] PHP 6. include_once() <INSTALL_DIR>\wp-settings.php:305
[26-Apr-2018 04:38:09 UTC] PHP 7. wp_enqueue_script() <INSTALL_DIR>\wp-content\plugins\wp-spell-check\wpspellcheck.php:57
[26-Apr-2018 04:38:09 UTC] PHP 8. _wp_scripts_maybe_doing_it_wrong() <INSTALL_DIR>\wp-includes\functions.wp-scripts.php:267
[26-Apr-2018 04:38:09 UTC] PHP 9. _doing_it_wrong() <INSTALL_DIR>\wp-includes\functions.wp-scripts.php:47
[26-Apr-2018 04:38:09 UTC] PHP 10. trigger_error() <INSTALL_DIR>\wp-includes\functions.php:4147
[26-Apr-2018 04:38:09 UTC] PHP Notice: wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.www.ads-software.com/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in <INSTALL_DIR>\wp-includes\functions.php on line 4147
[26-Apr-2018 04:38:09 UTC] PHP Stack trace:
[26-Apr-2018 04:38:09 UTC] PHP 1. {main}() <INSTALL_DIR>\index.php:0
[26-Apr-2018 04:38:09 UTC] PHP 2. require() <INSTALL_DIR>\index.php:17
[26-Apr-2018 04:38:09 UTC] PHP 3. require_once() <INSTALL_DIR>\wp-blog-header.php:13
[26-Apr-2018 04:38:09 UTC] PHP 4. require_once() <INSTALL_DIR>\wp-load.php:37
[26-Apr-2018 04:38:09 UTC] PHP 5. require_once() <INSTALL_DIR>\wp-config.php:129
[26-Apr-2018 04:38:09 UTC] PHP 6. include_once() <INSTALL_DIR>\wp-settings.php:305
[26-Apr-2018 04:38:09 UTC] PHP 7. wp_enqueue_script() <INSTALL_DIR>\wp-content\plugins\wp-spell-check\wpspellcheck.php:58
[26-Apr-2018 04:38:09 UTC] PHP 8. _wp_scripts_maybe_doing_it_wrong() <INSTALL_DIR>\wp-includes\functions.wp-scripts.php:267
[26-Apr-2018 04:38:09 UTC] PHP 9. _doing_it_wrong() <INSTALL_DIR>\wp-includes\functions.wp-scripts.php:47
[26-Apr-2018 04:38:09 UTC] PHP 10. trigger_error() <INSTALL_DIR>\wp-includes\functions.php:4147I was getting the following error: Warning: array_merge(): Argument #1 is not an array in /homepages/3/d88752171/htdocs/app578897945/wp-includes/cron.php on line 439
Disabling the WP Spell Check Plug in resulted in the error going away.
Any thoughts on how to fix this?
Installation caused a whie screen on my admin dashboard, deleting the plugin via FTP fixed this.
I’ll try again on my test site to see if it’s a conflict with theme or other plugin.
]]>WP Spell Check Version 6.7.1
All Plugins disabled.
When I try to “Network Activate” this plugin I get the dreaded “You do not have Sufficient Permissions to Access This Page”.
With Debug on i get…
Notice: Constant WP_CRON_LOCK_TIMEOUT already defined in wp-config.php on line 98
Notice: Constant AUTOSAVE_INTERVAL already defined in wp-config.php on line 99
Notice: Constant WP_POST_REVISIONS already defined in wp-config.php on line 100
Notice: Constant EMPTY_TRASH_DAYS already defined in wp-config.php on line 101
Warning: Cannot modify header information – headers already sent by (output started at wp-config.php:98) in wp-admin/includes/misc.php on line 1114
Warning: Cannot modify header information – headers already sent by (output started at wp-config.php:98) in wp-includes/pluggable.php on line 1216
Warning: Cannot modify header information – headers already sent by (output started at wp-config.php:98) in wp-includes/pluggable.php on line 1216
It seems to work ok if I activate it at the site level.
]]>Hi their it looks realy reeely great and thanks for the ideas!
I ran into this bug with just ‘the theme 2017. Plugin could not be activated because it triggered a fatal error. Warning: require_once(admin/wpsc-empty-results.php): failed to open stream: No such file or directory Fatal error: require_once(): Failed opening required ‘admin/wpsc-empty
I can try it with some other theme and see if it’s that.
]]>Can’t get this plugin to work.
First, it says it finds errors but then there’s nothin in the error table.
https://image.ibb.co/d27hWR/Screen_Shot_2017_10_24_at_19_12_11.png
Second, it says it’s scanned XXX words but also shows it’s scanned 0 pages/posts –?how is that possible?
https://image.ibb.co/fNrRrR/Screen_Shot_2017_10_24_at_19_12_19.png
Do help! ??
]]>Hello, I have been using this plugin for a while without issue but at some point noticed when I try to add a featured image that the usual lightbox display for choosing media doesn’t work when this plugin is activated (it’s a more generic display of media and you can’t choose anything… it’s not in the standard WP lightbox media selection screen). When I deactivate it then all is as it should be. Maybe some recent update is causing trouble with media selection?
]]>No error logs, nothing, no matter how much time I let it run. I tried on php versions 5.6, 7 and HHVM. No luck.
]]>If one editor adds a word to the dictionary, will other users also need to add it, or do the users share one dictionary?
]]>When I installed this plugin under the /wordpress, logo-icon-16×16.png because might be 404 because its url is hard-coded as /wp-content/plugins/wp-spell-check/images/logo-icon-16x16.png in global-admin-styles.css.
Hi WP Spell Check developer,
There seems to be a bug. After activating the plugin, I am immediately locked out of wp-admin. (“You don’t have permission to access that page” or something like that.)
These are the errors from the log:
PHP Notice: Undefined variable: networkwide in /nas/content/staging/telmate/wp-content/plugins/wp-spell-check/wpspellcheck.php on line 1640
PHP Notice: Use of undefined constant AUTH_COOKIE – assumed ‘AUTH_COOKIE’ in /nas/content/staging/telmate/wp-includes/pluggable.php on line 764
PHP Notice: Use of undefined constant LOGGED_IN_COOKIE – assumed ‘LOGGED_IN_COOKIE’ in /nas/content/staging/telmate/wp-includes/user.php on line 333
We have WordPress 4.5.2 running Enfold theme.
]]>Hi, i want to run this plugin in a site with english and spanish versions. Everything seems to work ok on english version. But on spanish version of the site is breaking urls and showing 500 Internal Server Error on most pages in frontend. Might that be something related with the thing that plugin doesn’t work / support spanish language?
]]>I can’t activate the plugin, due to the following fatal error: “Parse error: syntax error, unexpected ‘[‘ in /var/www/learn/wp-content/plugins/wp-spell-check/admin/wpsc-framework.php on line 1221”. What is wrong?
]]>Never completes….
]]>Hi, here is a warning error i’m getting in both “My Dictionary” and “Ignore List”:
Dictionary:
<th scope="row" class="check-column"><br>
<b>Warning</b>: sprintf() expects at least 1 parameter, 0 given in <b>/Applications/XAMPP/xamppfiles/htdocs/mobomo/mobomo2016/wp-content/plugins/wp-spell-check/admin/wpsc-dictionary.php</b> on line <b>91</b><br>
</th>Ignore List:
<th scope="row" class="check-column"><br>
<b>Warning</b>: sprintf() expects at least 1 parameter, 0 given in <b>/Applications/XAMPP/xamppfiles/htdocs/mobomo/mobomo2016/wp-content/plugins/wp-spell-check/admin/wpsc-ignore.php</b> on line <b>63</b><br>
</th>Any ideas? I’d just downloaded the plugin.
]]>