Forum Replies Created

Viewing 15 replies - 1 through 15 (of 19 total)
  • Plugin Author WebSpellChecker

    (@webspellchecker)

    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.

    Plugin Author WebSpellChecker

    (@webspellchecker)

    @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.

    Plugin Author WebSpellChecker

    (@webspellchecker)

    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.

    Plugin Author WebSpellChecker

    (@webspellchecker)

    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.

    Plugin Author WebSpellChecker

    (@webspellchecker)

    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!

    Plugin Author WebSpellChecker

    (@webspellchecker)

    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.

    Plugin Author WebSpellChecker

    (@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.

    Plugin Author WebSpellChecker

    (@webspellchecker)

    @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: support@webspellchecker.net. 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,

    Plugin Author WebSpellChecker

    (@webspellchecker)

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

    Plugin Author WebSpellChecker

    (@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,

    Plugin Author WebSpellChecker

    (@webspellchecker)

    Hello,

    Thank you for using our WProofreader plugin for WordPress.

    As for now, there is no way to switch the plugin off for a whole post except the option to disable it in the general WordPress settings. But thank you for letting us know that it’s something you’d like to see. We’ve forwarded your request to consideration to our technical team so that they can take it into account when making development plans.

    We apologize for any inconvenience.

    Plugin Author WebSpellChecker

    (@webspellchecker)

    Hi @neddonovan13,

    We would like to inform you that we fixed the issue with not saved changes in our release 2.3. Please install the newer version to solve the issue.

    Please confirm if everything works after the update.

    Plugin Author WebSpellChecker

    (@webspellchecker)

    @lisaweb,

    Just for the records here. Thanks to your help with the additional information, the issue has been fixed and a new updated version of plugin is released.

    Awaiting your feedback.

    Plugin Author WebSpellChecker

    (@webspellchecker)

    That is way too strange, as I’ve just checked the plugin and Spanish is there. Could you please go to orange badge button –> Settings –> Languages and check if you see Spanish listed?

    Plugin Author WebSpellChecker

    (@webspellchecker)

    Just for the information about the root cause of the problem. Gutenberg doesn’t re-checked the changes (replaced words) which are made by 3-rd party scripts before Saving/Publishing.

    As ‘temp’ solution, before hitting Save/Update, please try just to add space/remove in the post, and then save the post. With this action, Gutenberg will recheck changes, including the replaced words.

Viewing 15 replies - 1 through 15 (of 19 total)