Hello,
Brief description:
I have a really weird behaviour here: whenever I publish and promote to frontpage a "video" content type with a re-used term reference field I get a warning on the frontpage, but not on node's detail.
Detailed description
- I have several content types which several fields. Those content types seem to work fine.
- Whenever I create a content type called video, it works fine till I re-use certain taxonomy fields (the ones which create the error are always the same).
- Whenever I publish a video content type I get a warning (see below) on the frontpage, but nothing on node's detail.
- It doesn't matter if the two mentioned fields are left blank or not: the error always appear in frontpage, even after refreshing or viewing it as anonymous user.
- I deleted the content type and created it again and it works fine till I add the two mentioned fields.
- I have several term reference fields wich work fine, but I can't find any difference between those two fields and the others.
* Notice: Undefined index: taxonomy_term en taxonomy_field_formatter_view() (línea 1368 de /modules/taxonomy/taxonomy.module).
* Notice: Trying to get property of non-object en entity_extract_ids() (línea 7286 de /includes/common.inc).
* Notice: Trying to get property of non-object en taxonomy_term_uri() (línea 148 de /modules/taxonomy/taxonomy.module).
* Notice: Trying to get property of non-object en taxonomy_field_formatter_view() (línea 1372 de /modules/taxonomy/taxonomy.module).
* Notice: Undefined index: taxonomy_term en taxonomy_field_formatter_view() (línea 1368 de /modules/taxonomy/taxonomy.module).
* Notice: Trying to get property of non-object en entity_extract_ids() (línea 7286 de /includes/common.inc).
* Notice: Trying to get property of non-object en taxonomy_term_uri() (línea 148 de /modules/taxonomy/taxonomy.module).
* Notice: Trying to get property of non-object en taxonomy_field_formatter_view() (línea 1372 de /modules/taxonomy/taxonomy.module).
* Notice: Undefined index: taxonomy_term en taxonomy_field_formatter_view() (línea 1368 de /modules/taxonomy/taxonomy.module).
[etc.]
Hope anyone has a solution for this.
Thank you
Comments
Comment #1
c-c-m commentedI don't know if it matters or not, but I forgot to mention that frontpage is default's "ROR" frontpage, with bartik default theme.
Comment #2
c-c-m commentedTried again with a custom view and the problem persists. Any help with this, please?
Comment #3
c-c-m commentedI found a workaround to this problem: Instead of re-using the same field, I created a new term reference field which reads/write the same vocabulary and the warnings are gone.
The problem, though is still not solved, and I'd like to know why is this happening and how to solve it in a real way.
Comment #4
bradley.beckner commentedI have had a very similar thing happen. I am new to the community so I do not know the solution. I will tell you what I did to change things. Since it was on the home page I made an assumption that it had to to with the teaser. I went and started changing things on the teaser section of the last thing I had done. (In my case photo's) Once I set all the drop-downs in the teaser to make sense i.e. to show and not show like they were positioned in the table my issue went away.
This took some time and trying to make work but I guess it will get fixed sooner or later.
Comment #5
c-c-m commentedIn my case it didn't matter if such field was displayed or not in teaser view: the error was always displayed
Comment #6
kalilo commentedI can reproduce the same error.
Comment #7
kalilo commentedDoes any one know if the current version of Drupal still reproduce this bug?
Comment #8
markosaurus commentedI have a very similar issue after updating a load of modules at the weekend on a development server I am building. I have a LOT of modules installed and am almost completed with this build phase, so this is causing me a lot of problems at the moment, in fact, it's now my number 1 priority as this has stopped the entire build. I'm going to look into this now and see what I can find after the first hour of investigation.
This occurs for me on a page which is a custom page served through the "views" module (i.e. outputting info from Drupal 7 into a custom template through the use of cck and custom fields.)
I need to get an understanding of what people have as a setup (I'm not listing all of my modules as I have around 30 installed). I'm running Drupal 7.7 as of the weekend, but just noticed 7.8 is now out, so I'll install that, check everything else is up to date and then report back.
K, thx, bai
Comment #9
markosaurus commentedInstalled that core update for Drupal 7 and also one for CKEditor (my wysiwyg editor of choice) and that made things a whole lot worse!
Now I'm getting this instead (Not a warning as before, but rather an error now, the primary nav doesn't even render.);
EntityMalformedException: Missing bundle property on entity of type node. in entity_extract_ids() (line 7389 of /home/dixon/public_html/dev/includes/common.inc)...
This is rapidly putting me off using Drupal 7, and I'm a full-time developer, so I can only imagine what this is like for hobbyists.
Gah!
Comment #10
aspafford commented@markosaurus, the problem you've reported in #9 is being discussed here #1268006: Get error when upgrading from 7.7 to 7.8 EntityMalformedException:Missing bundle property on entity of type file. in entity_extr
Comment #11
kenjiru commentedI have the same problem in Drupal 7.8, when trying to preview a node.
Comment #12
xjmMarked two issues as duplicates of this:
#1323740: Undefined index: taxonomy_term in taxonomy_field_formatter_view()
#1230612: Multiple errors when viewing Tag
Comment #13
xjmNote that this issue appears to be different from #1108534: Forum Building Error.
Comment #14
Michael-IDA commentedThis is in the thread closed as a duplicate of this issue:
http://drupal.org/node/934726#comment-5414346
Comment #15
xjmPlease provide steps to reproduce this issue, starting from "1. Install Drupal 7.x with the standard profile." We need to know exactly how to reproduce this bug to fix it. It may be caused by a contributed module, so if one of the steps to reproduce is 2. "Install contributed module XYZ," we should move this issue to that module's queue.
Comment #16
clemens.tolboom[Powered by #1115636: Issue Macros and Templates - _default]
Please read Making an issue report to improve this issue report.
You could also:
Please update the issue summary by applying the template from http://drupal.org/node/1155816.
Please update the issue summary by editing the issue. This helps people to understand this issue quicker.
Comment #17
Michael-IDA commentedHi xjm,
You closed as dup: http://drupal.org/node/1323740 in which I listed extensive steps to reproduce and did a full module dump.
Best,
Sam
Comment #18
clemens.tolboom@Sam-Inet
In #1323740: Undefined index: taxonomy_term in taxonomy_field_formatter_view() there is no _new_ steps to reproduce. In http://drupal.org/node/1323740#comment-5217516 #5 & you in #6 we expressed the need for a cleaner way to reproduce the bug. I do agree your initial report had good steps what to do. But too many modules to pinpoint the problem.
So it would be great when you could recreate the minimal steps to reproduce this bug.
Thanks for keep this going :-)
Comment #19
xjmAlso, for this issue to be filed against core, the steps to reproduce should include installing only core. If a contributed module causes the issue, then it gets moved to that module's queue.
Comment #20
Eduardo_Martinez commentedSeems that problem is with Ubercart, products that have a link to
tagbroken when are listed on the standard view (first page or taxonomy term). I hope it helps; but I think that may be positive move this issue to http://drupal.org/project/issues/ubercartComment #21
MIB-2 commentedNo, this is not related to Ubercart. I do not use Ubercart, but I do have this problem.
Comment #22
Eduardo_Martinez commentedI have this problem only with nodes related to products (Ubercart), not with the other content types.
Comment #23
Robin Millette commented@Eduardo: resave your product nodes. My guess is they're using a term ID that was deleted from its vocabulary. Resaving the nodes will clear that up.
Comment #24
Eduardo_Martinez commentedThanks Robin, but this not solve this, I have the same problem than
upgrade problem to 7.12 EntityMalformedException: Missing bundle property on entity of type commenthttp://drupal.org/node/1436810 in fact I observe this sine 7.12 core update.Comment #25
Encarte commentedThere are two different error messages being reported in this issue:
- One is in #1 (Trying to get property of non-object)
- The other is in #11 (EntityMalformedException: Missing bundle)
Are they really duplicates?
I came across the message in #11 and I'll share the work around I found (maybe it will be useful for a proper fixing too).
The error showed up on a term page (not on the node default display or teaser display or the preview) of a test site with Ubercart 7.x-3.0, Entity API 7.x-1.0-rc1 and Taxonomy access fix 7.x-1.0. A particular node seemed to cause it and any term used in it would have the error on the term page (if you removed the term from the node, the term page would work again). Nothing seemed to be different about this node and then I realized that it would happen in any newly created nodes of a certain type (ubercart product). I reviewed the content type latest changes and reverted them by simply un-hiding the taxonomy fields that were recently set to hide on the teaser display. Note that there seemed to be no problem with the teaser display in views and yet the teaser display is also used on the term pages and that seems to be causing the problem. No more error message now...
Comment #26
stefmex commentedIn 7.12 I have post one issue about Ubercart and attributes..... I don't know if it is the same trouble.
http://drupal.org/node/1529276#comment-5874660
Comment #27
xjmComment #28
liza commentedpopping up to say this problem reared it's ugly head in my upgrade from 7.19 to 7.22 in a test site that i have running with a kabillion modules :P hence, i haven't been able to track down which contrib is the culprit but just letting y'all now that the solution in comment #14 stopped the error messages.
update: btw, the error message would only be triggered by cron or by visiting the status report page :\
Comment #29
allegragf commented#14 fixed the problem for me.
Comment #29.0
allegragf commentedUpdated issue summary.
Comment #37
pameeela commentedAs part of the Bug smash initiative, we are triaging issues that are marked 'Postponed (maintainer needs more info)'. Given that this issue is more than 12 months old and no steps were provided to reproduce it in Drupal core, I am marking it 'Closed (cannot reproduce)'.
If anyone believes this issue should not be closed, please provide specific steps to reproduce when reopening it.