Release 0.1.5

Operation Drama Llama - Released September 08, 2017

Picture by Alexandre Buisse (Nattfodd) (Own work ( [GFDL (], via Wikimedia Commons

In this release, we completed three major features: Site search, SSL, and a new HTML editor. Along with these major features, we also completed a large number of "minor" features, improvements, and bug fixes.

Site Search:

We implemented two different site search mechanisms for live sites and for the management interface. The two are similar with two notable exceptions:

How does search work?

All "searchable" content on your site is indexed by our internal search engine. In the management interface this includes almost all objects. In the live interface this only includes pages and objects that you can create pages for (which excludes objects such as menu items). Because the objects are indexed and not the generated markup, the search index does NOT contain any content from the template - which typically includes the header, footer, sidebars, and other shared modular content. Additionally, all HTML, text, and textarea custom fields are indexed along with the pages (or entities) they belong to. Note that other custom fields types are NOT indexed and will NOT be used by our internal search engine.

For further details about what exactly is indexed, please contact Marketpath directly.

How do I use Site Search?

To take advantage of site search in the management interface, click on the magnifying glass at the top of the page and start typing your search term in the search box that appears on the screen.

To take advantage of site search on your live site, your template developer will have to create a search page that includes the new {% Search %} tag. Note that currently there is no way to limit your live search to specific page types (eg: only search blog posts, etc...) although that feature is planned for the future.


All domains can now be accessed via "https://" URLs, although this is configurable for each domain. This feature has been in development for a long time due to it's technical and detail-intensive nature. The short explanation for this is that all domains that are accessible via "https" have to have valid and up-to-date SSL certificates, which require a significant amount of additional infrastructure and code to automatically generate and maintain.

As an alternative to automatically-generated SSL certificates, you may choose not to have an SSL certificate at all or to manage your own SSL certificate (eg: for Domain Validation [DV] or Extended Validation [EV] Certificates).

Although the infrastructure, processes, and code have all been completed for SSL certificates and "https://" URLs, it will still take a number of weeks to roll it out for all new and existing domains in the CMS.

Is this really a big deal?

YES! This is a big deal.

  1. There is certain content that should ONLY be accessible via https, such as login and contact forms or certain javascript content. Furthermore, if you are referencing content on other sites that are served over https, users' browsers may refuse to load the content on pages that are not loaded via https.
  2. SSL provides an extra layer of security for your website to protect against "man-in-the-middle" attacks. This type of attack has nothing to do with your website hosting or coding and may be difficult or impossible to prevent using other methods.
  3. Google ranks websites with SSL certificates higher than websites without them. Soon, Google will begin displaying warnings on search results for pages that are not served via https.
  4. Dependability. Users are getting more savvy when it comes to browsing the web, and many users take websites more seriously when they are served via https. To them, the lock icon next to the URL indicates security, dependability, and professionalism.
  5. There are no downsides. There is no good reason why you would not want a valid SSL certificate on your website. The main reasons that many websites do not have SSL certificates are cost and effort - both of which are handled for you by Marketpath. If you still don't want a SSL certificate, you can simply turn it off; or if you want a more advanced SSL certificate, we make that possible, too. This is a no-brainer.

If you have any further questions about SSL Certificates and https, send an email to and we will be happy to assist you.

HTML Editor

We have fully migrated our HTML editor to Froala, a "Beautiful javascript web editor ... users will simply fall in love with its clean design." We made the decision to switch editors as a team after a significant amount of research and deliberation and for a variety of reasons. We believe that marketers will appreciate the clean and effective interface, while developers will appreciate the clean and simple markup.

We were able to fully integrate the new editor with the CMS for uploading and editing images as well as linking to pages, documents, etc...

We were also able to integrate the new editor with CMS stylesheets so that the editor can easily be made to look like the live site so that site-specific classes can easily be added using editor icons. In order to associate a stylesheet with the editor, go to Site => Site Settings => Templating, select the stylesheet you wish to use for the "Editor Stylesheet", and save. Please note that before the stylesheet can be used by the editor, it must be published. You may also have to refresh the page for any changes to be visible in your browser.

We will add documentation in the near future for how to get the most out of the new HTML editor.

"Minor" Updates