Closed (fixed)
Project:
Drupal core
Version:
7.8
Component:
field system
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
14 Sep 2011 at 23:16 UTC
Updated:
4 Mar 2014 at 02:38 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #0.0
avir commentedmissing info
Comment #1
devin carlson commentedThe errors state that multiple required modules are disabled or missing.
Do you have the core Text, Taxonomy and Image modules enabled? Can you check your Drupal installation and make sure that all of these modules exist within the /modules directory?
Comment #2
Courtney.B commentedNot sure, but maybe this should be changed to bug report?
I think I'm having the same problem as Avir, as well as what's mentioned on this forum thread and this thread.
The Text module is unchecked and gray (uncheckable) on a fresh install, no changes made. I first noticed the problem when I was installing a few other modules and it failed because the Comment module is checked but Text is not.
For now, I'm sticking with 7.7 but will be following this thread. I'm not 100% sure if this is a problem with core or a problem with the hosting (Bluehost, simple script installation). In any case, I'm more than happy to test and report results.
Comment #3
Courtney.B commentedComment #4
TWD commentedHaving exactly same problem as reported by cybl00
Drupal 7.8
Fresh install on Hostmonster (sister company of BlueHost) using Simple Scripts one click installer.
Text Module is unchecked and uncheckable.
Comment #5
TWD commented* Solved *
http://drupal.org/node/1279398
Comment #6
Anonymous (not verified) commentedSame problem with 7.8 install. wysiwyg module and ckeditor installed. text module selected okay.
Comment #7
TWD commentedDid you install via a "one click installer" program like Simple Scripts or Fantastico?
Is your hosting company Hostmonster.com or BlueHost.com
It would be good to narrow down the source of this problem,
whether it's within Drupal or in the setup installation profile
that outside parties are creating.
Comment #8
Courtney.B commentedI believe the problem comes from the "one click installer" program. I use BlueHost and Simple Scripts. Should we change the component to "Other"?
If your "one click installer" is causing this particular problem, you could either change the database manually as suggested in http://drupal.org/node/1279398#comment-4990148 or you could choose to install 7.7 via Simple Scripts, then after completing the installation, upgrade to 7.8 through Simple Scripts. I tried out both solutions on different sites and they both worked for me.
Comment #9
jkingsnorth commentedSolutions suggested
Comment #10
deker0 commentedDrupal 7.22 here with almost the exact same issue.
Running Varnish. Have EntityAPI 1.2 installed as well.
Text module is greyed out, but shows as being checked ON. Database also shows status of '1' for the Text module.
After caches are cleared periodically (we do this using Drush via a cronjob), the body of some pages become blanked out.
Going to the content type shows this -
Inactive fields are not shown unless their providing modules are enabled. The following fields are not enabled: Body (body) field requires the Text area with a summary widget provided by text module
Any help in getting this resolved would be greatly appreciated!
Comment #11
deker0 commentedAttaching a screenshot of the error I am seeing.
Also, clearing cache manually seems to resolve the issue temporarily and the page content reappears.
Comment #11.0
deker0 commentedMore info
Comment #12
caspervoogt commentedjust to chime in, I just encountered this on 7.26, with Varnish + Memcache + APC, but with Drupal caching disabled (it's a dev site). I have commented these out in my settings.php and will see if that makes the issue stop happening. Will report back here when I have some results to share.
Comment #13
caspervoogt commentedp.s. not sure why this was marked fixed.. I didn't see any actual solutions in this thread, and the issue is still happening for some people. Clearing cache is only a temporary solution.
Comment #14
Anonymous (not verified) commentedI haven't looked at this issue in a long time. It may have been related to field permissions associated with content types that were marked as Organic Groups content. With OG you have to set permissions for each field individually.
Comment #15
caspervoogt commentedI'm not using Organic Groups. I'm also not using Field Permissions, of that matters. I have found the issue recurring, even after I disabled Memcache/Varnish/APC integration in settings.php I have now also disabled those modules, in case they were still interfering. Will see if that makes a difference.