I am getting the following error messages in my Error Log...

Warning: Missing argument 4 for wysiwyg_filter_filter_wysiwyg_process(),
called in /u01/www/vhosts/www..../httpdocs/sites/all/modules/ckeditor/includes/ckeditor.page.inc
on line 189 and defined in wysiwyg_filter_filter_wysiwyg_process()
(line 25 of /u01/www/vhosts/www..../httpdocs/sites/all/modules/wysiwyg_filter/wysiwyg_filter.pages.

it repeats above error for missing argument 4, 5 and 6 and then this error:

Notice: Trying to get property of non-object in wysiwyg_filter_filter_wysiwyg_process() (line 36 of /u01/www/vhosts/www.../httpdocs/sites/all/modules/wysiwyg_filter/wysiwyg_filter.pages.inc).

WYSIWYG filter 7.x-1.6-rc2
CKeditor v 7.x-1.8
Any ideas how I can fix this? I have had to disable WYSIWYG because although it was still working, it was really slowing my site down.

Members fund testing for the Drupal project. Drupal Association Learn more


fantom84’s picture

I have this error too
when I use taxonomy field this error shows

herderwu’s picture

I forget to attached patch, sorry. please see attached file next.

herderwu’s picture

Status: Active » Needs review
625 bytes

the patch file.

arnoldbird’s picture

The patch in #3 seems to address the first warning in the bug report, but not the notice: Trying to get property of non-object in wysiwyg_filter_filter_wysiwyg_process()

GaëlG’s picture

Status: Needs review » Needs work

arnoldbird is right.

GaëlG’s picture

Status: Needs work » Reviewed & tested by the community

My bad. The second error is addressed in #1728318: [D7] Text format filters are not properly given $format; cannot look up their per-format settings. Use both patches and it should work.

beeradb’s picture

Just wanted to chime in and help get this some traction. This patch is a super straightforward way to deal with optional function params. Gets a +1 from me as well.

stefan.r’s picture

Issue summary: View changes
Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.