MODX Revolution (Revo) is an easy-to-use Content Management System (CMS) and Application Framework. Despite the limitless possibilities, we think you’ll find it refreshingly intuitive to work with. At every step, MODX strives to deliver Creative Freedom.
In addition to this documentation site, the MODX Community is vibrant and always willing to help. Additionally, there are trusted, experienced MODX Professionals with whom you can engage to get the job done. MODX also has vendor-backed commercial support options.
MODX Revolution Theme contains a lot of features. But some of the important features are:
MODX Revolution is a Responsive Theme used basically in business. In this section, you will find resources on how to Install this theme.
-The installation of this theme is very easy. After you have downloaded MODX Revolution upload the .zip file to your server.
– On the server itself, either through your control panel extraction script or in the server’s file manager, extract the file to its own directory. Copy or move all the files within the new extracted MODX version directory to the directory that you wish to install MODX into. You may delete the extracted folder and its contents, as well as the MODX .zip file once your installation is complete.
Development sites often begin in a subdirectory, and then are moved to the root directory when completed. The subdirectory method is useful if you’ve got an existing site that must remain available during development, or for subdomain MODX installations. It is also possible to leave MODX in a subdirectory and use .htaccess to rewrite your URLs to the root.
If your existing site is static HTML with an index.html or similar start page, you can install MODX into the root folder alongside your static site while developing. When you are ready to go live, rename or move your static HTML files and MODX will take over. Do not enable Friendly URL’s if using this method until after your HTML files have been moved or renamed. As always, back up your existing site prior to installing MODX Revolution or making any changes to your current file structure.
Do not install MODX Revolution into a directory that contains another dynamically driven site or CMS until that site is removed. Use the subdirectory method to develop MODX in this case.
MODx Revolution introduces an entirely new program structure for its core. The manager is also built on what are called controllers templates, which use AJAX processing to send data to connectors that access processors.
The controllers are simply PHP files that load the correct Smarty template to display and fetch any pre-render data for the template. Revolution abstracts these controllers into the DB as modAction’s, allowing 3rd party developers to easily create custom manager pages that ‘hook’ into the current MODx system without modifying the core.
ModAction requires a controller and a template to exist, that must be found in the manager/controllers and manager/templates directories. They have a few certain parameters that are worth noting:
-First, go to the Contexts page, via System -> Contexts. Then, click on “Create New” in the grid. This will prompt you for a key and description. From there, right-click on your newly-created context, and click “Update Context”.
-This will bring you to a screen displaying the Context, and an empty grid of settings. From here you can add Context-specific settings that will override any System Settings. Your new context will be completely empty, requiring you to include any and all settings you will be using.
-You can create settings for any defined context by clicking on System -> Contexts, then right-click any context and select “Update Context”.
-Each context can have its own settings that override or extend the System Settings. Contextual settings can, in turn, be overridden or extended by User Settings. The hierarchy to remember is this:
System Setting -> Context Setting -> User Setting
When creating a new context, make sure your desired user-groups have access to it:
Security/Permissions -> Edit desired User Group -> Permissions -> Context Access