While UXi sites do publish content using the WordPress Content Management System, they do not use the typical page layout files, hosting solution, or cPanel dashboard like many other WordPress sites.
A keystone feature of UXi sites is our ability to make updates to all UXi sites at once. These updates include new features, plug-in updates, security improvements, etc. To accomplish this, we use a single code-base for all UXi sites, custom databases, and a highly customized hosting infrastructure.
Another main focus for the UXi platform is long-term site security. Unlike a lot of other standard hosting packages, all new features / security upgrades / plug-in updates are included with UXi hosting. WordPress is a constantly changing platform, and as sites and their plug-ins become out-of-date, they become highly vulnerable to hackers. This concern is greatly minimized with UXi sites, as our team is monitoring available updates and making them happen without any involvement from the user.
Page layouts for UXi sites don't use standard PHP files that are normally uploaded / downloaded via FTP. Instead, the layouts are built with the front-end editor. This creates entries in a custom database also hosted on Amazon Web Hosting Servers.
Most typical sites host the files in directories like the ones listed below and use FTP to upload new files or create new directories.
However, our UXi sites don't use traditional hosting. The site files aren't kept in a root directory like those shown above. We utilize a content delivery network, or CDN to host 100% of the files used for UXi sites, so our files also reside on Amazon Web Hosting servers.
cPanel / Hosting Access
Since the are no layout files or media assets hosted on the root domain, there is nothing to access with a standard hosting dashboard like cPanel, Plesk, or Webmin.
In short, to ensure that no user ever has to manage these updates, fight Malware or other methods of hacking, UXi relies on it's customized hosting environment and database structure.
Because of UXi's unique file and database architecture, We don't have the option to move the entire site to a new server or send layout files.
If users are interested in moving their site elsewhere, we can send them the contents of their UXi site and they can use that to reproduce it on their own host. Here's the best plan:
- Start with a standard WordPress installation using the latest available version.
- Import the XML files I've included (media, pages, posts)
- Install a new WordPress theme of their liking, and modify it using images already uploaded via the XML import. -OR- If they'd like to manually handle the image upload, they can disregard the media XML. We can also include zipped files of the media library contents if they'd like to manually upload assets.
- License and Install necessary plug-ins.
- Add forms. To make replicating the forms easy, we can export them in a single JSON file that can be imported into the new site.
However, we're unable to use our license for sites not hosted with us, so if they'd like to use Gravity Forms, that will be up to them. I've exported their form entries in separate CSV files for reference of any leads from the UXi site.