Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When adding "new custom content" to a Panel, that content does not get indexed by the search engine. E.g., if I add new custom content to a panel such as "The snozzberries taste like snozzberries", then search on "snozzberries", I get no search results found.
I have tried re-indexing the site as well.
This might be a feature request and not a bug (not sure if this is intended behavior or not).
Thanks!
Comments
Comment #1
sdboyer CreditAttribution: sdboyer commentedYep, it's a feature request. The built-in drupal search system searches node content; it doesn't know to search panels content. And it shouldn't; panels custom content panes are _really_ not supposed to be anything more than a convenient, quick-fix/hack tool. By and large, if you're putting information that needs to be accessible via searches into panels custom content types anyway, then it probably points to some weaknesses in your data model. Substantive data should almost never be DEFINED in Panels - Panels should be using one of its numerous mechanisms for pulling data in from elsewhere to find it.
Comment #2
John Bickar CreditAttribution: John Bickar commentedThanks for the clarification and the quick response. I suspected this was the case, and I agree that it should work this way.
Thank you!
Comment #3
dmitrig01 CreditAttribution: dmitrig01 commentedTo put what sdboyer said in easier terms, if you make every "custom content" into a node, and add the node to the panel, the search results will turn p that node. Then you can use a module like Path Redirect to redirect those nodes to the panel.
Comment #4
sdboyer CreditAttribution: sdboyer commentedFirst half, yes, thanks for distilling that down dmitrig01.
Second half, not quite so much - Panels Pages provide a plethora of options for overriding and sucking in node content (among other things) using panels-internal mechanisms. Though doing Path Redirect may well work, I can't think of a compelling reason to add another layer of complexity to Panels, especially when that layer is trying to do something that Panels is already quite good at doing itself.