Closed (works as designed)
Project:
Drupal core
Version:
7.22
Component:
node system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Apr 2013 at 09:06 UTC
Updated:
21 Mar 2016 at 16:31 UTC
Jump to comment: Most recent
Comments
Comment #1
giorgoskit turns out that solution presented did not help
it was just a coincedence that the message dissapeared
Comment #2
giorgoskdoing a google search reveals that this might be a commerce kickstart related problem
for example do a search "Notice: Undefined index: summary in _text_sanitize() (line 319"
or I have feeling it might be related to an omega subtheme issue
Comment #3
giorgoskrelated issues
#1847942: The [body-summary] token does not output anything
#1295524: [node:summary] does not work in default content meta tag when summary left empty
http://drupal.org/project/fixcore
I used fixcore but it did not help because the $item["summary"] is not empty but UNSET
Comment #4
bclinton commentedI am also using commerce and had this problem.
In my case it was from the metatag module. This module defaults to putting [node:summary] in the meta tags Description field, and if your content or content type does not have a summary field, you get this error. To fix it, remove [node:summary] from the description field, or put a real description in that field.
If you aren't using the metatag module, is there some other place you are using the token [node:summary] on content that does not have a summary field?
Comment #5
ailgm commentedGreat. I believe #4 solved it for me. Thank you.
Comment #6
marktheshark commentedAlso experiencing this on CK 2.6, probably due to the metatag module.
Shouldn't this issue be reassigned to that module?
Comment #7
maxchock commentedHi,
I'm suffering from the same problem, but as #4 mention, how we can remove [node:summary] from the description field ?
Thanks.
Comment #8
As If commentedThis error message can be caused in numerous ways.
In my case it was being triggered within a block view. I had a text field that I deleted and replaced with an integer field of the same name. However, I also had a View that did not know I had done this :-) So the View was still trying to process it like a text field.
The problem was solved by opening that View and re-saving the field in question with proper values.
Basically, if you get this error message, look at any field or token that you (or a module) has recently changed. Then examine every place where that field or token appears (for instance, inside a View), and resave the field/token with your selected values.
Comment #9
darkpoision commentedI also had the same problem... but in my case I was rearrenging the content type structure/layout using panelizer. So when I had tried to use email field in my content type it had show me the error.. but but going into the structure -> content type -> mycontent -> (here instead of changing the manage display setting) panelizer tab -> full page override -> content. Here I had changed the setting for my email field. So the main problem was if we change the manage display setting which was overrided by panelizer so it throws the null value....
Comment #10
mayur.pimple commentedI had also same issue, I have disable meta tags modules. Now error is resolve.
Great. I believe #4 solved it for me. Thank you.
Comment #11
maxchock commentedyou are avoiding the error, not solving. Meta Tags are important for SEO, unless SEO is not important to you..
Comment #12
JAScarb commentedThank you #4, that sorted it for me too
Comment #13
jhodgdonIt looks like this is not a Drupal Core issue.