SmartRouting is a simple plugin that handles requests for different contexts. It automatically switches the context based on a (sub)domain AND/OR subfolder.

SmartRouting is a rewrite of the popular XRouting extra. Unfortunately, this extra has not been updated in the MODX repository since 2015 and many unfixed issues have arisen since then, including the lack of full PHP 8 compatibility.


SmartRouting is a simple plugin that handles requests for different contexts. It automatically switches the context based on a (sub)domain AND/OR subfolder.

It is a rewrite of the popular XRouting extra which was not updated since 2015. Many unfixed issues have arisen since then, including the lack of full PHP 8
compatibility.

SmartRouting

This extra caches the order of the menu before installing or updating an extra and restores it after the installation or update is finished. It also moves new menu entries added during installing a package to the bottom.


This extra caches the order of the menu before installing or updating an extra
and restores it after the installation or update is finished. It also moves new
menu entries added during installing a package to the bottom.


MenuKeeper

CustomRequest is an effective routing plugin for MODX Revolution to map pretty but not found URLs to a MODX resource and set the request parameters by separating the URI path at the URI separators or by a regular expression.

As standard option the first characters of the not found URI will be compared with the alias value of each config entry. If found, this config entry is used. The alias path is stripped from the not found URI and the remaining string is used to set the request parameters.

As a second option, the alias value of a config entry could contain a valid regular expression and the not found URI will be matched with that expression. If matched, this config entry is used. The first subpattern part of the expression is stripped from the found pattern and the remaining  string is used to identify the resource where the user is forwarded to later. At least the found pattern is removed from the not found URI and the remaining string is used to set the request parameters.

For full details and some example configurations see the documentation.

Use friendly URLs everywhere in the frontend.

CustomRequest

With this MODX Revolution package you can generate a xPDO where clause on base of request parameters. This where clause can i.e. be used as pdoRessources or getResources where property.

Filter resources with request parameters. With this MODX Revolution package you
can generate a xPDO where clause on base of request parameters. This where
clause can i.e. be used as pdoRessources or getResources where property.

FilterWhere

LangRouter is a language routing plugin for MODx Revolution that is meant to be used with Babel. It takes care of switching contexts that hold the translations, depending on the URL requested by the client.

LangRouter is an installable extended version of https://gist.github.com/gadamiak/3812853. Thanks to gadamiak for the permission to use his code.

Language Router for Babel that uses the browser HTTP_ACCEPT_LANGUAGE header. LangRouter works with so called subfolder based setup.

LangRouter

MySQL

SwitchTemplate changes the template of a MODX resource on the fly with a request parameter. Different settings with different setting keys could be set in a custom manager page.

With each setting a different template could be used to output the resource. As well the template type could be set to chunk or template. If the template type is chunk the resource variables and template variables are prepared as placeholder before the chunk is parsed. The caching of the output of SwitchTemplate could be enabled for each separate setting. The output is cached separate for each resource and each setting. Each setting could be enabled or disabled for selected resources.

SwitchTemplate could be used for different purposes: As Ajax connector, as language switcher, ...

SwitchTemplate changes the template of a MODX resource on the fly with a request parameter. Different settings with different setting keys could be set in a custom manager page.

With each setting a different template could be used to output the resource. As well the template type could be set to chunk or template. If the template type is chunk the resource variables and template variables are prepared as placeholder before the chunk is parsed. The caching of the output of SwitchTemplate could be enabled for each separate setting. The output is cached separate for each resource and each setting. Each setting could be enabled or disabled for selected resources. The output could be filtered to valid AMP markup.

SwitchTemplate could be used for different purposes: As Ajax connector, as language switcher, AMP output ...

SwitchTemplate changes the template of a MODX resource on the fly with a request parameter. Different settings with different setting keys could be set in a custom manager page.

With each setting a different template could be used to output the resource. As well the template type could be set to chunk or template. If the template type is chunk the resource variables and template variables are prepared as placeholder before the chunk is parsed. The caching of the output of SwitchTemplate could be enabled for each separate setting. The output is cached separate for each resource and each setting. Each setting could be enabled or disabled for selected resources. The output could be filtered to valid AMP markup.

SwitchTemplate could be used for different purposes: As Ajax connector, as language switcher, AMP output ...

SwitchTemplate changes the template of a MODX resource on the fly with a request parameter. Different settings with different setting keys could be set in a custom manager page.With each setting a different template could be used to output the resource. As well the template type could be set to chunk or template. If the template type is chunk the resource variables and template variables are prepared as placeholder before the chunk is parsed. The caching of the output of SwitchTemplate could be enabled for each separate setting. The output is cached separate for each resource and each setting. Each setting could be enabled or disabled for selected resources. The output could be filtered to valid AMP markup.SwitchTemplate could be used for different purposes: As Ajax connector, as language switcher, AMP output ...For full details, see the&nbsp;<a href="http://jako.github.io/SwitchTemplate/" title="" target="">SwitchTemplate documentation</a>.&nbsp;This project is hosted on GitHub:&nbsp;<a href="http://jako.github.io/SwitchTemplate/" title="" target="">https://github.com/Jako/SwitchTemplate</a>

SwitchTemplate changes the template of a MODX resource on the fly with a request&nbsp;parameter. Different settings with different setting keys could be set in a&nbsp;custom manager page.&nbsp;With each setting a different template could be used to output the resource.&nbsp;As well the template type could be set to chunk or template. If the&nbsp;template type is chunk the resource variables and template variables are&nbsp;prepared as placeholder before the chunk is parsed. The caching of the output&nbsp;of SwitchTemplate could be enabled for each separate setting. The output is&nbsp;cached separate for each resource and each setting. Each setting could be&nbsp;enabled or disabled for selected resources.&nbsp;SwitchTemplate could be used for different purposes: As Ajax connector, as&nbsp;language switcher ...SettingsSwitchTemplate could be configured by settings created in a custom manager page.&nbsp;Each setting could use the following properties:Setting Name:&nbsp;A name to identify this configuration.Setting Key:&nbsp;The request key value that selects this setting.Chunk/Template Name:&nbsp;The name of a chunk or a template that is parsed and displayed if this setting&nbsp;is used. The name of the chunk is variable by using MODX placeholders. The&nbsp;placeholders are filled with the values of the current resource (no template&nbsp;variables). If this chunk is not found, a chunkname with stripped placeholders is used.Template Type:&nbsp;The template type that is parsed and displayed (`Chunk` or `Template`)Cache the Output:&nbsp;Cache the output of the switched template.Enabled Resources (Default 'All'):&nbsp;A list of MODX resources that could have a switched template.Disabled Resources (Default 'None'):&nbsp;A list of MODX resources that could not have a switched template.ExampleIf you create the following setting in the custom manager page you could call every page in your installation with the url parameter mode=test (i.e. `your.own.domain/?mode=test`) and the page is shown with the template chunk `switchTest`.Setting Name: TestSetting Key: testChunk/Template Name: switchTestTemplate Type: ChunkCache the Output: YesEnabled Resources (Default 'All'):Disabled Resources (Default 'None'):

SwitchTemplate changes the template of a MODX resource on the fly with a request&nbsp;parameter. Different settings with different setting keys could be set in a&nbsp;custom manager page.&nbsp;With each setting a different template could be used to output the resource.&nbsp;As well the template type could be set to chunk or template. If the&nbsp;template type is chunk the resource variables and template variables are&nbsp;prepared as placeholder before the chunk is parsed. The caching of the output&nbsp;of SwitchTemplate could be enabled for each separate setting. The output is&nbsp;cached separate for each resource and each setting. Each setting could be&nbsp;enabled or disabled for selected resources.&nbsp;SwitchTemplate could be used for different purposes: As Ajax connector, as&nbsp;language switcher ...ExampleIf you create the following setting in the custom manager page you could call every page in your installation with the url parameter mode=test (i.e. `your.own.domain/?mode=test`) and the page is shown with the template chunk `switchTest`.Setting Name: TestSetting Key: testChunk/Template Name: switchTestTemplate Type: ChunkCache the Output: YesEnabled Resources (Default 'All'):Disabled Resources (Default 'None'):

SwitchTemplate changes the template of a MODX resource on the fly with a request&nbsp;parameter. Different settings with different setting keys could be set in a&nbsp;custom manager page.With each setting a different template could be used to output the resource.&nbsp;As well the template type could be set to chunk or template. If the&nbsp;template type is chunk the resource variables and template variables are&nbsp;prepared as placeholder before the chunk is parsed. The caching of the output&nbsp;of SwitchTemplate could be enabled for each separate setting. The output is&nbsp;cached separate for each resource and each setting. Each setting could be&nbsp;enabled or disabled for selected resources.SwitchTemplate could be used for different purposes: As Ajax connector, as&nbsp;language switcher ...ExampleIf you create the following setting in the custom manager page you could call every page in your installation with the url parameter mode=test (i.e. `your.own.domain/?mode=test`) and the page is shown with the template chunk `switchTest`.Setting Name: TestSetting Key: testChunk/Template Name: switchTestTemplate Type: ChunkCache the Output: YesEnabled Resources (Default 'All'):Disabled Resources (Default 'None'):

SwitchTemplate

Screenshots

About SwitchTemplate

Information

Instructions

New in 2.0.0-pl

Current releases

Related Extras

More by Thomas Jakobi

SmartRouting

MenuKeeper

CustomRequest

FilterWhere

Browse Category

Content