Closed (fixed)
Project:
Featured Content
Version:
7.x-1.5
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
22 Apr 2012 at 21:06 UTC
Updated:
29 Jul 2025 at 23:50 UTC
Jump to comment: Most recent
Comments
Comment #1
kristen polSorry for the delay... the system hasn't been notifying me consistently about these issues for some reason.
I will test this right now.
Comment #2
kristen polI verified the behavior. For now, you might want to try the Filtered Content for "Type" and then use the "Title Keywords" filter as that does give results as far as I can tell.
I'm not sure when I will have time to look into why this isn't working. Patches and co-maintainers are welcome!
Comment #3
kristen polComment #4
kristen polThe workaround is the best approach for this right now.
Comment #5
kristen polNote that the code has been updated to using view modes. Please test the dev version using the Search Results view mode.
Comment #6
kristen polI have figured out this issue. It's rather strange. When the nodes are loaded during the search, they have less information and that is cached. So when the node is loaded later to be rendered, it is missing some information. I have a hack to deal with this (it resets the node when loading for search results). But, this is an interesting issue as it might be revealing an underlying core problem.
Comment #7
kristen polI just checked in the fix to 7.x-1.x-dev.
Comment #8
kristen polComment #10
kristen polunassigning old issues