I previously installed WYSIWYG, then uninstalled and deleted so I could switch to another editor. When I switched back to WYSIWYG, I get the error:

Notice: Undefined index: wysiwyg_profile_overview in drupal_retrieve_form() (line 752 of /var/ww/drupal/includes/form.inc).
Warning: call_user_func_array() expects parameter 1 to be a valid callback, function 'wysiwyg_profile_overview' not found or invalid function name in drupal_retrieve_form() (line 787 of /var/www/drupal/includes/form.inc).

Removing and reinstalling the module doesn't do anything to resolve this issue.

Comments

Anonymous’s picture

Anonymous (not verified) commented

Ok, I fixed it. However, the resolve was ridiculous. I spend half an hour pruning any instance of the string "ckeditor" and "wysiwyg" in my database via a dump. I think the uninstall script should be updated to more deeply prune any traces.

twod’s picture

twod
Primary language Swedish
Location Sweden
commented
Status: Active » Postponed (maintainer needs more info)

I would expect these types of notices/warning if the module was simply deleted without being disabled first and one tried to navigate to the editor profile overview form, or if wysiwyg.admin.inc was missing. Or perhaps if the installation was somehow interrupted after menu entries got created, but before the form builder function was registered, if that's even possible.

Flushing all caches after [un]installing modules should take care of issues where the form cache doesn't match which form builder function actually exist.

The D7 version of Wysiwyg doesn't have a disable or uninstall routine, as all the traces of it is supposed to be erased by Drupal itself.
Its database tables are automatically removed as well, based on the hook_schema() implementation, when it's being uninstalled.

Can you reproduce this on a clean D7 installation by installing, enabling, disabling, uninstalling and reinstalling/enabling Wysiwyg?

twod’s picture

twod
Primary language Swedish
Location Sweden
commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Without further details about the problem I can only close this issue. Please re-open it if you can provide the requested information.