I have performed a fresh install of Drupal 7 Beta 1 with the standard profile and language.
I have created a new content type which includes a title, a field text, and two "existing fields" (field_tags, field_image). I have deleted the body.
When I create a new entry with information in all fields, I get the following error in the front page (it's set up to promote entries to the front page by default):
Notice: Undefined index: taxonomy_term in taxonomy_field_formatter_view() (line 1233 of /home/ariscaiv/public_html/d7b1/modules/taxonomy/taxonomy.module).
Notice: Trying to get property of non-object in entity_extract_ids() (line 6974 of /home/ariscaiv/public_html/d7b1/includes/common.inc).
Notice: Trying to get property of non-object in taxonomy_term_uri() (line 148 of /home/ariscaiv/public_html/d7b1/modules/taxonomy/taxonomy.module).
Notice: Trying to get property of non-object in taxonomy_field_formatter_view() (line 1237 of /home/ariscaiv/public_html/d7b1/modules/taxonomy/taxonomy.module).
Notice: Undefined index: taxonomy_term in taxonomy_field_formatter_view() (line 1233 of /home/ariscaiv/public_html/d7b1/modules/taxonomy/taxonomy.module).
Notice: Trying to get property of non-object in entity_extract_ids() (line 6974 of /home/ariscaiv/public_html/d7b1/includes/common.inc).
Notice: Trying to get property of non-object in taxonomy_term_uri() (line 148 of /home/ariscaiv/public_html/d7b1/modules/taxonomy/taxonomy.module).
Notice: Trying to get property of non-object in taxonomy_field_formatter_view() (line 1237 of /home/ariscaiv/public_html/d7b1/modules/taxonomy/taxonomy.module).
However, when I click in the item, it shows correctly with no further messages. The error message is shown to authenticated and non-authenticated users. The new content type is not accepting comments, apart from that, I believe I have left everything else in its default value.
Two screenshots are included, the frontpage region with the error, and the node page with no messages.
Comment | File | Size | Author |
---|---|---|---|
#96 | 934726-96.patch | 692 bytes | rickmanelius |
#89 | 934726-89.patch | 690 bytes | rickmanelius |
#38 | field_default_prepare_view-test-only-934726-38.patch | 2.81 KB | yched |
#38 | field_default_prepare_view-934726-38.patch | 3.96 KB | yched |
#37 | field_default_prepare_view-test-only-934726-37.patch | 4.43 KB | yched |
Comments
Comment #1
Damien Tournoud CreditAttribution: Damien Tournoud commentedI cannot reproduce this.
Could you try to dump the content of
$item
at line 1233 of thetaxonomy.module
file?Comment #2
ehalber CreditAttribution: ehalber commentedI am experiencing the same issue. However, I am running the development snapshot from 10/17/2010
In addition to the default fields I have created a number of custom fields, some are text while four are terms populated by vocabularies.
Comment #3
vinazoom CreditAttribution: vinazoom commentedI have same problem when I testing Drupal New version (beta 2)
I think this cause by You create a new field act as Tag but not correct type.
if you want to create tag field, you must use Term reference type.
Delete you exist field and try that.
Good luck !
Comment #4
webchickSeems like there might be enough info here to troubleshoot this now.
Comment #5
zugaldia CreditAttribution: zugaldia commentedPlease let me know the steps I should follow if you need me to provide further info.
Comment #6
rosborn CreditAttribution: rosborn commentedIf it's any help, I have just encountered the same error message (see attached). I think it might have been caused by creating a new alias to a taxonomy term, perhaps overriding the automatic alias, but I could easily be wrong.
Comment #7
rosborn CreditAttribution: rosborn commentedActually, I was able to clear it by deleting an item of content on the front page, which is the only page where the error message was displayed. I am creating new tags - I don't know whether a previously defined tag somehow got dereferenced. Probably dangerous for me to speculate any more.
Comment #8
Taxoman CreditAttribution: Taxoman commentedNot sure where the core problem lies, but it might be affected by having the Media module enabled too. Here are my observations with Beta1:
Initially, I have enabled an image field and filefield in core CCK for several content types, including a completely new one, and they seem to work well.
I cannot add Media fields from the Media module to any content type, regardless if I disable the core CCK custom fields or not, as that causes wsod errors (not THIS error discussed here). (any of the field widget types available in Media module)
While having the core CCK fields working, no active fields from Media module (but that module is enabled), I then enabled separate "custom display settings" for full, teaser, print, etc. on the "manage display" tab for my custom CCK content type. I adjusted its default values, and set the same plus other values for each separate settings page.
That is when this error started occurring.
I think it occurs on any "listing" page that at the time of rendering actually includes one or more items from the content type that has had those settings altered. That means the front page if such content is promoted there, and any taxonomy page that would include any of those pages of that content type.
Have not had time to dig further into this, but hope these observations may help further investigations.
Comment #9
chrispomeroy CreditAttribution: chrispomeroy commentedI got the same issue, let me know what information I could provide that might help diagnosing it.
# Notice: Undefined index: taxonomy_term in taxonomy_field_formatter_view() (line 1318 of /var/www/cpomus7/modules/taxonomy/taxonomy.module).
# Notice: Trying to get property of non-object in entity_extract_ids() (line 7076 of /var/www/cpomus7/includes/common.inc).
# Notice: Trying to get property of non-object in taxonomy_term_uri() (line 148 of /var/www/cpomus7/modules/taxonomy/taxonomy.module).
# Notice: Trying to get property of non-object in taxonomy_field_formatter_view() (line 1322 of /var/www/cpomus7/modules/taxonomy/taxonomy.module).
# Notice: Undefined index: taxonomy_term in taxonomy_field_formatter_view() (line 1318 of /var/www/cpomus7/modules/taxonomy/taxonomy.module).
# Notice: Trying to get property of non-object in entity_extract_ids() (line 7076 of /var/www/cpomus7/includes/common.inc).
Comment #10
jerobins CreditAttribution: jerobins commentedWe were hoping beta3 would make this go away; alas, it did not.
Any other information i can provide to help diagnose?
My errors look the same as posted above; however, for completeness, i've included the output in a file.
Comment #11
inf CreditAttribution: inf commentedI got the same error. I use tagadelic module and I have more content types.
I created new contents in each types and added same tags to them. This error occures when I list a tag which belongs to more than one content and the contents have different types.
If the contents have the same type I didn't get this error.
Comment #12
inf CreditAttribution: inf commentedWith a little work I think I found the problem in taxonomy.module file. I changed a line (1336) in taxonomy_field_formatter_view function.
original: $term = $item['taxonomy_term'];
new: $term = taxonomy_term_load($item['tid']);
It works for me now, I hope it helps!
Comment #13
yched CreditAttribution: yched commented#12 is not the fix. $item['taxonomy_term'] is supposed to contain the taxonomy term. Fixing the bug means finding out why it isn't populated.
Also, I haven't been able to reproduce this with the tag terms in the 'Tag' vocabulary created in a default install. We really need reproducible steps triggering the bug if we want to move forward - or at worst a database dump ?
Comment #14
inf CreditAttribution: inf commented#13 here are my steps:
- I installed drupal
- after that I went to 'Structure' -> 'Content types' -> 'Add content type'
- I named the new content type ('show') then I saved it
- I opened 'Manage fields' and I selected from an existing field (I chose 'Term reference: field_tags' and 'Autocomplete term widget' from the lists.) then I saved it.
- In the next screen I left everything in default value then I clicked 'Save settings'
- then I clicked 'Add new content' and I created a new Article. I gave two tags to it (kutya, cica) then I saved it.
- then I added a new Show content. I gave two tags to it (kutya, lila) then I saved it.
- after that I opened the 'Article' typed content I created then I clicked on 'kutya' tag, then I got the error.
I updated Drupal from CVS today.
I hope it helps you to reproduce the error.
Comment #15
inf CreditAttribution: inf commented#13 I attach my db dump.
Comment #16
yched CreditAttribution: yched commentedThks @inf - no time to investigate right now, but reopening.
Comment #17
cwrstl CreditAttribution: cwrstl commentedSeeing the same thing here. Can provide dump or access to the site if needed.
Comment #18
cwrstl CreditAttribution: cwrstl commentedDo we know if this has been addressed in RC1?
Comment #19
yched CreditAttribution: yched commentedno it hasn't
Comment #20
DamienMcKennaAm unable to reproduce this following the steps in #14 above with a copy of CVS HEAD (last commit #459116) with PHP v5.2.13 as bundled with MAMP. Anyone else?
Comment #21
DamienMcKennaCould someone please post (or email me) a database dump that shows this with the latest CVS HEAD codebase?
Comment #22
yched CreditAttribution: yched commented@DamienMcKenna : inf posted a db dump in #10. I didn't find the time to deploy it and test locally so far, but if you can take a crack at it ... :-)
Comment #23
DamienMcKenna@yched: The file in #10 is a list of errors, not a database dump. I'm using MySQL so the PostgreSQL dump in #15 won't run, so I'll see if I can get pgsql installed.
Comment #24
inf CreditAttribution: inf commented@DamienMcKenna: I updated drupal from CVS now. I installed drupal again but I used MySQL db now. I followed the steps I wrote (#14) and I got the same error again.
I attached my mysql db dump.
Comment #25
mokecc CreditAttribution: mokecc commented* Notice: Undefined index: taxonomy_term in taxonomy_field_formatter_view() (line 1366 of /wwwroot/FTP951E/htdocs/modules/taxonomy/taxonomy.module).
* Notice: Trying to get property of non-object in entity_extract_ids() (line 7258 of /wwwroot/FTP951E/htdocs/includes/common.inc).
* Notice: Trying to get property of non-object in taxonomy_term_uri() (line 148 of /wwwroot/FTP951E/htdocs/modules/taxonomy/taxonomy.module).
* Notice: Trying to get property of non-object in taxonomy_field_formatter_view() (line 1370 of /wwwroot/FTP951E/htdocs/modules/taxonomy/taxonomy.module).
Comment #26
ksdhanjal CreditAttribution: ksdhanjal commentedFacing same issues with latest install; is there a fix in the works or a potential timeline ?
Comment #27
eule CreditAttribution: eule commentedhere i have same issue on the final drupal 7 release
* Notice: Undefined index: taxonomy_term in taxonomy_field_formatter_view() (line 1368 of ./modules/taxonomy/taxonomy.module).
* Notice: Trying to get property of non-object in entity_extract_ids() (line 7286 of ./includes/common.inc).
* Notice: Trying to get property of non-object in taxonomy_term_uri() (line 148 of ./modules/taxonomy/taxonomy.module).
* Notice: Trying to get property of non-object in taxonomy_field_formatter_view() (line 1372 of ./modules/taxonomy/taxonomy.module).
* Notice: Undefined index: taxonomy_term in taxonomy_field_formatter_view() (line 1368 of ./modules/taxonomy/taxonomy.module).
* Notice: Trying to get property of non-object in entity_extract_ids() (line 7286 of ./includes/common.inc).
* Notice: Trying to get property of non-object in taxonomy_term_uri() (line 148 of ./modules/taxonomy/taxonomy.module).
* Notice: Trying to get property of non-object in taxonomy_field_formatter_view() (line 1372 of ./modules/taxonomy/taxonomy.module).
Comment #28
Moparx CreditAttribution: Moparx commentedI was having this issue until I went to /admin/structure/types/manage/your_custom_content_type/display/teaser and changed my Tags field from Hidden to Link.
Comment #29
eule CreditAttribution: eule commentedyou are right! i change to inline -> text in teaser. cache cleanup, error field is gone, after i change to link and clean cache , now i dont see the error field anymore.
Comment #30
tsvenson CreditAttribution: tsvenson commentedSame here, Hiding the Tags field on teasers causes these errors. I have several more vocabularies, all are hidden for teasers, but only the Tags is needed to be changed to Link for this error to go away.
To add some more info to this, it also happened on a Views page for me, but tags are not used at all in the view on that page, nor are teasers.
Bumping to 7.0 since that's the version I am using.
Comment #31
Tom.Camp CreditAttribution: Tom.Camp commentedI'm having the same problem with a clean install of the latest release, 7.0. The error only occurs if I display terms for a custom content type in the teaser. It doesn't happen on the page display and it doesn't happen for teasers for blog posts. Change the display from link to plain text or vice versa and clearing cache has no effect. When it does throw the error it outputs a string of commas rather than a comma separated list of terms (see attached screenshot). I have also attached a screenshot of the error message.
As I said before this is a new install of latest D7 with the following modules installed:
CTools
Context
Devel
References
Colorbox
Site_map
Pathauto
Token
Views
Webform
Comment #32
yched CreditAttribution: yched commentedfrom #28, #29 (? not clear), #30 : "Hiding the Tags field on teasers causes these errors"
from #31 : "The error only occurs if I display terms for a custom content type in the teaser."
Contradiction, plus I still cannot reproduce this myself locally, either hiding or displaying the 'tags' field, either in teasers or full node page.
I'm afraid we do need detailed steps to reproduce from a fresh install, or a db dump from a site having the error (a sanitized dump, with passwords and emails removed). @inf was kind enough to provide a db dump in #24, unfortunately, it was generated before #986992: Insane etid / {field_config_entity_type} abstraction, and the dump no longer applies against current 7.x (apologies for not coming back at this soon enough).
In short : "me too" comments and screenshots are not helping. Detailed steps or a db dump, please :-)
Comment #33
jinglemansweep CreditAttribution: jinglemansweep commentedI'm using Drupal 7 Final, and it was all working well until I installed the "Synonyms" module. Since installing that, I got the error message stated above. Removing the "Synonyms" module doesn't fix the problem.
I've attached a sanitised MySQL dump (GZip'd) of my broken installation.
Comment #34
jinglemansweep CreditAttribution: jinglemansweep commentedExact error message that appears when viewing a specific taxonomy term. I have a "Devices" taxonomy and the error only appears when viewing one (of the total of three) taxonomy terms within the "Devices" taxonomy.
Devices:
- Advent Vega (Error Displayed)
- HTC Desire
- ZTE Blade
The only difference I can see is that the "Advent Vega" term has a node (of custom content type "FAQ" attached). The other two have other content types attached, so it could be something to do with the configuration of my "FAQ" content type.
Comment #35
jinglemansweep CreditAttribution: jinglemansweep commentedComment #36
yched CreditAttribution: yched commentedMany thanks for the dump, @jinglemansweep. I could finally nail this.
The problem happens on listing pages, listing nodes of different types, when a shared field has different display settings in each type (i.e field_taxo displayed in node type A, hidden in node type B).
Logic error in field_default_prepare_view() : The function operates on multiple entities, and thus on multiple instances. But the first iteration of the
foreach ($instances)
loop overwrites the incoming $display parameter, and messes it for the remaining entities.If this results in an instance being incorrectly seen as 'hidden', the 'prepare_view' hooks don't not run. Yet the formatter will run, because the instance is in fact not hidden, and field_default_view() is *not* broken ;-).
Taxonomy formatters expect the term object to have been loaded during the 'prepare view' step --> bang.
Thus, raising to major.
We'll need a test for this, but here's a patch fixing the bug for now.
Comment #37
yched CreditAttribution: yched commentedWith tests.
- test-only patch, should fail,
- test + fix patch, should pass
Comment #38
yched CreditAttribution: yched commentedWithout renaming other test methods so they stay out of the way :-p.
Comment #39
shaikhnizam CreditAttribution: shaikhnizam commented#36 worked fine for me, i applied this patch and the problem resolved...thanks guys.
Comment #40
webmatter CreditAttribution: webmatter commentedI have applied the last patch and it solved my problem. Thanks a lot!
Comment #41
jinglemansweep CreditAttribution: jinglemansweep commentedNo problems @yched. I suppose it was just good timing that I was redeveloping my site and didn't have too much sensitive data. Glad I stumbled across this bug report and that I could help. Even happier about the time it took you to research, investigate, fix and patch this issue.
Thank you very much for your assistance. Your speed and passion truly make the Drupal community what it is.
Now about to apply the patches so I can continue developing my site!
Comment #42
jinglemansweep CreditAttribution: jinglemansweep commentedJust applied the patch in #38 and it has solved the problem. Thanks again!
Comment #43
vhmauery CreditAttribution: vhmauery commented+1
I had a similar setup with a custom image node type and found that whenever I added an image tagged with this term, it would spew the same messages. I also found that if I added, say, an article tagged with the same term, then the messages would go away. But this patch fixes the errors on my installation. Please apply!
Comment #44
catchPatch looks great, test obviously works. RTBC.
Comment #45
webchickAwesome sleuthing! Thanks for the tests, too.
Committed to HEAD.
Comment #46
sashkernel CreditAttribution: sashkernel commentedI've got the same issue and I see that there is a fix for it. One thing is: I don't have experience applying patches
Do these patches integrate without any issues? I was advised to disable and backup all the modules before applying any patch, which I think makes sense.
But do I need to disable all modules that come with drupal core?
+Do i save patch above to the drupal root folder or somewhere down the tree?
+Which one of those 3 I should apply? (36, 37, or 38?)
Any advise will be helpful.
Thanks for getting solution for this problem so quickly.
Sash.
Comment #47
webchickComment #48
sam_squarewave CreditAttribution: sam_squarewave commented@sashkernel
I'm a pretty basic user as well, but maybe this will help...
When something is committed to head, you can go get the latest development release and install that. Otherwise you can apply the patch by hand by looking at the patch report - removing the lines with minuses and added the lines with plusses.
Installing the latest D7 worked to correct this for me. I imagine there are many bugfixes in there that would make it worth the gamble of going with a dev release.
Comment #49
sashkernel CreditAttribution: sashkernel commentedyep. got it to work by replacing field module from dev image.
thnx.
Comment #51
bryancasler CreditAttribution: bryancasler commentedsubscribe
Comment #52
Thomas_Zahreddin CreditAttribution: Thomas_Zahreddin commentedto #48: just a simple answer to a simple question would help too ;-)
Comment #53
kalilo CreditAttribution: kalilo commentedI've got the same issue, and Im using drupal 7.0.
Comment #54
kalilo CreditAttribution: kalilo commentedI get this error every time I choose to: Add existing field.
Comment #55
Kevin_VE CreditAttribution: Kevin_VE commentedSame problem here. subscribe
Comment #56
yched CreditAttribution: yched commentedNo need to subscribe, nothing will happen here anymore. The fix has been committed to the 7.x-dev branch, and will be part of the next core release (7.1). Meanwhile you can download a tarball of the current state of 7.x-dev on http://drupal.org/project/drupal.
Comment #57
x.flimon@gmail.com CreditAttribution: x.flimon@gmail.com commentedThat did the trick for me.. Thanks!
Comment #58
gargoyle CreditAttribution: gargoyle commentedI realize that this is "fixed" in 7.1, but is it not considered best practice to actually check for the existence of an array key before you use it?
Should the offending code block in taxonomy_field_formatter_view() not be wrapped in a isset() check?
Comment #59
yched CreditAttribution: yched commented@gargoyle : not if the key is supposed to be present, and its absence is a smoke sign of something else going wrong. Core coding conventions include not adding unneeded preventive cruft checks, and not hiding errors under the carpet.
Comment #60
DamienMcKenna@yched: One of the problems, though is not being able to debug the problem without (temporarily) hacking core, so would it be so bad to add in a watchdog statement for invalid data just to record the invalid nid?
Comment #61
Snicers CreditAttribution: Snicers commentedI am still having this issue.
Notice: Undefined variable: element in media_field_formatter_view() (line 162 of /var/www/Drupal/sites/all/modules/media/includes/media.fields.inc).
Comment #62
yched CreditAttribution: yched commented@Snicers : that is a different issue, which should be reported in the Media module issue queue (if it hasn't been already)
Comment #63
Michael-IDA CreditAttribution: Michael-IDA commentedStill an issue in D7.8. Standard install, no code modifications of any kind.
Steps for reproduction:
- Taxonomy >> Add vocabulary
"MY-Page Keywords"
- Create custom Content Type, "MY-Page"
- "Add new field"
Label: Keywords
Name: field_my_page_keywords
Field: Term reference
Widget: Autocomplete term widget (tagging)
- Edit "Keywords"
Number of values: Unlimited
Vocabulary: "MY-Page Keywords"
- Hide "Keywords" field
- Add a meta tag default (/admin/config/search/metatags)
Node: MY-Page
Inherits meta tags from: Global, Node
Keywords: [node:field_my_page_keywords]
- Add Content >> MY-Page
- Add three terms to "Keywords"
Error occurs.
Error and basic site info below. Need more?, just ask.
Best,
Sam
====
Comment #64
catchThis was committed with automated tests several months ago, so if you're seeing the same error or a similar one, it will be a different root cause. Please open a new issue.
Comment #65
Michael-IDA CreditAttribution: Michael-IDA commentedCatch,
Quote: "I realize that this is "fixed" in 7.1, but is it"
It hasn't been completely fixed. It still crops up in D7.8, as I presented, with what should be enough information to go figure out the last tidbit of this bug.
Please play nice, it's not what the 'root' cause is, it's that this isn't a "new" issue.
Sam
Comment #66
StevenPatzComment #67
Michael-IDA CreditAttribution: Michael-IDA commentedThis isn't fixed, but I'll play your reindeer games, new bug report at: http://drupal.org/node/1323740
Comment #68
johnlclark CreditAttribution: johnlclark commentedI found this in 7.9 when I had hidden the tags in default view but not in the teaser. I just edited the content type: manage display and hide tags in both views. Hope this helps.
Comment #69
dynamicdan CreditAttribution: dynamicdan commentedThis also happens to us on 7.8 when clicking Preview on certain content types. I believe we are also hiding many (taxonomy) fields for our default view....
Double posting here and in new issue (http://drupal.org/node/1323740) because I am simply confused as to where to post.
Comment #70
catchThe other issue was the right one, I've bumped priority on that one though.
Comment #71
Dharmendra.s CreditAttribution: Dharmendra.s commentedThanks , its really helpful...
My proublem is solved i have replaced the Taxanomy.module
Line 1436 in drupal7
Original $term = $item['taxonomy_term'];
Replaced $term = taxonomy_term_load($item['tid']);
Happy Drupling....
Comment #72
Anonymous (not verified) CreditAttribution: Anonymous commentedConfirming that this fixes the error.
It's a shame to have to hack core but at least it works
Comment #73
nextmove CreditAttribution: nextmove commentedIssue still exists in 7.12. I used hack see post #71 at line 1443 - that fixed the issue for me too. Drupal is new to me so I was very surprised to bump into a bug like this one. As soon as i assigned a product to a catalog i got the error when accessing page with catalog.
Comment #74
xjmPlease follow up in this issue: #1075998: Notice: Undefined index: taxonomy_term after re-using term reference fields. We need steps to reproduce the problem in that issue. It may be caused by a contributed module.
Comment #75
mgsolipa CreditAttribution: mgsolipa commentedI had the same problem and this solution works fine for me too. Thanks for sharing.
Comment #76
maxchock CreditAttribution: maxchock commentedthanks, that work for me too. TQ.
Comment #77
just_like_good_vibesthanks it's worked for me too
Comment #78
klopsen CreditAttribution: klopsen commentedIn my case applying #71 sollution caused another bug:
Fatal error: Unsupported operand types in /modules/node/node.module on line 1361
Any ideas?
Comment #79
sachbearbeiter CreditAttribution: sachbearbeiter commentedafter #71 i now get EntityMalformedException: Missing bundle property on entity of type node. in entity_extract_ids() (line 7501 of /includes/common.inc).
Comment #80
stanoman CreditAttribution: stanoman commented#71 fixed this for me too. My trouble seems to have started when I somehow built duplicate taxonomy names called "catalog" because I couldn't figure out how to get ubercart to list products. The taxonomy implementation into Ubercart seems fairly new, so I'm thinking something there may have caused my particular issue.
Comment #81
dynamicdan CreditAttribution: dynamicdan commentedRe-opening... #1075998 is not related in my opinion. Comment #71 has not made it to the core so the bug has jumped into the latest 7.12 version!
I used 7 'Term Reference' fields. There may be a connection to field_regions or field_images being loaded twice as per previous comments.
NOTE that I only get the error when clicking the 'preview' button. Saving works as expected.
It seems obvious to me that the term is simply not being loaded into $item['taxonomy_term'].
Comment #82
xjm@dynamicdan: Please open a new issue with explicit steps to reproduce the error you're getting. So far everything points to this being caused by bad code in contributed modules.
Comment #83
sansaturno CreditAttribution: sansaturno commented#71 worked well for me too, it was something related with Ubercart Catalog, that is conected with taxonomy, thanks a lot.
Comment #84
stefmex CreditAttribution: stefmex commentedI have this problem with ubercart products (www.riberbike.es)
but only when terms has more than one product :) on 1rst and 2nd block (list) taxonomy
ej: "Peugeot" have troubles (many products for this make),
but "polisport" no trouble >> only one term in this make.
#71 do not work for me.
>>> 3rd block taxonomy: no problem even if more than one "product" included in this term
because (???? mmm) 3rd block have a class defined in shop (ubercart > bike accessories )
1rst & 2nd block haven't class defined in ubercart (default product, bikes) It could be the reason ????
thanks for help.
------ edit
No troubles in terms like "Origin-8" in the 1rst block because many products but alls from accessories, i.e: from "defined class" in ubercart shop.
So only problem with terms linked with "ubercart: default product class", not with terms "from" ubercart defined class. !!! I hope it can help for reproducing this issue. thanks
Comment #85
catchPlease open a new issue against ubercart and link to it from this one.
Comment #86
rickmanelius CreditAttribution: rickmanelius commentedUgh. I had to resort to #71...
The issue for me is simple to reproduce. Any ubercart product node with attributes results in an $item array that lacks the taxonomy_term key and therefore it borks.
For performance reasons, I tried to not load every single time, so here was my hack.
Obviously, use with care and realize the upcoming 7.13 will break this.
Comment #87
stefmex CreditAttribution: stefmex commentedSame for me, see: http://drupal.org/node/1529276#comment-5874660
thank you,
Comment #88
Lars Bo Jensen CreditAttribution: Lars Bo Jensen commentedI don't know if helps anybody, but I had the error when displaying taxonomy terms on current content with a dynamic field in Display Suite, using a view, passing on nid as an argument to it, but NOT selecting 'Load terms' under Field settings. Load terms checked -> works again. Drupal 7.14, Views 7.x-3.3, Display Suite 7.x-1.5.
Comment #89
rickmanelius CreditAttribution: rickmanelius commentedThis bit me again, so I'm adding a patch so I can track.
Comment #90
Michele Wickham CreditAttribution: Michele Wickham commentedThis issue cropped up for me today when using preview. This patch fixes the problem. Any chance we could see this added to a core update?
Comment #91
grossmont@gmail.com CreditAttribution: grossmont@gmail.com commentedThis patch also fixed my issue. And just ilke mishwick, above, it was occurring during preview.
Comment #92
dynamicdan CreditAttribution: dynamicdan commentedSet status to active... I think it's important to test patches.
Comment #93
webchickMoving to needs review, since there's a patch. However, a notice error cannot possibly be a "major" bug.
Comment #94
nagba CreditAttribution: nagba commentedThe very least fix up the coding style a bit please. There should be a space between the if and the opening parenthese. Similarly after 'else'.
Comment #95
grossmont@gmail.com CreditAttribution: grossmont@gmail.com commentedWhen the error occurred, I didn't get a notice. It actually failed with the WSOD.
Comment #96
rickmanelius CreditAttribution: rickmanelius commentedFixing the style issues noted in #94. Otherwise its the same patch as #89.
Comment #97
nagba CreditAttribution: nagba commentedOne thing that comes to mind, if core actually is setting up the proper data structure, then isnt it rather ubercart module that needs fixing to populate the data structure to the expected format ? The original module could load multiple terms at once and push the necessary data into place in one go, while in this patch on a larger data set code would load the terms one by one.
Comment #98
cangeceiro CreditAttribution: cangeceiro commentedalso had this issue, and the patch resolved it for me.
Comment #99
nagba CreditAttribution: nagba commentedjust because the patch fixes something it does not mean that it is the right approach, fix the offending module, not core.
Comment #100
nagba CreditAttribution: nagba commentedwe should open a new issue on whichever module is causing trouble instead of having core babysit broken code
Comment #101
vlajkop CreditAttribution: vlajkop commentedHere is some more description about this problem that may be helpful in solving issue including and instruction how to reproduce same issue.
To reproduce this issue:
1. Create couple of taxonomy terms (5 for example).
2. Assign taxonomy filed to content type and attach node to belong to those taxonomy terms.
3. Delete some (two) terms from taxonomy.
4. Visit node and error will be displayed.
This is exact error:
Notice: Undefined index: 67 in taxonomy_formatter_field_formatter_view() (line 147 of /var/www/html/sites/all/modules/taxonomy_formatter/taxonomy_formatter.module).
EntityMalformedException: Missing bundle property on entity of type taxonomy_term. in entity_extract_ids() (line 7562 of /var/www/html/includes/common.inc).
What is happening is that field is still holding relation to deleted taxonomy term id (in this case 67).
I was unable to identify in database table where this is a case. If someone has found solution please post it.
Taxonomy formatter is extension - a module, but in this case when hook taxonomy_formatter_field_formatter_view ( hook field_formatter_view()) is called $items is holding deleted taxonomy terms IDs regardless if cache is cleaned & server restarted.
Comment #102
SpikeX CreditAttribution: SpikeX commentedI am having the same issue. #101 seems to explain it well.
This is preventing me from viewing content on my site. Could someone develop a patch for this?
Comment #103
osysltd CreditAttribution: osysltd commentedAcknowledge bug.
Any ideas?
Comment #104
BeaPower CreditAttribution: BeaPower commentedHaving this issue after deleting terms, any fix?
Comment #105
xjmMoving to the correct queue per #101.
Comment #106
rooby CreditAttribution: rooby commentedI'm seeing the error and don't have the taxonomy_formatter module installed (and never did have).
I am seeing it when previewing a node and $items being passed into taxonomy_field_formatter_view() are:
But the code is looking for:
which doesn't exist.
Investigating further.
Comment #107
rooby CreditAttribution: rooby commentedSorry, my problem turns out to be this one - #1289336: Calling node_view for the same node with multiple view modes on the same page during node preview does not correctly attach fields
Comment #108
danlinn CreditAttribution: danlinn commentedDang! All this hoopla due to this little module. D'oh!.
Turns out that the nodes hang on to all term ids, deleted or not. I've added a simple check for this. New version soon. Sorry everyone!
Comment #109
danlinn CreditAttribution: danlinn commentedOk, 7.x-1.4 has been released with the fix in it. Thanks for the report.
Comment #110
sustainablesolutionsnz CreditAttribution: sustainablesolutionsnz commentedI just had this issue after completely rebuilding my website and then restoring nodes. I am no longer running uc catalog module but using views to add filters to catalog pages.
As someone pointed out it could be a result of running more than one taxonomy term called catalog, but that is no longer the case.
The error only occurs when I add an attribute price to a product. Fix 71 has worked, but of course next update it will happen again.
Comment #111
dragonbite CreditAttribution: dragonbite commentedUpgrading my website to Drupal 7.32, I needed to apply this patch to get rid of the errors.
The errors show up when attempting to Preview content. The description of what is going on in #36 makes sense for my situation.
There was mention elsewhere (cannot find it right now) about making all Taxonomy fields visible for all Content types (Default, teaser and others) and then set them again. I tried that before applying the patch and it did not work (hence, why I applied the patch).
Comment #112
vmsiam CreditAttribution: vmsiam commentedUpgrading to drupal 7.34 I get this error while trying to preview content.
Tried to apply the patch 96 but no success.
Any ideas?
Comment #113
giupenni CreditAttribution: giupenni commentedI have the same problem witdh D 7.34.
As usual there is always a problem.
Comment #114
giupenni CreditAttribution: giupenni commentedThis patch solve my problem:
https://www.drupal.org/node/2128265#comment-8636171
Comment #115
giupenni CreditAttribution: giupenni commentedNever mind, unfortunately the problem is still present.
Damned
Comment #116
giupenni CreditAttribution: giupenni commentedWell, seems to work but with some issue:
https://www.drupal.org/node/2128265#comment-9398765
Comment #117
bobburns CreditAttribution: bobburns commentedThere is another patch for this same issue at https://www.drupal.org/project/drupal/issues/2128265#comment-12976770 which appears to work
I am using this one right now
But can someone look into this since the issue is still present in 7.64, can someone commit one or the other to core so this does not need to patched over and over again each Drupal core is updated ??