Hi, if you click on get started on that link it takes you to a page which details how it will be shut down. It gives the following message:
That module was actually written by @stefen who is a regular on these boards. Maybe he could chime in with some modification help.
I actually just created a custom search for a resource page that checked the searched term against all of the blogs components (title, content, image, custom module content) and returned any matches on the listing page. This would work for a site wide search except that I cannot seam to find a token that contains the published pages.
— Jonathan Sumner
No in my case I had the blogs contents loop to search through.
I created a variable for the query:
{% set query = request.query_dict.q|lower %}created a search bar to pass a query to the url:
<form id="tagForm">
<div class="page_center large">
<input id="keyword" type="search" value="{% if query is defined %} {{ query }} {% endif %} ">
<button type="submit"></button>
</div>
</form>
<script>
$(document).ready(function() {
$('#tagForm').submit( function() {
goUrl = 'SiteURL/resources' + '?q=' + $('#keyword').val().toLowerCase();
window.location = goUrl;
return false; // Prevent the default form behaviour
});
});
</script>and a custom for contents loop if a query is present in the url:
{% if query is defined %}
{% for content in contents %}
{% set title = content.widgets.resource_title.body.value|lower %}
{% set type = content.widgets.resource_content_type.body.value|lower %}
{% set summary = content.widgets.resource_content_type.body.value|lower %}
{% set topic = in content.topic_list|map('name')|lower %}
{%if query in title or query in type or query in summary or query in topic %}
<div class="resource_item {{ content.widgets.resource_content_type.body.value|lower }}">
<a class="resource_featured_image" href="{{ content.widgets.resource_link.body.value }}" style="background: url({{ content.widgets.resource_image.body.src }});"></a>
<h2><a href="{{ content.widgets.resource_link.body.value }}">{{ content.widgets.resource_title.body.value }}</a></h2>
<div class="sum_wrap">
{{ content.widgets.resource_summary.body.value }}
</div>
<a class="resource_read_more" href="{{ content.widgets.resource_link.body.value }}">{{ content.widgets.resource_button_text.body.value }}</a>
</div>
{% endif %}
{% endfor %}
{% endif %}This was based off of a request to have the clients resource page searchable like Hubspots search page. It works pretty much the same.
This would work in your case to only you would need to redirect to a different page with the query and use an array like contents that gives you access to all of the pages on your site. I can't seam to find anything that allows this. without having access to all of the pages and their content to loop through this won't work.
— Jonathan Sumner
I placed the query variable and the search bar w/ javascript in a custom HubL module outside of the listing and post template code, in the main template. This is because they share a search bar so I needed it for both instead of one or the other.
It doesn't matter where you place your query variable as long as you have it above the code that references it.
You are correct about the code that you placed in your listing template.
— Jonathan Sumner
I would imagine that the "is string_containing" part is the issue. I might be wrong but I am pretty sure that the topics are delivered as a dict containing the slug and the topic name. I haven't had this issue before. I wrote a blog post about this method: http://www.khaoticdigital.com/blog/simple-hubspot-blog-search-function
% if query in title or query in post or query in topics %}
hasn't let me down yet, though I can't honestly say I remember whether or not I actually tested topics. I am pretty sure I did. The same search is implemented on my blog there.
— Jonathan Sumner
