WebSpellChecker

Hi @shizart, we are sad to hear that you experienced issues with enabling/using our plugin. There is a video linked to the plugin description explaining how it works. Here is a link for your convenience. The plugin works only in the edit mode for pages/post and other supported elements.

There is a free version of the plugin that doesn’t require any key to get started. You just install the plugin on your WordPress website and it’s ready to use. To check how it works, you need to open any post or page for editing. And as soon as you do it, you should see red underlines for words that aren’t recognized by spelling engine.

Could you please give us a bit more information on the steps that you took and how you tested the solution to come up to the conclusion that it did nothing? Since you mentioned that you subscribed to the trial on our website, you are welcome to reach our support email address and our support team will do our best to help you in using the plugin.

Hi @davidebonfanti,

Here are the results of our investigation regarding the PHP warning in the WordPress admin panel.

Our Web developer used the latest WProofreader plugin and PHP version, and successfully activated the plugin: the necessary info was immediately pulled up, no errors reproduced.

But still we assume that warnings may appear if there is, for example, no Internet on a computer and it’s all local. Thus we added an additional check and introduced a new mini-release 2.6.7 for the WProofreader plugin with a fix for this particular warning.

Please update our proofreading plugin, and if the warning is still here, try to remove it and install a a new version from scratch. For further troubleshooting if needed, please send a full list of plugins that are in use and which theme is activated, specify the version of PHP, WordPress.

Keep us updated about your progress.

Thank you,

Hello @seacomms,

Thank you for your feedback and sorry to hear that you have a misconception about our product. You can keep using the free version of our plugin without limitations in period, but taking into account daily usage limitations. The details are below.

The free version is limited to spell checking 10,000 words per day one a single website. Upon reaching the limit, it stops working until the next day. This information is in the description of the plugin: https://ww.wp.xz.cn/plugins/webspellchecker/.

Moreover, you can find an explanation of how the usage is calculated and when you will be able to continue using the free version in our FAQ:

My website exceeded word usage quota. What does it mean?

Hope that you keep using our WProofreader plugin for WordPress and enjoy its work.

Hi @strusbobbin,

Thank you for your review.

Definitely, this is not the expected behavior for the plugin. And it looks like a support case or misunderstanding.

So, when you go to a blog post or a page and open it for editing, do you have any text on the page? Does it have any spelling issues?

I’ve just recorded a short video showing how the free version with enabled spelling and spelling autocorrect works on the post. Check the link here: https://monosnap.com/file/lBVhlQEsKFGa8kQuIInXRHkv8mOCrB

By the way, you can the link below. It spins up a new TasteWP instance with the WProofreader spell & grammar check plugin already installed. You can play with the plugin without any commitment.

Link to spin a TasteWP instance: https://tastewp.com/new?pre-installed-plugin-slug=webspellchecker&redirect=options-general.php%3Fpage%3Dspell-checker-settings&ni=true

Could you please try to reinstall/reactivate the plugin, go to any post, open it for editing. Enter the following text as a text: “Hello wrold!”. The expected behavior, the word “wrold” will be underlined with red line. Then you need to hover on the word and select one of the suggestions for correction.

If it still doesn’t work, since you are a developer, it should not be a problem for you to open the browser developer tools and check if there are any errors in the console and if there are any failed requests in the network. If any, please share it with us (you can send them via email or as links to screenshots here?

Dear @shawfactor,

It looks like the initial language was cached in your browser. Please clean your localstorage: Open development tools — Console — Type localStorage.clear () — Enter — then Local Storage — Enter to make sure that it is empty.

Could you please try to do this and let us know if your issue is resolved or not?

Hi @jessithecat,

Did you have a chance to review our questions to troubleshoot the issue?

The problem that you describe when the German words were swapped with English ones must have been caused by the fact that English language was selected for checking or remembered from the previous selection. Also, to disable autocorrect, please click on the orange badge > settings > toggle off “Correct spelling automatically”.

The plugin supports the German language as well as the list of others.

Hi @glorain,

We are happy to inform you that earlier today we released the updated version of the plugin that allows disabling the autocorrect feature as mentioned above. Please try it and provide your feedback.

Our team will be grateful if you reconsider your review based on the updates.

Regards,