CMS Compatibility List

Green indicates full compatibility.
Still subject to some issues with 3rd party plugins, modules, and frameworks, however.

Yellow indicates moderate compatibility.
There is a good chance that there will be issues in some form or another. Issues include: limited access to site header code, not being able to create a working template, or not being able to hide the template in the navigation. If templates cannot be created, then iframes are the last resort, and you will then be unable to include the scrolling modules.

Red indicates severely limited or no compatibility.
Issues include: not being able to point to external links, not being able to create a working template, or cross domain issues. Iframes may not even be available as a backup as some servers don’t allow iframe code to be dropped in. If templates cannot be created, then iframes are the last resort, and you will then be unable to include the scrolling modules.


WordPress

Supports Template Integration Method

This is the most commonly integrated CMS. Although various templates and plugins can pose problems, a high percentage of the issues that we run into can be resolved.

Joomla

Supports Template Integration Method

Another common CMS. Although not as user friendly as WordPress, creating a template and pointing menu links are easy. Problems can arise when using old versions of Joomla, namely v1.5. We HIGHLY recommend upgrading to the latest version of Joomla before integrating with our modules.

Drupal

Supports Template Integration Method

One of the ‘Big Three’ CMS, Drupal is easy to integrate. Here we also recommend upgrading to the latest version to avoid common (usually menu related) compatibility issues.

Concrete5

Supports Template Integration Method

We have little data on specific issues for this CMS, but like the others, keeping it updated to the latest version and watching for plugin-related issues will be important.

LiveEdit

Supports Template Integration Method

Tried and tested, as one of GrowthZone’s CMS of choice, LiveEdit integrates well with our software.

WordPress.com

Supports Template Integration Method

A wordpress site located on WordPress.com has a few limitations. First, we’re unable to make changes to the theme files of the site, which prevents us from adding scrolling module code to some locations and prevents us entirely from dropping in a mobile detections script. Aside from that, a WordPress.com site can still be successfully integrated.

ModX

Supports Template Integration Method

The Template page used for integration needs to have its Base Tag URL removed in the source code. If not removed, the integration will not work properly.

Squarespace

Some versions support Template Integration Method (see below)

There are two types of Squarespace sites that are available to integrate with our modules: the older flash based version and the newer HTML5 version.

  1. The older Flash based system can only be integrated through the use of iframes. We recommend that users of the flash version update to the HTML5 version of the Squarespace software, as flash is not supported by the majority of mobile phones.
  2. The HTML5 version populates the content of pages via JSON/Ajax calls, and thus our server has difficulties caching the content tag that is required for the placement of our content. With the HTML5 version of the Squarespace software, we can work around the main challenges of the software through the use of jQuery.  Note that in our most recent tests, we have found current Squarespace themes to work with our template integration method.
    * note that a known issue is that Squarespace does not support CORS which is required for use of custom hosted fonts – this can be bypassed by selecting web safe fonts and applying them via the Design > Style Editor > Typography section.

DotNetNuke

Some themes support Template Integration Method

Although it is possible to use the template method to integrate with DotNetNuke, we have run into cross-domain server issues that prevent some of the javascript from running properly on the page, causing issues such as navigation dropdowns not functioning, scrolling modules (both javascript-based and iframe-based) not working properly, and sidebar content disappearing altogether. It seems that these issues are not consistent for each DotNetNuke site, so it is probable that the source of the issues lies in the theme files DNN uses.

Weebly

Supports Template Integration Method on modern web browsers

There is a known bug with the way that Weebly loads its main navigation and dropdown items – although we have a javascript fix available for this, there is no remedy for IE7 and IE8. (the main nav items are clickable, but the dropdowns do not function). The pages load correctly in the other major browsers, including Chrome, Safari, Firefox, and IE9+.

Yahoo Sitebuilder

Available Integration Methods: Iframes or Static HTML Template*

Cannot point main navigation links to our modules (or any external link for that matter).  MUST use iframes, and no scrolling modules allowed.

Wix

Available Integration Methods: Iframes or Static HTML Template*

Cannot create a working template page, due to the Ajax nature of the Wix pages.  MUST use iframes, and no scrolling modules allowed.

MOTO CMS

Available Integration Methods: Iframes or Static HTML Template*

Cannot create a working template page, due to the Ajax nature of the MOTO pages.  MUST use iframes, and no scrolling modules allowed.

sitebuilder.com

Available Integration Methods: Iframes or Static HTML Template*

Cannot create a working template page, due to the Ajax nature of the siteuilder.com pages.  MUST use iframes, and no scrolling modules allowed.

*Using a static HTML template is an option for Yahoo Sitebuilder, Wix, MOTO CMS & sitebuilder.com but will require that someone with web design abilities build, host, and maintain that static template separately from the primary website CMS.  Meaning that if a page is added to the navigation via the CMS, the static HTML template will need to be manually updated so that the navigation change is reflected on the ChamberMaster / MemberZone module pages as well (note that this would apply to any other type of change to the site as well e.g. header, footer, sidebar, etc… not just navigation changes).

GoDaddy Sitebuilder

Updated to use Ajax. Available Integration Methods: Iframes

Recently, GoDaddy Sitebuilder updated their software to use Ajax code. Meaning our servers can’t extract the styling of any template pages. Best case now is to not use GoDaddy Sitebuilder with GrowthZone or ChamberMaster/MemberZone integrations. Last resort is to use iframes.