WordPress.org

Make WordPress Core

Opened 2 years ago

Closed 21 months ago

Last modified 21 months ago

#23343 closed enhancement (wontfix)

tinymce supports sevaral spellchecker but there is no option to configure it in wordpress

Reported by: mark-k Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: TinyMCE Keywords:
Focuses: Cc:

Description

tinymce configuration is in wp-includes\js\tinymce\plugins\spellchecker\config.php, at seems to support pspell, pspellshell, google spellchecker and rpc.

Will be nice if it will be possible to configure it. A use case is create a network installation for a company which want to have its own vocabulary shared among all its writers.

Change History (9)

comment:1 @azaozz2 years ago

  • Keywords close added

It is quite easy to configure this when you have full access to your server. TinyMCE has a setting for the spellchecked backend URL. You can move the backend anywhere and configure it, then it would take a simple one-line WordPress plugin to "tell" TinyMCE the new location using the 'tiny_mce_before_init' filter.

Last edited 2 years ago by azaozz (previous) (diff)

comment:2 @SergeyBiryukov2 years ago

  • Component changed from Editor to TinyMCE

comment:3 @ryanduff23 months ago

Related, it looks like google may have scrapped the spellcheck API. Reports of numerous failures across multiple versions of WP.

From TinyMCE forums: http://www.tinymce.com/forum/viewtopic.php?id=30779

Definitely an upstream issue as far as defaults, but if there's a way we can override in core to use another service, that'd be great.

comment:4 @ryanduff23 months ago

  • Keywords 2nd-opinion added; close removed
  • Type changed from enhancement to defect (bug)

I'm setting this to bug because it appears the API is broken at this point so more than an enhancement.

comment:5 @helen23 months ago

  • Keywords close added; 2nd-opinion removed
  • Type changed from defect (bug) to enhancement

We don't need a UI option for this, though. I think a new ticket is warranted for the API being broken.

comment:6 @ryanduff23 months ago

  • Keywords 2nd-opinion added; close removed
  • Type changed from enhancement to defect (bug)

10-4. Was just about to add another update, but I'll open and reference a new ticket w/ that info.

comment:7 @ryanduff23 months ago

  • Keywords close added; 2nd-opinion removed
  • Type changed from defect (bug) to enhancement

Whoops. Didn't refresh editor after Helen's comment and it reset keywords.

Opened #24789

Last edited 23 months ago by ryanduff (previous) (diff)

comment:8 @c3mdigital21 months ago

  • Keywords close removed
  • Resolution set to wontfix
  • Status changed from new to closed

Spellcheck button removed in [24745] .

comment:9 @SergeyBiryukov21 months ago

  • Milestone Awaiting Review deleted
Note: See TracTickets for help on using tickets.