In order for the aXcelerate WordPress plugin to function correctly, please verify the following requirements have been met. You may require the assistance of a IT or web development professional.
- The server WordPress runs on uses PHP version 5.5 or above
- WordPress version 4.6 or greater is used
- The WordPress default jQuery is not overridden (the theme and plugins you intend to use do not overwrite the default WordPress jQuery)
- An SSL security certificate has been purchased from your hosting provider and is installed at the destination website URL. The URL will need ‘https’ to appear and browsers to be able to recognise the certificate. Without this the plugin will be unable to verify the security of personally identifiable information and live data cannot be processed.
- The plugin max upload file size is 4MB or greater
- Administrative login credentials to your website have been provided to aXcelerate (please use this ticket to provide these details)
- Ensure all caching plugins have been removed from your site during configuration. Caching plugins will cause dynamic content to be stored for returning users, meaning it can display outdated information or not show changes that have been made to the enrolment forms or the site.
- A WordPress theme should be installed on the site. Typically we recommend ‘Be theme’ or 'Avada', however you are free to use any WordPress theme that abides by best-practices, specifically not overwriting the default WordPress version of jQuery. Please be aware that while our plugin should work with the vast majority of widely used WordPress themes we cannot guarantee that the theme used by your site will not cause conflicts with our software. You may use the WordPress default template if you wish to, however the styling options will be limited.
- Cron Events need to be able to run on the site. This is necessary for The Events Calendar, Enrolment Resumption and Post Enrolment to function correctly.
If your website is live and public-facing, we recommend you set up a working copy of the site in a development environment (e.g: dev.mainsite.com.au), to mitigate any potential issues. It would be the responsibility of your web developer to organise the development environment and port the development site over to the live domain upon completion of the project if you choose to do so. Any changes made to your live site during the project will be overwritten upon migration of the development site.
It is possible for us to work on a public-facing website developing private pages and we have an excellent history doing so. Forgoing the setup of a development environment will likely speed up the project process, however we cannot accept liability for any potential issues that arise with a live website. Please discuss with your web developer which option is best suited to your business.