WebSpellChecker

Hi @marywt,

We are sorry to hear that with the new release of WProofreader you lost the ability to open links. It would help us a lot if you could provide the additional technical details about your WP setup.

1. WordPress version
2. PHP version
3. List of used/enabled plugins
4. Browser and its version
5. Screenshot of the browser console when the WProofreader plugin is enabled.
6. Also, if you could record a short video it would be wonderful. You can send it to our email box: [email protected].

Looking forward to hearing back from you.

Thanks!

Dear Paul,

Thank you for the technical details provided. Our team had a discussion of your case and would like to ask you to check two more things:

1) Is the License Key field in the plugin admin panel is empty (without any symbols and spaces)? The reported error issue might be shown if the invalid activation key is used.
2) Please send the screenshots of the failed request/response (header and response information) from the network tab (*ssrv.cgi) to [email protected].

Thank you in advance,

Dear Paul,

Our first assumption is that there are no spelling errors in your blog posts, so nothing is highlighted. There is also no orange badge on the page as now it is turned off by default. All of this might cause the feeling that the plugin doesn’t work at all.

To check this, you can turn on the badge via your admin panel and also make some misspellings in your posts to verify the plugin’s operability.

If there is still an issue with the plugin, we will need to ask for additional information to reproduce the case. Please provide as much information as you can.

The technical details can be sent to <[email protected]>.

1) WordPress version;
2) The list of plugins you use;
3) PHP version;
4) Do you use a Nginx or Apache HTTP web server?
5) Also, could you send the details about the errors which appeared after updating the plugin? Perhaps these errors are stored in the hosting log files.

Hello @paulcola,

We are glad to inform you that we have just released a new WProofreader plugin version 2.6 for WordPress, which includes improvements to the integration with the Gutenberg editor. Now WProofreader will be automatically started in all editable elements of the editor without the necessity to click on each element to enable the spelling/grammar checking.

The orange badge is disabled by default for all types of elements, including the Gutenberg editor. Also, there is still a setting allowing you to reactivate the badge from the plugin’s settings page if needed.

To apply the changes please update the WProofreader plugin to the latest version.

Moreover, we are planning some other improvements regarding the plugin’s work with the Gutenberg editor. You can monitor the changes using our release notes.

We will be grateful to hear your additional feedback regarding the latest updates, and if the assessment is revised once more.

Hello @paulcola,

Thank you for giving the WProofreader plugin for WordPress a try and this feedback. We hope you will reconsider your two-star estimate after our comments.

First, we would like to note that identifying double-space is covered by grammar checking, which is available in our Pro version of the plugin, while the Free version is distributed only with the spellchecking functionality. You can subscribe to the 14-day Trial version on our website to evaluate all the benefits of the Pro version: https://webspellchecker.com/free-trial/.

Regarding Gutenberg, we completely understand that it might be annoying to click on every single Gutenberg block to proofread the text. But this is caused by the technical limitations of working with this editor. We even tried to reach the Gutenberg team to ask them to reconsider such a flow, but with no changes for a year: https://github.com/WordPress/gutenberg/issues/13620.

Today we once again checked the work of several other proofreading tools (Grammarly, LanguageTool) to understand whether someone found the way to overcome the case with Gutenberg blocks, but couldn’t find such a solution.

Nevertheless, taking into account your comments, we approved with the team some small improvements to working with Gutenberg. After the changes, the WProofreader plugin will autostart on all blocks on pages where the Gutenberg editor is identified. It means that you won’t need to click on each editor’s block to proofread the specific part of the text. We are expecting the release of these improvements next week and will write to you there once they are introduced.

Hi @acr0bit,

We are glad to inform you that we have just released a language auto-detection feature that is available as a part of the Pro package.

Now our Pro customers can specify the “Auto Detect” as the default language in their Plugins page. With the auto-detection there will be no need to switch the languages, our services will automatically detect the language for the check.

@acr0bit we are glad to hear that I was able to answer your question. By the way, I will be happy to notify you as soon as language auto-detection feature is out.

Hi @acr0bit,

You can use a single language at a time for check. The default language is the language that will be used each time on WProofreader launch. However, your users/editors can change the language on fly while they are working with WProofreader from UI settings. Go to orange bubble/badge -> hover on it –> select settings -> in the settings dialog go to language –> change the language.

Moreover, with the next release of WProofreader, we plan to add language auto-detection feature that will be available as a part of Pro package. With the auto-detection there will be no need to switch the languages.

Hi @keyivr,

The plugin doesn’t install banner ads. A while ago in the first version of the plugin there was a pop-up banner saying that this is a free version.

Back in December 2018 we released a brand new version of the plugin which doesn’t have this banner.

You can install plugin and check that there are no banner ads.

Hi @kisabelle!

That’s great news. We are glad to hear that it’s working now. Thank you for letting us know.

Hope you are satisfied with the plugin and it helps you in improving your texts. We will be very thankful if you can rate our plugin and share you feedback!

Dear @kisabelle,

Today we have tried the options how to enabled WProofreader for your case. There are two options for you to consider:

Option A. Enable WProofreader for user-edit.php:

Go to your function.php and add the next code below:

add_action( 'admin_enqueue_scripts', 'wsc_activate_bundle_in_admin_panel' );

function wsc_activate_bundle_in_admin_panel() {
    if ( class_exists( 'WProofreader' ) ) {
        $screen = get_current_screen();
        if ( 'user-edit' === $screen->id ) {

            $WProofreader = new WProofreader();
            $WProofreader->init_proofreader_js();
        }
    }
}

Option B. Enable WProofreader for whole the admin panel:

Go to your function.php and add the next code below:

add_action( 'admin_enqueue_scripts', 'wsc_activate_bundle_in_admin_panel' );

function wsc_activate_bundle_in_admin_panel() {
    if ( class_exists( 'WProofreader' ) ) {
        $WProofreader = new WProofreader();
        $WProofreader->init_proofreader_js();
    }
}

Try one of the suggested options. And let us know if it works for you.

Please note that we haven’t tested properly this functionality in all admin. So, if you find any issues or strange behavior, please report it to us.

• This reply was modified 5 years, 2 months ago by WebSpellChecker.

Dear @kisabelle,

Thank you for the additional answers and providing the URL.

Now we understood what is the problem. WProofreader is not enabled for all WP website (it works for pages, posts and custom post types).

Let us discuss internally to see if we can extend WProofreader support to other pages including /user-edit.php.

I will get back to you on Tuersday as we have a bank holiday on Monday.

@kisabelle

We’ve checked the work of our CPT for posts and pages and it works properly. Our assumption is that the place where you try to enable plugin is settings of the website.

May we ask you to send a screen of the whole page you have including URL? You can send it to our email address: [email protected]. We want to understand the type of the page where you try to enable it.

Also, could you please specify the version of your WP, ACF and the plugin itseld?

Thank you,

Thank you for the screenshots. I will pass this information to our technical team for review. We will get back to you on Monday.

• This reply was modified 5 years, 3 months ago by WebSpellChecker.

@kisabelle,

Thank you for sharing your feedback about our plugin!

We are glad to hear that you were able to configure WProofreader in the custom post types.

By default WProofreader works in the standard fields of ACF. Are you able to send us screenshot or exact type of fields that are used in ACF WYSIWYG fields in the Edit user screen?

Thank you,