MODExt MODx Object

The MODx JS Object¶

MODExt comes with a global MODx JS object on each manager page. This object has a few custom methods that can be executed from any custom manager page using MODExt, and also sets up some default settings and customizations.

Custom Class Variables¶

The following variables are accessible from the MODx JS object:

MODx.request¶

This is a JS object that contains all the current GET parameters for the page. Example:

var id = MODx.request.id;

MODx.config¶

This object contains all the active System Settings in MODX by key:

var tpl = MODx.config.default_template;

Other Variables¶

There are a few other variables available on the MODx.config object that are not System Settings:

MODx.action¶

This object contains a map of all the modAction objects (or MODX manager controllers), mapped by their controller to their ID:

var actionId = MODx.action['resource/create'];

As of MODX 2.2, the non-core Actions are prefixed with their namespace. Prior to 2.2 it would just be the action controller. For example a "controllers/index" action in a "mycomponent" namespace would be retrievable using the following in 2.2 and up:

var actionId = MODx.action['mycomponent:controllers/index'];

MODx.version¶

Contains MODX version information, with the following attributes:

Example:

var fv = MODx.version.full_version;

MODx.user¶

This object will contain the two following properties for the currently logged-in manager user:

var userId = MODx.user.id;

MODx.perm¶

This will contain the following permissions should they be granted to the user (they will not exist if the user does not have the permission):

if (MODx.perm.file_upload) { /* ...code... */ }

Custom Methods¶

The MODx object also has quite a few custom methods available to it:

MODx.load¶

This method will create a new object of any specified xtype and passed in configuration parameters. Example:

var w = MODx.load({
  xtype: 'modx-window-namespace-create'
  ,blankValues: true
});
w.setValues({ name: 'My Namespace' });
w.show();

Any defined class that has a registered xtype can be loaded from this method.

MODx.clearCache¶

This fires up the console that clears the MODX cache. It will also fire the 'beforeClearCache' and 'afterClearCache' events on the MODx object. If the System Setting clear_cache_refresh_trees is set to 1, it will also refresh all the active left-hand trees.

MODx.releaseLock¶

This will release the lock on the current active Resource. This method should not be fired on non-Resource editing pages. It will fire the 'beforeReleaseLocks' and 'afterReleaseLocks' events on the MODx object.

MODx.sleep¶

This method will cause JavaScript to sleep (or halt) for a specified number of seconds:

MODx.sleep(3); /* sleep for 3 seconds */

MODx.logout¶

This method will automatically logout the active manager user. It fires the 'beforeLogout' and 'afterLogout' events on the MODx object. If both events are successful, it will then redirect the user to the login screen.

MODx.loadHelpPane¶

This will load the current Help screen for the active page. Normally this is set by default on the modAction record for the page, and its URL can be found by the MODx.config.help_url property. You can, however, override this to fire up any URL into the panel:

/* show the modx.com site in the Help modal */
MODx.config.help_url = 'https://modx.com/';
MODx.loadHelpPane();

MODx.preview¶

Loads the current MODX site for the active Context.

MODx.isEmpty¶

Checks to see if the specified variable is "empty" (in the PHP sense). This means it is either:

• false, 'false', or 'FALSE'
• 0 or '0'
• '' (blank string)
• null
• undefined

MODx.debug¶

(2.1+ only)

This will send off a debug message if and only if the MODX System Setting ui_debug_mode is set to Yes/1. The debug message will use console.log to output to the console. This can be useful to add debugging and assertions to your code without breaking it in production sites (which would presumably have ui_debug_mode off).