Whenever I enable the EntityAPI module, all content from my node types of type "body" is no longer visible (See attached screen shots). Disabling the EntityAPI module returns all my nodes back to their orignal glory. I've updated Core, all my modules and even installed the dev version of EntityAPI and I still get the same result.

When Entity API is enabled, I get this error when viewing my content types (this is the "basic page"):
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
File (field_file) field requires the File widget provided by file module
Content Reference (field_content_reference) field requires the Autocomplete text field widget provided by node_reference module

Additionally, admin/reports/fields comes back saying there are not any fields defined. This is solved by disabling entity api.

I look forward to anybody's input, many good modules depend on this api and I'd like to use them.

CommentFileSizeAuthor
Screen Shot 2012-08-10 at 6.07.13 AM.png281.93 KBvangorra
Screen Shot 2012-08-10 at 5.56.19 AM.png110.41 KBvangorra
Screen Shot 2012-08-10 at 5.56.06 AM.png80.47 KBvangorra
Screen Shot 2012-08-10 at 5.58.09 AM.png149.97 KBvangorra

Comments

vangorra’s picture

vangorra commented
Status: Active » Closed (won't fix)

At the time of writing this, I'm running Drupal 7.15.
This appears to be a bug caused by drupal core. I'm not sure what caused it, but the text module was disabled after enabling entity api. I manually enabled just the text module and everything is working perfectly now. Very odd.

vangorra’s picture

vangorra commented

At the time of writing this, I'm running Drupal 7.15.
This appears to be a bug caused by drupal core. I'm not sure what caused it, but the text module was disabled after enabling entity api. I manually enabled just the text module and everything is working perfectly now. Very odd.

vangorra’s picture

vangorra commented

For anybody who comes across this in the future. My problem still persists. For a while it seemed to be working, but that is caused by this issues spastically breaking and fixing itself.

I noticed the problem occurs each time the site cache is cleared. Which means this will happen each time you view the modules page.

Don't use the overlay, after a node is rendered with this broken, it will remain broken until these steps are performed.
To get things working:
Clear the site cache in Configuration -> Performance
Manage the fields of one of your content types.

vangorra’s picture

vangorra commented
Project: Entity API » XML sitemap
Version: 7.x-1.0-rc3 » 7.x-2.0-beta1
Component: Core integration » xmlsitemap_node.module
Assigned: Unassigned » vangorra

I have isolated the problem. The XML Sitemap Node beta module was causing all the trouble. I upgraded XML Sitemap to its current rc1 release and all the problems went away. Yeah!!

I hope this helps somebody in the future. Sorry to the Entity API guys for this thread clogging their issue queue.

millionleaves’s picture

millionleaves commented

I was noticing this issue occur when creating new content types. The Text module was already enabled.

I'm running XML Sitemap Node v7.x-2.0-rc2 and Entity API v1.0.

I found that disabling the XML Sitemap Node module fixed the issue - the Body field was restored to my new content type. Re-enabling the module did not re-introduce the problem, at least not immediately. Will monitor and report back if appropriate.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Category: bug » support
Status: Closed (won't fix) » Postponed (maintainer needs more info)

I have literally no idea how XML sitemap would cause anything to do with messing with the presentation of your nodes. None at all. There is no code that should affect it...

It sounds actually like there is a bug with corrupted cache, indicated by saying there are no fields available.

Unless someone can actually point to a specific error or line of code in XML sitemap node, this is complete mystery to me.

millionleaves’s picture

millionleaves commented

Yeah, I remain stumped, but as long as I have a workaround I'm not too bothered.

Just happened again. I rather unwisely changed the machine name of a content type, with various knock-on effects, one of which was that this issue popped up again for all of the fields in the content type - none of them were available. I disabled/re-enabled the XML Sitemap Node module and all was good again.

Very weird.

millionleaves’s picture

millionleaves commented
Issue summary: View changes

Adding additional findings.

bpadaria’s picture

bpadaria commented
Issue summary: View changes

I experience this issue with APC cache enabled.

Solution mentioned in #3 works for me.

Thanks vangorra!

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Closing as I don't think this is XML sitemap module at fault.