I installed wysiwyg and now my configure page wont load. I also get this warning on the content page...

Error message
Warning: require_once(/hermes/bosoraweb162/b536/d5.amberlight/public_html/NaziMidwife/modules/wysiwyg/wysiwyg.admin.inc) [function.require-once]: failed to open stream: No such file or directory in menu_execute_active_handler() (line 515 of /hermes/bosoraweb162/b536/d5.amberlight/public_html/NaziMidwife/includes/menu.inc).

Comments

TwoD’s picture

Status: Active » Postponed (maintainer needs more info)

It looks like Wysiwyg hasn't been completely installed. Is the wysiwyg.admin.inc file actually there?

Btw, you have installed Wysiwyg into the folder meant for Drupal Core modules, that is only those shipped with Drupal itself.
You should extract other downloaded modules to DRUPAL_ROOT/sites/all/modules/. It helps when updating Drupal Core.
Do that (make sure you completely get rid of DRUPAL_ROOT/modules/wysiwyg and then extract the wysiwyg package to DRUPAL_ROOT/sites/all/modules/ and flush the Drupal cache.

Suggested reading: https://drupal.org/documentation/install/modules-themes/modules-7

MPARKER’s picture

I have done what you suggested and my config page still wont load. The wysiwyg.admin.inc file is there. Any thoughts? I haven't seen that warning again though.

TwoD’s picture

You might need to uninstall the module (tab in the Modules list, if it shows up there) and enable it again to have it show up. If the wysiwyg.install file was also missing, the wysiwyg database tables might not have been installed correctly and that should fix it.

If you just get a white screen, check the web server logs for error messages. You could also look up the row in the system database table where the name column is "wysiwyg" and check if the path/filename coulumn points to the correct location (/sites/all/modules/wysiwyg/wysiwyg.module)

steinmb’s picture

Issue summary: View changes
Priority: Critical » Normal
Status: Postponed (maintainer needs more info) » Fixed

Status: Fixed » Closed (fixed)

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