Share in the brilliance with our Developer APIWe welcome all RapidWeaver designers and developers to incorporate support for RapidSearch and RapidSearch Pro into your themes, stacks, snippets and templates. This can include the bare-minimum (such as marking your addons as being compatible with RapidSearch stacks), through to support for search boxes built directly into themes or stacks.
If you are a registered RapidWeaver developer, we will be happy to send you a complimentary RapidSearch and RapidSearch Pro license; you can use for testing and building demo sites with.
RapidSearch and RapidSearch Pro were the very first website searching addons to become available for RapidWeaver. They remain the most popular method for adding search capabilities to websites. Website searching is a function a lot of RapidWeaver users want. If you can demonstrate that your RapidWeaver addons or templates are optimized for RapidSearch and RapidSearch Pro; then there's a good chance you might see an increase in sales.
As of summer 2016, we've shutdown development of the RapidSearch and RapidSearch Pro plugins. We now focus solely on the two stack elements. The stack elements are far more popular than the standalone plugins ever were. We've been able to grow the feature set of the stacks. The stacks are proving easier and more cost-effective for us to maintain and support. Pricing of the stacks remains competitive and we've revised the pricing structure to promote more flexible use of the stacks in more projects (the 1-license-per-domain rule has been abolished).
Integrate RapidSearch and RapidSearch Pro into your webpages, themes and stacksIt is very easy to add an HTML search form to your addon, that will integrate with RapidSearch or RapidSearch Pro. The form should submit a
getrequest to the public-facing RapidSearch page URL with a
queryparameter whose value is a URL encoded string of search keywords. The following markup is a good example.
<form action="http://example.com/path/to/rapidsearch/" method="get">
<input type="text" name="query" value="" placeholder="Enter search terms..." />
<input type="submit" value="Search" />
Quite a number of frontend frameworks (like Twitter Bootstrap, Zurb Foundation and UIKit) include special class selector names you can add to the form elements; to instantly apply attractive styling (like rounded corners, active outlines and colored buttons). Alternatively you can write your own CSS code to style the form.
CSS SelectorsRapidSearch provides default CSS styles so that the public-facing RapidSearch Pro search form looks great out of the box. However, it is also possible to disable the default CSS styles so they may be overridden with your own CSS. Use the following CSS selectors to style the RapidSearch Pro search form with your own styles:
The container around the search form and search results
The search form
The search form text input
The search form submit button
The search form clear hyperlink
The ordered list element that contains search results
A search result
A search result title
A search result excerpt
A search result URL
JSON Search APIRapidSearch Pro provides a JSON search API so you can implement custom search results into your RapidWeaver website or even into an external website. Before you can use the API, you must first know the full absolute URL of your public-facing RapidSearch Pro page. The API endpoint URL is the same URL as your public-facing RapidSearch Pro page with a "/files/index.php/api/search" suffix.
For example, if my RapidSearch Pro form is available at "http://www.domain.com/search/", I can find the API endpoint at "http://www.domain.com/search/files/index.php/api/search". To request JSON search results, send a GET request for:
The API request requires one GET parameter:
URL encoded string of keywords. This may contain boolean logic operators.
"title":"RapidWeaver Themes and Plugins - NimbleHost.com",
"description":"Shop for professional RapidWeaver themes...",
Each search result object contains the following keys:
The database-assigned page unique identifier.
The page title as specified in the title tag of the document head.
The page description as specified in the description meta tag. This will be empty if no description meta tag is present for that page.
The page URL
The API may return a 400 Bad Request status if your request is malformed, a 405 Method Not Allowed status if your request is not a GET request, or a 500 Error status if the API malfunctioned on the server. If all goes well, the API will return a 200 OK status. If you receive a 400, 405, or 500 status code, the HTTP response body will contain information about the error.