Needs work
Project:
Content Taxonomy
Version:
6.x-1.0-rc2
Component:
Documentation
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Mar 2011 at 19:03 UTC
Updated:
8 Aug 2014 at 12:17 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
joelstein commentedI found a couple more.
Comment #2
vectoroc commentedthanks
Comment #3
fgmI was just going to suggest the exact same patch: good for me.
Same problem still exists in 6.x-2.x, by the way.
Comment #4
fgmTagging for 5.3.
Comment #5
fgmExcept of course it needs to be rerolled in git format against an actual version, so someone else needs to check.
Comment #6
vectoroc commentedhere is a patch for another notices
Comment #7
vectoroc commentedand another set of fixes
Comment #8
fgmif (isset($entry['value']) && $entry['value'])can be replaced byif (!empty($entry['value'])which is slightly shorter.Comment #9
gateway69 commentedany updates to this? we are seeing this still
Comment #10
hchonovCouldn't apply content_taxonomy_notices2.patch because of the path prefixes, which have been exchanged with a/ and b/ in content_taxonomy_notices2.1.patch