Implement browser side of spellchecking

Bug #398940 reported by Paul Everitt
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KARL3
Fix Released
Medium
Derek DeVries

Bug Description

Backlog ID: 4

Primary goal is to get TinyMCE-based spellchecking integrated into the editor widget. The spellchecker is here:

   http://wiki.moxiecode.com/index.php/TinyMCE:Plugins/spellchecker

Secondary goals and notes
========================

- Make sure the plugin turns off browser-side spellchecking in FF and/or Safari

- Get some initial testing in place JavaScript, and see if we can test that the spellchecker doesn't fail horribly.

- Get Derek to the point of closing a bug in Launchpad and making a commit in the repo. Mike might need to get with ChrisM about swapping SSH keys.

- If you login and click Communities, then click Add Community, you'll get an editor.

- You *might* need to put your sandbox in "js_devel_mode". If you edit etc/karl.ini you'll find the js_devel_mode to set to true and your <head> will have the fully decomposed sources.

Tags: editor backlog
description: updated
tags: added: backlog
Revision history for this message
Paul Everitt (paul-agendaless) wrote :

I'll slot this for next week (M24) as Derek needs Mike for wrapping this up.

Changed in karl3:
milestone: none → m24
Changed in karl3:
status: New → Fix Committed
Revision history for this message
Nat Katin-Borland (nborland) wrote :

Spell check seems to be working on the blog, but when I hit submit I'm getting an error box and I can't figure out what the error is. Take a look at the screenshot.

Revision history for this message
Paul Everitt (paul-agendaless) wrote : Re: [Bug 398940] Re: Implement browser side of spellchecking

I have a feeling that when MikeN said "wait till I finish writing the
tests", I should have waited.

Nat, we'll take a look.

--Paul

On Jul 23, 2009, at 2:00 PM, Nat Katin-Borland wrote:

> Spell check seems to be working on the blog, but when I hit submit I'm
> getting an error box and I can't figure out what the error is. Take a
> look at the screenshot.
>
> ** Attachment added: "Spellcheck error.JPG"
> http://launchpadlibrarian.net/29425803/Spellcheck%20error.JPG
>
> --
> Implement browser side of spellchecking
> https://bugs.launchpad.net/bugs/398940
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Porting KARL to a new architecture: Fix Committed
>
> Bug description:
> Backlog ID: 4
>
> Primary goal is to get TinyMCE-based spellchecking integrated into
> the editor widget. The spellchecker is here:
>
> http://wiki.moxiecode.com/index.php/TinyMCE:Plugins/spellchecker
>
> Secondary goals and notes
> ========================
>
> - Make sure the plugin turns off browser-side spellchecking in FF
> and/or Safari
>
> - Get some initial testing in place JavaScript, and see if we can
> test that the spellchecker doesn't fail horribly.
>
> - Get Derek to the point of closing a bug in Launchpad and making a
> commit in the repo. Mike might need to get with ChrisM about
> swapping SSH keys.
>
> - If you login and click Communities, then click Add Community,
> you'll get an editor.
>
> - You *might* need to put your sandbox in "js_devel_mode". If you
> edit etc/karl.ini you'll find the js_devel_mode to set to true and
> your <head> will have the fully decomposed sources.

Revision history for this message
Nat Katin-Borland (nborland) wrote :

The problem might have to do with blogs in private communities. Wikis seem to work fine...

Revision history for this message
Mike Naberezny (mnaberez) wrote :

I was able to duplicate this issue. When I create a public community, I am able to add a new blog post. When I create a private community and try to add a blog post, I get the same error as Nat's screenshot. In both cases, I did not use the spell check feature. I believe that this might be unrelated to spell check.

Revision history for this message
Shane Hathaway (shane-hathawaymix) wrote :

I just fixed an issue with the blog entry and wiki page forms in private communities. Nat and Mike N, please try again.

Revision history for this message
Mike Naberezny (mnaberez) wrote :

Yes, the fix Shane committed in r3692-3693 for private communities solves this issue for me.

Revision history for this message
Nat Katin-Borland (nborland) wrote :

Seems to work now! Thanks guys

Revision history for this message
Paul Everitt (paul-agendaless) wrote :

Nat says it is good.

Changed in karl3:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.