Page 1 of 1
Disable Automatic Spell Checker
Posted: Thu Aug 14, 2025 3:46 pm
by aujunior
Good morning,
We would like to disable the automatic spell checker in Oxygen Web. We attempted to use the setting "spell.check.options>automaticSpellCheck>false" within the options.xml file, but the system did not deactivate the feature.
We also tried "autocorrect.feature.state>false", but again, it didn’t work.
We found that disabling "Preferences > Enable automatic spell checking" sets the variable -oxy-core-spellcheck.enabled>false in Browser Local Storage, which effectively solved the issue.
However, we want this feature to be disabled by default for all users, without requiring them to manually change the setting.
Could you please advise us on how to configure this as the default in our framework?
Thank you in advance!
image.png
image.png
Re: Disable Automatic Spell Checker
Posted: Thu Aug 14, 2025 4:12 pm
by cosminef
Hello,
To disable spellcheck, you can add this entry [1] in
options.xml according to the documentation. Alternatively, there is the option for the property set in the browser's local storage:
-oxy-core-spellcheck.enabled to be set programmatically, depending on use cases, to either false or true.
[1]
https://www.oxygenxml.com/doc/ug-webaut ... checker%3A
Best,
Cosmin
Re: Disable Automatic Spell Checker
Posted: Thu Aug 14, 2025 6:22 pm
by aujunior
Hello Cosmin,
I tested the "preferredChecker=2" option, but unfortunately it did not work.
Could you kindly show how to programmatically set the -oxy-core-spellcheck.enabled parameter?
Additionally, please note that we are using version 27.0 of Oxygen Web.
Re: Disable Automatic Spell Checker
Posted: Mon Aug 18, 2025 12:14 pm
by cosminef
Hello,
I tested the "preferredChecker=2" option, but unfortunately it did not work.
Setting the entry in
options.xml will disable the spellcheck functionality, but it will still appear as active in the UI. Are you still seeing spellcheck errors after setting that entry in
options.xml? Did you restart the server after modifying the
options.xml file?
Could you kindly show how to programmatically set the -oxy-core-spellcheck.enabled parameter?
Please note that the
-oxy-core-spellcheck.enabled setting stored in local storage will be overridden by the value set through the user interface (UI). Therefore, relying on the local storage value for this option is not recommended.
If you are encountering the "Displaying only the first 500 spelling errors" message, it may be due to the fallback mechanism defaulting to English. To resolve this, you can set the
xml:lang attribute on the root element of your documents to the appropriate language code. This will prevent the fallback to English and ensure that the correct language is used.
Best,
Cosmin
Re: Disable Automatic Spell Checker
Posted: Fri Aug 22, 2025 2:11 pm
by aujunior
Hi Cosmin,
Setting the entry in options.xml will disable the spellcheck functionality, but it will still appear as active in the UI. Are you still seeing spellcheck errors after setting that entry in options.xml? Did you restart the server after modifying the options.xml file?
Indeed, modifying the options.xml file resolved the issue with the message "Displaying only the first 500 spelling errors." As you mentioned in your response, the system disabled the automatic functionality but kept the button active in the interface.
However, the current issue is that when we click the spell check button, the system does not perform any correction. When we disable the feature via the preferences menu, the automatic spell check is correctly turned off, but the button still works as expected when needed.
Our intention is to disable only the automatic spell check while keeping the manual correction functionality available through the interface button.
Best regards,
Audye
Re: Disable Automatic Spell Checker
Posted: Mon Aug 25, 2025 3:52 pm
by cosminef
Hello,
Thank you for your feedback and clarification.
You are right, by using that entry in options.xml, the spell check option is disabled both automatically and manually when pressing the button.
We would like to understand your use case in detail and wanted to know why the automatic spell checking is inconvenient for you, so that we can provide you with the most suitable solution.
Best,
Cosmin