Resources
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.
LightCMS
Supports Template Integration Method
Must be most updated version. Template integration works well with our software.
Mura CMS
Supports Template Integration Method
Little data on this CMS but have tested with our software. Template integration works but may seem CORS issues (fonts not working on module page) but can be resolved. Latest version of he CMS must be used.
SilverStripe CMS
Supports Template Integration Method
Latest version of he CMS must be used. Template integration works well but may have some font sizes appear larger on the module pages. GrowthZone can add CSS code to couter the font size to make it the same as on the template page.
Craft CMS
Supports Template Integration Method
Template integration works well. Testing shows there to be CORS issues but can be easily resolved adding code to htaccess file. This file is usually available with FTP or cPanel access.
Webflow
Supports Template Integration Method
Limited testing early data shows the template integration works well.
GoDaddy Sitebuilder
Supports Template Integration Method
Recently, GoDaddy Sitebuilder updated their software to use code that is supported by our integration.
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.
- 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.
- 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.
- ***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. If able, users can upload the fonts to a server that does support CORS and reference them in their Squarespace template.
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+.
Supports Template Integration Method on modern web browsers.
Wild Apricot
Supports Template Integration Method on modern web browsers. More testing is being done currently.
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.
YourMembership
Available Integration Methods: Iframes or Static HTML Template*
Similar to a Wix CMS, we cannot create a working template page, due to the Ajax nature of the 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).
Homestead Sitebuilder
Uses Ajax. Available Integration Methods: Iframes
Similar to the other Sitebuilders, their software uses Ajax code. Servers can’t extract the styling for our module pages. Resort to Iframes.
Adobe Dreamweaver CMS
Uses Ajax code/libraries. Available Integration Methods: Iframes
Duda Website Builder
The lack of Cross-Origin service worker registration prevents parts of the ChamberMaster/MemberZone/GrowthZone module pages from fetching the resources they need to from the primary domain in order to implement layout resources. Available Integration Methods: Iframes