Incompatible with Search Autocomplete [#1574084]

The wysiwig is no longer showing up with ckeditor, seems to have been broken during the recent D7 core update.

As the title, the editor is showing up when you go to the structure/content types manage fields/ text processing default value, but not when you go to add content through the live site.

The wysiwig + ckeditor combo was working well until the latest D7 core update but sadly is broken for me now.

I have tried both wysiwig 7.x-2.1 and the dev version, also I updated my version of ckeditor hoping this would fix the issue but I have had no luck :(

Also I have tried the usual suspects: clear cache (several times), checked permissions etc

Any help as to why it's no longer showing up would be awesome.

Many thanks

Comments

Comment #1

Babymaggie commented 12 May 2012 at 18:15

OOPS! seems I may have been looking in the wrong area for my problem.

After trying various things (different editors) even ckeditor module without wysiwig (Which I cannot get on with) nothing had worked so far.

As a last ditch attempt I tried 1 by 1 turning off my last installed modules and I think I have found the culprit!

Turns out it's not to do with the last core update but the module search autocomplete which does'nt play nicely with wysiwig.

I disabled Search Autocomplete 7.x-2.3 and ckeditor showed up again.

Is there any way I can get the 2 modules to work peacefully together?

Would this be an issue for wysiwig or Search Autocomplete? I would love to get these 2 to going!

many thanks

Comment #2

Babymaggie commented 12 May 2012 at 20:00

Priority:

Critical

» Major

Comment #3

twod

Swedish

Sweden

commented 24 May 2012 at 17:31

Component:	Editor - CKEditor	» Code
Priority:	Major	» Normal
Status:	Active	» Postponed (maintainer needs more info)

Sorry, putting this back to normal since the problems only happen with certain module combinations.
Changing the Component field since it happens both with CKEditor and other editors.

I don't have a setup with Search Autocomplete to test with so I can only guess here. I took a quick look at their code and based on it I'm assuming autocompletion happens via an AJAX operations in the background, which can be a tricky situation for the editors. They also seem to have a lot of code manipulating the current selection range and field values, which could indeed conflict with how editors manage content Most of them hide the original textarea - which can throws exceptions in some browsers if trying to get the selection - and don't actually update it until just before the form is submitted, so what the selection returns might not be what the user thinks is selected.

Are there any errors in the browser's JavaScript console at any time?
Which browser(s) have you tested with?