From 01ef93ca2ee19957e9a9731c942523cb6dac07d1 Mon Sep 17 00:00:00 2001 From: Ivan Bochkarev Date: Sat, 15 Aug 2026 09:02:42 +0600 Subject: [PATCH] docs: Remove Evolution product notifications and references Drop homepage Evolution sections, rewrite FAQs for MODX 2.x/3.x, stub legacy 1.x migration pages, and strip comparative Evolution asides so this documentation no longer points readers at an unsupported product. Fixes #30 --- .../settings/tvs_below_content.md | 2 +- .../tag-syntax/output-filters/index.md | 2 +- en/contribute/issues.md | 4 +- .../custom-manager-pages/index.md | 2 - .../getting-started/tutorial/index.md | 2 +- en/extending-modx/menus/action-list.md | 2 +- en/extras/advsearch/index.md | 2 +- en/extras/ajaxupload/index.md | 2 +- en/extras/breadcrumbs/index.md | 18 ++++---- en/extras/filedownload-r/index.md | 2 +- en/extras/fileupload/index.md | 2 +- en/extras/firstchildredirect/index.md | 8 ++-- en/extras/formit/index.md | 2 +- en/extras/getdynadescription/index.md | 2 +- en/extras/getresources/index.md | 2 +- en/extras/gorevo/index.md | 6 +-- en/extras/index.md | 1 - en/extras/metax/index.md | 2 +- en/extras/mxcalendar/index.md | 17 +------ en/extras/newspublisher/index.md | 2 +- en/extras/obfuscateemail-revo/index.md | 2 +- en/extras/renderresources/index.md | 2 +- en/extras/simplesearch/index.md | 2 +- .../socialsuite.getfacebookprofile.md | 2 +- en/extras/wayfinder/index.md | 18 ++------ .../faqs-and-troubleshooting.md | 4 +- en/getting-started/maintenance/upgrading.md | 2 - .../maintenance/upgrading/2.0.0-rc2.md | 2 +- .../maintenance/upgrading/2.0.5.md | 2 - .../maintenance/upgrading/2.1.md | 2 +- .../maintenance/upgrading/2.2.md | 2 - .../maintenance/upgrading/evolution.md | 37 +--------------- .../upgrading/evolution/functional-changes.md | 44 +------------------ .../upgrading-to-3.0/breaking-changes.md | 2 +- .../upgrading-to-3.0/system-settings.md | 2 +- en/index.md | 6 --- .../faqs-and-troubleshooting.md | 20 ++------- es/index.md | 6 --- .../settings/tvs_below_content.md | 2 +- .../tag-syntax/output-filters/index.md | 2 +- ru/contribute/issues.md | 6 +-- .../custom-manager-pages/index.md | 2 - ru/extending-modx/menus/action-list.md | 2 +- ru/extras/ajaxupload/index.md | 2 +- ru/extras/formit/index.md | 2 +- ru/extras/index.md | 1 - .../faqs-and-troubleshooting.md | 4 +- ru/getting-started/maintenance/upgrading.md | 2 - .../maintenance/upgrading/2.0.0-rc2.md | 2 +- .../maintenance/upgrading/2.0.5.md | 2 - .../maintenance/upgrading/2.1.md | 2 +- .../maintenance/upgrading/2.2.md | 2 - .../maintenance/upgrading/evolution.md | 35 +-------------- .../upgrading/evolution/functional-changes.md | 43 +----------------- .../upgrading-to-3.0/breaking-changes.md | 2 +- .../upgrading-to-3.0/system-settings.md | 2 +- ru/index.md | 6 --- 57 files changed, 70 insertions(+), 290 deletions(-) diff --git a/en/building-sites/settings/tvs_below_content.md b/en/building-sites/settings/tvs_below_content.md index fff173d92..8725d24a2 100644 --- a/en/building-sites/settings/tvs_below_content.md +++ b/en/building-sites/settings/tvs_below_content.md @@ -14,7 +14,7 @@ This controls whether Template Variables show up on their own tab or below resou ### Yes -All TVs appear below the Resource content, just like they did for MODX Evolution. +All TVs appear below the Resource content. ![](tvs_below_content.jpg) diff --git a/en/building-sites/tag-syntax/output-filters/index.md b/en/building-sites/tag-syntax/output-filters/index.md index ccd06d0a2..43aca3200 100644 --- a/en/building-sites/tag-syntax/output-filters/index.md +++ b/en/building-sites/tag-syntax/output-filters/index.md @@ -12,7 +12,7 @@ Filters in Revolution allow you to manipulate the way data is presented or parse ## Output Filter -In Revolution, the Output Filter applies one or more of series of output modifiers, which behave similarly to PHx calls in MODX Evolution - except they're built into the core. The syntax looks like this: +An Output Filter applies one or more output modifiers built into the core. The syntax looks like this: ```php [[element:modifier=`value`]] diff --git a/en/contribute/issues.md b/en/contribute/issues.md index b7e05646a..d4ecaf602 100644 --- a/en/contribute/issues.md +++ b/en/contribute/issues.md @@ -78,8 +78,8 @@ Please file issues for the appropriate project in the issues section at Github: Issues that the community can initiate or collaborate on include: -- bugs in MODX (Evolution and Revolution) and some Extras -- feature requests for MODX (Evolution and Revolution) and some Extras +- bugs in MODX and some Extras +- feature requests for MODX and some Extras - reports of bugs or problems with various MODX websites or parts thereof Many feature requests and bug reports stem originally from discussions in the forums. If you are filing a bug report or feature request for which there is forum discussion, please include a link to the forum thread. diff --git a/en/extending-modx/custom-manager-pages/index.md b/en/extending-modx/custom-manager-pages/index.md index ec8cb28f3..a3c528c82 100644 --- a/en/extending-modx/custom-manager-pages/index.md +++ b/en/extending-modx/custom-manager-pages/index.md @@ -10,8 +10,6 @@ CMP stands for Custom Manager Page, and it is simply a custom page that loads in If you are a developer looking to build an extra which includes a component, you should follow the [Developing an Extra for MODX Revolution tutorial](extending-modx/tutorials/developing-an-extra), as it walks you through all the specific steps and terminology based on an example package called doodles. This page only goes into a minimum set up for custom manager pages. -The equivalent of a CMP or Component in MODX Evolution is a Module, though the technique in which they are created is quite different. - ## Namespaces CMPs need a namespace in order for MODX to know where to load the files from. diff --git a/en/extending-modx/getting-started/tutorial/index.md b/en/extending-modx/getting-started/tutorial/index.md index b7d1b48d1..ad333a563 100644 --- a/en/extending-modx/getting-started/tutorial/index.md +++ b/en/extending-modx/getting-started/tutorial/index.md @@ -4,7 +4,7 @@ _old_id: "1116" _old_uri: "2.x/case-studies-and-tutorials/php-coding-in-modx-revolution,-pt.-i" --- -So, a lot of people have been asking about the new codebase. Is it coder-friendly? Will it be a big deviation from 0.9.6/Evolution? Does it support OOP projects? Is it faster? Will it be easy to learn? +So, a lot of people have been asking about the codebase. Is it coder-friendly? Does it support OOP projects? Is it faster? Will it be easy to learn? In these tutorials, we plan to answer those questions with YES. diff --git a/en/extending-modx/menus/action-list.md b/en/extending-modx/menus/action-list.md index fe7054666..923537df9 100644 --- a/en/extending-modx/menus/action-list.md +++ b/en/extending-modx/menus/action-list.md @@ -10,7 +10,7 @@ _old_uri: "2.x/developing-in-modx/advanced-development/custom-manager-pages/acti Within the Manager, you can access a list of actions with the `MODx.action` variable. Do NOT rely on any list with manager action IDs as these IDs are not hardcoded in the MODX Core, but instead they are dynamically created during setup and just happen to have a certain ID. -Back in Evolution there was indeed a fixed list, but there has never been one in Revolution. +There has never been a fixed list of manager actions in modern MODX. ### Before Revolution 2.3 diff --git a/en/extras/advsearch/index.md b/en/extras/advsearch/index.md index 49f3f9ceb..81b2f2932 100644 --- a/en/extras/advsearch/index.md +++ b/en/extras/advsearch/index.md @@ -20,7 +20,7 @@ MySQL-only search (`&engine=` `mysql`, the default) does not need ZendSearch. ## History -AdvSearch was written by [Coroico](https://github.com/coroico) and first released on August 14th, 2011. It is loosely based on AjaxSearch for MODX Evolution by KyleJ/Coroico, with optional Lucene indexing via ZendSearch. +AdvSearch was written by [Coroico](https://github.com/coroico) and first released on August 14th, 2011. It is loosely based on AjaxSearch by KyleJ/Coroico, with optional Lucene indexing via ZendSearch. ### Download diff --git a/en/extras/ajaxupload/index.md b/en/extras/ajaxupload/index.md index 646ba7444..383dd374d 100644 --- a/en/extras/ajaxupload/index.md +++ b/en/extras/ajaxupload/index.md @@ -18,7 +18,7 @@ With two Formit hooks the upload queue could be pre filled from Formit field val ## History & Info -AjaxUpload was initially written in 2012 for MODX Evolution and is maintained and developed since then by [Thomas Jakobi](https://github.com/jako). +AjaxUpload was first released in 2012 and is maintained by [Thomas Jakobi](https://github.com/jako). ### Download diff --git a/en/extras/breadcrumbs/index.md b/en/extras/breadcrumbs/index.md index 9ce93779e..d1c69e0ca 100644 --- a/en/extras/breadcrumbs/index.md +++ b/en/extras/breadcrumbs/index.md @@ -15,7 +15,7 @@ Breadcrumbs is a simple navigation trail [Snippet](developing-in-modx/basic-deve ## History -Breadcrumbs has been around since the start of MODX 0.9.1, or MODX Evolution, with its first release on June 30th, 2006. It has had many different authors since its inception. +Breadcrumbs has been around since MODX 0.9.1, with its first release on June 30th, 2006. It has had many different authors since its inception. ### Public Releases @@ -26,14 +26,14 @@ Breadcrumbs has been around since the start of MODX 0.9.1, or MODX Evolution, wi | 1.1-beta1 | May 21st, 2009 | splittingred | Revolution | | 1.0-alpha4 | April 21st, 2009 | splittingred | Revolution | | 1.0-alpha3 | March 24th, 2009 | splittingred | Revolution | -| 1.0.1 | April 25th, 2008 | jaredc | Evolution | -| 1.0.0 | April 22nd, 2008 | jaredc | Evolution | -| 0.9g | March 26th, 2008 | webe | Evolution | -| 0.9f | January 17th, 2008 | jaredc | Evolution | -| 0.9e | January 11th, 2008 | jaredc | Evolution | -| 0.9d | July 12th, 2006 | jaredc | Evolution | -| 0.91 | July 10th, 2006 | tillda | Evolution | -| 0.9c | June 30th, 2006 | jaredc | Evolution | +| 1.0.1 | April 25th, 2008 | jaredc | 1.x | +| 1.0.0 | April 22nd, 2008 | jaredc | 1.x | +| 0.9g | March 26th, 2008 | webe | 1.x | +| 0.9f | January 17th, 2008 | jaredc | 1.x | +| 0.9e | January 11th, 2008 | jaredc | 1.x | +| 0.9d | July 12th, 2006 | jaredc | 1.x | +| 0.91 | July 10th, 2006 | tillda | 1.x | +| 0.9c | June 30th, 2006 | jaredc | 1.x | ### Download diff --git a/en/extras/filedownload-r/index.md b/en/extras/filedownload-r/index.md index 9490a4404..564c4cbba 100644 --- a/en/extras/filedownload-r/index.md +++ b/en/extras/filedownload-r/index.md @@ -11,7 +11,7 @@ This way, the full url of the file will not be revealed and the files/directorie Each file can also be assigned a download counter, which is stored in a custom database table. The FileDownloadR project was started in 2011 by [Rico Goldsky](https://github.com/goldsky) as a rewite of the -FileDownload Evolution package by Kyle Jaebker. It is maintained since 2023 by [Thomas Jakobi](https://github.com/Jako). +Based on the earlier FileDownload package by Kyle Jaebker. Maintained since 2023 by [Thomas Jakobi](https://github.com/Jako). FileDownloadR can be installed from within the MODX Revolution manager via Package Management, or from the MODX Extras Repository, available on [modx.com/extras/package/filedownloadr](https://modx.com/extras/package/filedownloadr) diff --git a/en/extras/fileupload/index.md b/en/extras/fileupload/index.md index 2e9f6e3cd..859eb72c3 100644 --- a/en/extras/fileupload/index.md +++ b/en/extras/fileupload/index.md @@ -20,7 +20,7 @@ FileUpload presents a file upload form. - Downloads: 5,348 - License: Free - [Discuss Extra](http://www.modxcms.com/forums/index.php?topic=5889) -- Requires: Evolution 1.0.x or greater +- Requires: MODX 2.x or greater - Supports: mysql ## History diff --git a/en/extras/firstchildredirect/index.md b/en/extras/firstchildredirect/index.md index 1c62da2ae..e1f2232e3 100644 --- a/en/extras/firstchildredirect/index.md +++ b/en/extras/firstchildredirect/index.md @@ -4,14 +4,12 @@ _old_id: "641" _old_uri: "revo/firstchildredirect" --- -FirstChildRedirect is a snippet that will redirect a certain resource to its first child resource. There is a version for both Revolution and Evolution, of which the Revolution one allows more easy customization. +FirstChildRedirect is a snippet that redirects a resource to its first child resource. ## Installation & bugs FirstChildRedirect can be installed through the MODX Revolution Package Manager, or installed manually by downloading the package from the MODX Extras website, uploading it to core/packages and adding a new package through the package manager from a local search. -FirstChildRedirect is also available for MODX Evolution, however that does not support all additional parameters as described below. - ## Snippet usage The snippet is really easy to use, just call uncached it in the content or template of the container resource you want to redirect to its first child. @@ -22,10 +20,10 @@ The snippet is really easy to use, just call uncached it in the content or templ Alternatively, you can specify one or more parameters in the snippet call which influence how the redirect will be handled. -| Parameter | Evo/Revo | Details | Default | +| Parameter | Optional | Details | Default | | ------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------- | | &docid | Yes/Yes | Setting a docid parameter to another resource's ID will tell the snippet to use that resource as the container to look in for the first child. | current resource ID (ie `[[*id]]`) | -| &default | No\*/Yes | The resource to redirect to when there are no children resources found. This can be either a resource ID or one of the following settings: site\_start, site\_unavailable\_page, error\_page or unauthorized\_page. \* In Evolution, this also defaults to site\_start and can be modified in the actual snippet code if required. Just find $modx->config\['site\_start'\] and replace that by an ID or one of the system settings mentioned. | site\_start setting | +| &default | No\*/Yes | The resource to redirect to when there are no children resources found. This can be either a resource ID or one of the following settings: site\_start, site\_unavailable\_page, error\_page or unauthorized\_page. | site\_start setting | | &sortBy | No/Yes | Any valid resource fieldname to sort the children found on. | menuindex setting | | &sortDir | No/Yes | Either 'desc' for descending (redirects to highest menuindex or &sortBy field found) or 'asc' for ascending (redirects to lowest menuindex or &sortBy field found). | "asc" | | &responseCode | No/Yes | The response code (status code) for sending the redirect. Defaults to a 301 ("HTTP/1.1 301 Moved Permanently") but also contains shortcuts for 302 (temporarily) - you can also specify the complete response code (including the HTTP part and name) for others. _Added in 2.3.1._ | 301 | diff --git a/en/extras/formit/index.md b/en/extras/formit/index.md index e35afe750..fec316339 100644 --- a/en/extras/formit/index.md +++ b/en/extras/formit/index.md @@ -34,7 +34,7 @@ As of FormIt 1.1.4, all fields will automatically have `stripTags` applied. To a ## How to Use -Simply place the FormIt snippet call into the Resource that contains the form you want to use. Unlike similar predecessors (most notably eForm in MODX Evolution), you do not put the form into a Chunk and reference the Chunk in the FormIt snippet call: you literally put the snippet call along side the form you want it to process. Specify the "hooks" (or post-validation processing scripts) in the snippet call. Then add validation via the _&validate_ and _&customValidators_ parameters in the snippet tag. +Simply place the FormIt snippet call into the Resource that contains the form you want to use. Place the snippet call next to the form you want it to process. Do not put the form into a Chunk and reference that Chunk from the FormIt call. Specify the "hooks" (or post-validation processing scripts) in the snippet call. Then add validation via the _&validate_ and _&customValidators_ parameters in the snippet tag. If you have multiple forms on a page, set the _&submitVar_ property on your Snippet call to a name of a form element within the form (ie, ``&submitVar=`form1-submit` ``). This tells FormIt to only process form requests with that POST variable. Multiple forms should be used with INPUT type="submit" name="form1-submit", button elements have been reported not working. diff --git a/en/extras/getdynadescription/index.md b/en/extras/getdynadescription/index.md index 2961ab3c9..d1c906af6 100644 --- a/en/extras/getdynadescription/index.md +++ b/en/extras/getdynadescription/index.md @@ -6,7 +6,7 @@ _old_uri: "revo/getdynadescription" ## What is getDynaDescription? -Conversion and rewrite of the Evolution getDynaDescription snippet. +Conversion and rewrite of the earlier getDynaDescription snippet. Creates Meta tags from a TV, the resource description field, or the resource content field. diff --git a/en/extras/getresources/index.md b/en/extras/getresources/index.md index 0200f5a8f..7218767e6 100644 --- a/en/extras/getresources/index.md +++ b/en/extras/getresources/index.md @@ -21,7 +21,7 @@ getResources was first written by Jason Coward (opengeek) and released on June 3 It can be downloaded from within the MODX Revolution manager via [Package Management](developing-in-modx/advanced-development/package-management "Package Management"), or from the MODX Extras Repository, here: -It is NOT a replacement for Ditto, but rather an alternative component that can accomplish some of the things that the more specialized components do, i.e. Ditto, Wayfinder, Breadcrumbs; basically anything that output the properties for a list of Resources (formerly Documents in MODX Evolution). +It is NOT a replacement for Ditto, but rather an alternative component that can accomplish some of the things that the more specialized components do, i.e. Ditto, Wayfinder, Breadcrumbs; basically anything that outputs the properties for a list of Resources. Documentation and tutorials on Russian can be found here: diff --git a/en/extras/gorevo/index.md b/en/extras/gorevo/index.md index ce9c7f833..c037b912c 100644 --- a/en/extras/gorevo/index.md +++ b/en/extras/gorevo/index.md @@ -6,7 +6,7 @@ _old_uri: "revo/gorevo" ## What is GoRevo? -GoRevo is a commercial extra that performs an intelligent migration of MODX Evolution sites to MODX Revolution. +GoRevo is a commercial Extra that migrates older 1.x sites to modern MODX. ### Features @@ -25,7 +25,7 @@ GoRevo is a commercial extra that performs an intelligent migration of MODX Evol - Custom Plugins - Selected files and/or directories -GoRevo will attempt to convert Ditto, Breadcrumbs, WebLogin, WebLoginPE, and PHX tags to work in Revolution. Wayfinder tags will generally work as is. GoRevo will also attempt to duplicate the User Groups, User Login credentials, and Resource Groups from the Evolution site. +GoRevo attempts to convert Ditto, Breadcrumbs, WebLogin, WebLoginPE, and PHX tags for modern MODX. Wayfinder tags usually work as-is. GoRevo also tries to duplicate User Groups, login credentials, and Resource Groups from the source site. You can get more information about GoRevo at [Bob's Guides](https://bobsguides.com/why-choose-gorevo.html). @@ -33,7 +33,7 @@ You can get more information about GoRevo at [Bob's Guides](https://bobsguides.c - Author: Bob Ray [Bob's Guides](https://bobsguides.com) -GoRevo took about six months of intensive development. It has been used to convert many Evolution sites to MODX Revolution, including many conversions performed by MODX LLC. +GoRevo took about six months of intensive development. Teams have used it to convert many older 1.x sites to modern MODX, including conversions performed by MODX LLC. This version of the GoRevo extra was developed by Bob Ray in 2014. As of Jun 22, 2017 it had been last updated on December 21, 2017, had 190 commits, and had been downloaded 61 times. The GoRevo package consists of 1,563 separate files, containing 32,211 lines of code. diff --git a/en/extras/index.md b/en/extras/index.md index 4cec688a3..b5e5cfc31 100644 --- a/en/extras/index.md +++ b/en/extras/index.md @@ -102,7 +102,6 @@ This does not mean however that these are your only options. Browse the reposito ### Upgrading MODX - [UpgradeMODX](https://bobsguides.com/upgrade-modx-package.html) allows you to upgrade MODX Revolution from within the MODX Manager. -- [GoRevo](https://bobsguides.com/why-choose-gorevo.html) (premium extra from Bob Ray) provides a tool for migrating from MODX Evolution to MODX Revolution. ## Distributing your own Extras diff --git a/en/extras/metax/index.md b/en/extras/metax/index.md index c01f92a63..fa6eaf11a 100644 --- a/en/extras/metax/index.md +++ b/en/extras/metax/index.md @@ -13,7 +13,7 @@ Requirements ## History -MetaX was created in 2010 for both MODX Evolution and later MODX Revolution using the same codebase. Since then, the codebase for MetaX has been split to take better advantage of new features in MODX Revolution. All versions of MetaX have been released by it's creator, Sal Sodano ( ), with other contributors along the way. +MetaX was created in 2010. Later builds target MODX Revolution features. All versions of MetaX have been released by its creator, Sal Sodano (), with other contributors along the way. ### Development diff --git a/en/extras/mxcalendar/index.md b/en/extras/mxcalendar/index.md index 0a910fa8f..55433bdcf 100644 --- a/en/extras/mxcalendar/index.md +++ b/en/extras/mxcalendar/index.md @@ -10,7 +10,7 @@ _old_uri: "revo/mxcalendar" ## About mxCalendar -mxCalendar is a extra created for both Evolution and Revolution to allow for full calendar editing using the native Manager of ModX. The calendar supports various views including calendar, list, and detail of which all views support the ModX template standards for fully customizing your themes. In addition mxCalendar supports feature rich calendar functions such as repeating events, Google Maps, cateogries, context, and unique calendars. +mxCalendar is an Extra for full calendar editing in the MODX Manager. The calendar supports various views including calendar, list, and detail of which all views support the ModX template standards for fully customizing your themes. In addition mxCalendar supports feature rich calendar functions such as repeating events, Google Maps, cateogries, context, and unique calendars. ## Installation @@ -18,21 +18,6 @@ mxCalendar is a extra created for both Evolution and Revolution to allow for ful It can be downloaded from within the MODX Revolution manager via [Package Management](developing-in-modx/advanced-development/package-management "Package Management"), or from the MODX Extras Repository, here: . When using the Package Management for direct download you can simply click on the "Install" button after download completes. If you choose to download from the extras site you will then need to FTP, or otherwise move, the transport package zip file to your "/core/packages/" folder first. After you have copied the transport zip file to your packages folder you will then need to launch Package Management from inside the Manager (ver 2.2.x) and then select the down arrow next to "Download Extras" and select the last option "Search Locally for Packages" and then find "mxcalendars" in the list of packages and choose "install". -### ModX Evolution - -You will need to download from the ModX Extras Repository, here . After you have downloaded you will need to follow these steps. - -1. Unzip folder to your favorite place -2. Upload mxCalendar folder to your sites root /assets/modules/ folder -3. Copy contents of "snippets/mxCalendar.module.txt" file from the unzipped folder -4. Log into your Manager interface and goto the Modules > Manage Modules section -5. Select the New Module button -6. In the Module name field place mxcalendar -7. Past the content of "snippets/mxCalendar.module.txt" into the Module code (php) section -8. Select Save -9. Click the gear icon next to the new entry "mxcalendar" and select Run Module -10. You should see a screen saying the installation was successful, so click the Start button -11. Now you are in the new manager ## Creating Calendars diff --git a/en/extras/newspublisher/index.md b/en/extras/newspublisher/index.md index 052f650eb..c99d6fe0e 100644 --- a/en/extras/newspublisher/index.md +++ b/en/extras/newspublisher/index.md @@ -27,7 +27,7 @@ Install using Package Manager and see the tutorial at [Bobs Guides](https://bobs ## History -- Evolution Author: Raymond Irving [SlideShare](https://www.slideshare.net/xwisdom) +- Earlier author: Raymond Irving [SlideShare](https://www.slideshare.net/xwisdom) - Revolution Author: Bob Ray [Bob's Guides](https://bobsguides.com) - Contributors: Invaluable fixes, improvements, and feature additions were created and tested by Markus Schlegel, donshakespeare, Bruno17, Gregor Šekoranja, Alberto Ramacciotti, and others too numerous to mention. diff --git a/en/extras/obfuscateemail-revo/index.md b/en/extras/obfuscateemail-revo/index.md index 648bcf6e5..6015b156d 100644 --- a/en/extras/obfuscateemail-revo/index.md +++ b/en/extras/obfuscateemail-revo/index.md @@ -67,5 +67,5 @@ Protect your users and make your self look good in the process. ## History -This Plugin was originally released for MODX Evolution by Aloysius Lim: . When I made the jump to MODX Revolution a few years ago, I brought this plugin along as it had served my clients well. With the Release of MODX Revolution 2.1 and its move away from legacy code, some updates had to be performed. +This plugin was originally released by Aloysius Lim: . Later ports target MODX Revolution. With MODX Revolution 2.1 and its move away from legacy code, some updates had to be performed. I hope you find ObfuscateEmail-Revo as effective as I have over the years. \ No newline at end of file diff --git a/en/extras/renderresources/index.md b/en/extras/renderresources/index.md index 041b14362..84670b003 100644 --- a/en/extras/renderresources/index.md +++ b/en/extras/renderresources/index.md @@ -21,7 +21,7 @@ renderResources was first written by Jason Coward (opengeek) and released on Mar It can be downloaded from within the MODX Revolution manager via [Package Management](developing-in-modx/advanced-development/package-management "Package Management"), or from the MODX Extras Repository, here: -It is NOT a replacement for Ditto, but rather an alternative component that can accomplish some of the things that the more specialized components do, i.e. Ditto, Wayfinder, Breadcrumbs; basically anything that output the properties for a list of Resources (formerly Documents in MODX Evolution). +It is NOT a replacement for Ditto, but rather an alternative component that can accomplish some of the things that the more specialized components do, i.e. Ditto, Wayfinder, Breadcrumbs; basically anything that outputs the properties for a list of Resources. ## Usage diff --git a/en/extras/simplesearch/index.md b/en/extras/simplesearch/index.md index 8a90bd54a..ec17e6c83 100644 --- a/en/extras/simplesearch/index.md +++ b/en/extras/simplesearch/index.md @@ -15,7 +15,7 @@ SimpleSearch is a simple search component for MODX Revolution. It supports searc ## History -SimpleSearch was written by [Shaun McCormick](https://github.com/splittingred) as a simple search component, and first released on June 2nd, 2010. It is loosely based on AjaxSearch for MODX Evolution by KyleJ/coroico, without the Ajax functionality. +SimpleSearch was written by [Shaun McCormick](https://github.com/splittingred) as a simple search component, and first released on June 2nd, 2010. It is loosely based on AjaxSearch by KyleJ/coroico, without the Ajax functionality. ## Upgrade risks diff --git a/en/extras/socialsuite/socialsuite.getfacebookprofile.md b/en/extras/socialsuite/socialsuite.getfacebookprofile.md index dc86a9aea..72348c81c 100644 --- a/en/extras/socialsuite/socialsuite.getfacebookprofile.md +++ b/en/extras/socialsuite/socialsuite.getfacebookprofile.md @@ -35,7 +35,7 @@ website = https://modx.com/ username = modxcms founded = November 2004 company_overview = MODX is the Content Management System that gives developers, designers and end-users the creative freedom and power to build and maintain websites and online applications with ease. Lose the limitations. There’s no steep learning curve, no cumbersome template language, and no awkward or restrictive structures forced on your site. MODX gives you the freedom to work your way and get things done. -products = MODX Evolution, MODX Revolution +products = MODX Revolution about = MODX CMS is the Content Management System, framework and platform. https://modx.com/ MODX Revolution https://modx.com/download/ talking_about_count = 45 category = Software diff --git a/en/extras/wayfinder/index.md b/en/extras/wayfinder/index.md index 11eb14e0a..c11911a97 100644 --- a/en/extras/wayfinder/index.md +++ b/en/extras/wayfinder/index.md @@ -10,7 +10,7 @@ _Wayfinder's_ primary purpose is to generate navigational menus that automatical Since you can make multiple calls to _Wayfinder_ on a single page, and each call can specify a different section of the document tree, you can have multiple navigational menus or document lists on a single page. For example you may wish to have a main menu at the top of the page, then along the sides have secondary menus for products, services, teams, roles, etc. Each pertaining to a different section of the document tree. -Please note that since the release of Revolution there are two types of Wayfinder snippets available, one for each version. For clarity, this page uses the Evolution syntax when showing examples. Generally speaking the functionality between the two versions are the same, and so are the parameters. Mind that in Revolution, snippets must be called with `[[Wayfinder? &...]]` instead of \[!Wayfinder? &...!\]. +Call Wayfinder with modern tag syntax: `[[Wayfinder? &...]]`. For Wayfinder discussions on the MODX forums see . @@ -27,7 +27,7 @@ _Wayfinder_ has been totally re-factored from the original DropMenu navigation b | 0.9 beta 1/2/3 | Aug/Sept 2006 | 0.9.2.1 | Initial release | | 1.0 | Oct 23, 2006 | 0.9.2.1 | | | 1.0.1 | Nov 07, 2006 | 0.9.2.1 - 0.9.5 | | -| 2.0 | Feb 27, 2007 | 0.9.5 + | Current release for Evolution | +| 2.0 | Feb 27, 2007 | 0.9.5 + | Legacy 1.x release | | 2.1.1 beta 1 | May 21, 2009 | 2.0.0-beta 1 | | | 2.1.1 beta 2 | Oct 20, 2009 | 2.0.0-beta 4 | | | 2.1.1 beta 4 | Nov 05, 2009 | 2.0.0-beta 5 + | | @@ -40,17 +40,7 @@ _Wayfinder_ has been totally re-factored from the original DropMenu navigation b ### Downloads - Download the [latest version of Wayfinder for Revolution](https://modx.com/extras/package/wayfinder) from the [MODX Extras Repository](http://www.modx.com/extras), or install via Package Management. -- Download [version 2.0 for Evolution](http://www.muddydogpaws.com/development/wayfinder/download.html) from MuddyDogPaws. -### Evolution (and before) - -MODX version 0.9.5-1.0 includes Wayfinder by default in the installer. To add Wayfinder to an older version of MODX or to upgrade to a newer version of Wayfinder in **Evolution**: - -1. Download the neccesary files from the link above. -2. Create a new snippet in your MODX Manager (Elements -> Manage Elements -> Snippets) and name if Wayfinder. -3. Copy the contents of snippet.wayfinder.tpl.php to the snippet contents. -4. Create a new folder in your file system under /assets/snippets/ and call it wayfinder. -5. Copy the file wayfinder.inc.php to the new folder. ### Revolution @@ -144,7 +134,7 @@ Available placeholders are: Please note that you will need to wrap the placeholders with the relevant tags. ``` php -Evolution: [+wf._____+] +Older 1.x placeholder style: [+wf._____+] Revolution: [[+wf._____]] ``` @@ -186,7 +176,7 @@ Available placeholders are: Please note that you will need to wrap the placeholders with the relevant tags. ``` php -Evolution: [+wf._____+] +Older 1.x placeholder style: [+wf._____+] Revolution: [[+wf._____]] ``` diff --git a/en/getting-started/faqs-and-troubleshooting.md b/en/getting-started/faqs-and-troubleshooting.md index c7145a1d8..0eaa5eb3d 100644 --- a/en/getting-started/faqs-and-troubleshooting.md +++ b/en/getting-started/faqs-and-troubleshooting.md @@ -17,11 +17,11 @@ Common questions and quick fixes for MODX 3. For deeper troubleshooting, see the ## 1. MODX 101 -### 1.1. What is MODX / MODX Revolution / MODX Evolution? +### 1.1. What is MODX? **MODX** (also called **MODX Revolution**) is the actively developed CMS documented here. Current releases are **3.x**. See [An Overview of MODX](getting-started/what-is-modx) for concepts. -**MODX Evolution** is a separate, older 1.x product line. It is not covered by these 3.x docs. Sites still on Evolution need a migration project; there is no official one-click upgrade path. Historical notes live under [Upgrading from Evolution](getting-started/maintenance/upgrading/evolution). +Older 1.x releases sit outside the scope of these docs. If you are moving from **Revolution 2.x to 3.x**, start with [Upgrading from 2.x to 3.0](getting-started/upgrading-to-3.0). diff --git a/en/getting-started/maintenance/upgrading.md b/en/getting-started/maintenance/upgrading.md index 066f4763a..c92f24eaa 100644 --- a/en/getting-started/maintenance/upgrading.md +++ b/en/getting-started/maintenance/upgrading.md @@ -8,7 +8,6 @@ This document covers the standard process for upgrading an existing MODX Revolut - Upgrading **from 2.x to 3.0+**: read [Upgrading from 2.x to 3.0](getting-started/upgrading-to-3.0) first — namespaces, processors, the fixed core path, and PHP requirements all change. - Confirm your host meets current [Server Requirements](getting-started/server-requirements). **MODX 3.2+ requires PHP 8.1 or higher** (3.0 originally allowed PHP 7.2+). -- Upgrading from Evolution (1.x) is not officially supported; historical notes are [here](getting-started/maintenance/upgrading/evolution). ## Upgrading MODX Revolution @@ -101,4 +100,3 @@ See the note above about FTP clients that support directory merging. 2. [Upgrading from 2.x to 3.0](getting-started/upgrading-to-3.0) 3. [Server Requirements](getting-started/server-requirements) 4. [Upgrading to 2.8.2 / 2.8.3](getting-started/maintenance/upgrading/2.8.2) -5. [Upgrading from MODX Evolution](getting-started/maintenance/upgrading/evolution) diff --git a/en/getting-started/maintenance/upgrading/2.0.0-rc2.md b/en/getting-started/maintenance/upgrading/2.0.0-rc2.md index 7f4fa2736..bae787bf5 100644 --- a/en/getting-started/maintenance/upgrading/2.0.0-rc2.md +++ b/en/getting-started/maintenance/upgrading/2.0.0-rc2.md @@ -33,7 +33,7 @@ There are some real benefits to the new approach: - Cuts down on the size of the core.transport.zip and massively decreases build and setup times. - Much easier development. Just put a 'lexicon/' directory in your root of your Namespace's path (like most current Extras do) and build it in this format: 'lexicon/\[language\]/\[topic\].inc.php'. MODX will automatically parse that directory and browse it in Lexicon Management for you. You no longer need to 'buildLexicon' in your Extra's build scripts. However, this means that **all packages using lexicons will need to be rebuilt for 2.0.0 RC-2**. All that needs to be changed is that they no longer need to call 'modPackageBuilder::buildLexicon' in their build scripts, and their lexicon directories must be under the namespace path with the directory name 'lexicon' (similar to [this component](http://svn.modxcms.com/svn/modx-components/doodles/trunk/)). We apologize for the inconvience, but we promise that you'll find the change much, much easier to develop in. -This also means that we will be packaging in core translations into SVN. All core translations will be committed there, similar to Evolution. +This also means that we will be packaging in core translations into SVN. All core translations will be committed there. ## Plugin Changes diff --git a/en/getting-started/maintenance/upgrading/2.0.5.md b/en/getting-started/maintenance/upgrading/2.0.5.md index 017a3b37a..a9282f6ba 100644 --- a/en/getting-started/maintenance/upgrading/2.0.5.md +++ b/en/getting-started/maintenance/upgrading/2.0.5.md @@ -69,5 +69,3 @@ This should automatically upgrade without you having to adjust it. 3. [Upgrading from 2.0.x to 2.1.x](getting-started/maintenance/upgrading/2.1) 4. [Upgrading from Versions Earlier than 2.0.5](getting-started/maintenance/upgrading/2.0.5) 5. [Upgrading to Revolution 2.0.0-rc-2](getting-started/maintenance/upgrading/2.0.0-rc2) -6. [Upgrading from MODX Evolution](getting-started/maintenance/upgrading/evolution) - 1. [Functional Changes from Evolution](getting-started/maintenance/upgrading/evolution/functional-changes) diff --git a/en/getting-started/maintenance/upgrading/2.1.md b/en/getting-started/maintenance/upgrading/2.1.md index 11873f83a..19840386f 100644 --- a/en/getting-started/maintenance/upgrading/2.1.md +++ b/en/getting-started/maintenance/upgrading/2.1.md @@ -7,6 +7,6 @@ sortorder: 96 Revolution 2.1 saw the removal of much [legacy code](getting-started/maintenance/upgrading/evolution/legacy-removed-2.1) that was marked deprecated in pre-2.0 releases. This is partially responsible for the vast improvements in speed and efficiency across the MODX core in this release. -Many of the most common and popular Extras have been upgraded and tested with 2.1 accordingly. While Extras developers have had a long time to start using the more up-to-date object-oriented API and stop using the old Evolution-style API calls, some Extras may still not work as expected or work at all. As a result it is very important to test your site in a safe environment before deploying to ensure changes in the codebase do not cause problems. +Many of the most common and popular Extras have been upgraded and tested with 2.1 accordingly. While Extras developers have had a long time to adopt the object-oriented API and leave older procedural API calls behind, some Extras may still not work as expected or work at all. As a result it is very important to test your site in a safe environment before deploying to ensure changes in the codebase do not cause problems. Uploading files for an upgrade overwrites all the core files. You can only go back by restoring your backed up files and database. This is why you should test before upgrading your production/live site. diff --git a/en/getting-started/maintenance/upgrading/2.2.md b/en/getting-started/maintenance/upgrading/2.2.md index 0cd780a53..9ef627906 100644 --- a/en/getting-started/maintenance/upgrading/2.2.md +++ b/en/getting-started/maintenance/upgrading/2.2.md @@ -79,5 +79,3 @@ MODX developers and users can now tell specific Elements to pre-process any MODX 3. [Upgrading from 2.0.x to 2.1.x](getting-started/maintenance/upgrading/2.1) 4. [Upgrading from Versions Earlier than 2.0.5](getting-started/maintenance/upgrading/2.0.5) 5. [Upgrading to Revolution 2.0.0-rc-2](getting-started/maintenance/upgrading/2.0.0-rc2) -6. [Upgrading from MODX Evolution](getting-started/maintenance/upgrading/evolution) - 1. [Functional Changes from Evolution](getting-started/maintenance/upgrading/evolution/functional-changes) diff --git a/en/getting-started/maintenance/upgrading/evolution.md b/en/getting-started/maintenance/upgrading/evolution.md index 0de30825d..829057af7 100644 --- a/en/getting-started/maintenance/upgrading/evolution.md +++ b/en/getting-started/maintenance/upgrading/evolution.md @@ -1,39 +1,6 @@ --- -title: "Upgrading from MODX Evolution" -_old_id: "320" +title: "Upgrading from older 1.x releases" _old_uri: "2.x/administering-your-site/upgrading-modx/upgrading-from-modx-evolution" -sortorder: 99 --- -Due to the significant differences in the codebases, tag syntax, and users, upgrading from MODX Evolution to Revolution is more involved process with a number of manual steps. - -It is **strongly recommended that you back up your data prior to performing any upgrade.**. Once you've done so, simply run the upgrade mode in the setup/ program, and your database tables will be upgraded. - -From there, a few things will happen. One, you'll probably notice most of your 3rd party scripts will be broken. You'll need to convert them to the Revolution core, as well as all of your tags to the new [Tag Syntax](building-sites/tag-syntax "Tag Syntax"). Component developers will hopefully already be converting their scripts by this point, so you may be able to find Revolution-compatible scripts via [Package Management](extending-modx/transport-packages "Package Management"), or on [modx.com](https://modx.com/extras/) or in the [forums](https://community.modx.com/). - -Also, it's worth noting that there are no more "web users" or "manager users" - only Users. And the [new permissions scheme](building-sites/client-proofing/security "Security") is vastly different than in 0.9.6/Evolution. - -Again, we don't recommend this, but if you're a \*brave\* soul, feel free to backup and try it. - -An excellent resource on upgrading from Evolution can be found here: - -## Extras Changes from Evolution - -Some Extras in Evolution have been discontinued or are no longer in active development. Below is a list of Evolution Extras and their Revolution equivalents: - -| Evolution | Revolution | -| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Ditto | [getResources](/extras/getresources "getResources"), [getPage](/extras/getpage "getPage"), [tagLister](/extras/taglister "tagLister"), [Archivist](/extras/archivist "Archivist") | -| Jot | [Quip](/extras/quip "Quip") | -| SiteMap | [GoogleSiteMap](/extras/googlesitemap "GoogleSiteMap") | -| MaxiGallery | [Gallery](/extras/gallery "Gallery") | -| eForm | [FormIt](/extras/formit "FormIt") | -| Wayfinder | [Wayfinder](/extras/wayfinder "Wayfinder") | -| DocManager | [Batcher](/extras/batcher "Batcher") | -| AjaxSearch | [SimpleSearch](/extras/simplesearch "SimpleSearch") | -| WebLogin | [Login](/extras/login "Login") | - -## See Also - -- [Functional Changes from Evolution](getting-started/maintenance/upgrading/evolution/functional-changes) -- [Bob's Guide to Upgrading to Revolution](http://bobsguides.com/migrating-revolution.html) +This documentation covers MODX 2.x and 3.x. Migration guides for older 1.x codebases are no longer maintained here. diff --git a/en/getting-started/maintenance/upgrading/evolution/functional-changes.md b/en/getting-started/maintenance/upgrading/evolution/functional-changes.md index 6f70da5ec..cd7ba74fa 100644 --- a/en/getting-started/maintenance/upgrading/evolution/functional-changes.md +++ b/en/getting-started/maintenance/upgrading/evolution/functional-changes.md @@ -1,46 +1,6 @@ --- -title: "Functional Changes from Evolution" -_old_id: "151" +title: "Functional changes from older 1.x releases" _old_uri: "2.x/administering-your-site/upgrading-modx/upgrading-from-modx-evolution/functional-changes-from-evolution" --- -## Changes from MODX Evolution to MODX Revolution - -Much has changed from MODX Evolution in the new Revolution release. This document will attempt to address some of the major ones. - -### Tag Syntax - -Tags have changed their basic syntax. You can view the [Tag Syntax changes here](building-sites/tag-syntax "Tag Syntax"). - -### Parsing Order - -In Evolution, pages were parsed via eval and done as a whole - in Revolution, we implemented "Source Order" parsing. This means tags are parsed in the order that they occur. - -So what does that mean? Well, a few things: - -- _Don't put Snippet calls that assign placeholders at the end of a Resource, or after the Resource._ The placeholders will simply be blank, since the [Snippet](extending-modx/snippets "Snippets") haven't executed yet. -- _Tags can now have tags within their properties._ `[[mySnippet? &tag=`test`[[call]]``]]` is now 100% a-okay. -- \_Using =,?,!,\* is now OK in a Snippet property. - -### No More 5000-Document limit - -Although this has been mostly remedied in later versions of Evolution, there is still a performance hit in those versions. This, caching-wise, has been fixed in Revolution. - -That said, if you're creating a site that has over 10,000 Resources, chances are you're not designing it right. Consider writing custom [Snippets](extending-modx/snippets "Snippets") that pull from custom database tables instead for similar pages (such as inventories or e-commerce). - -### Security - -The access permissions system has been completely rewritten into a new ABAC-based system. You can read more about it [here](building-sites/client-proofing/security "Security"). - -### Error Page vs Unauthorized Page - -This is a change from MODX Evolution. In Revolution, if a web page is protected in the front end so that only logged-in users can see it, the default behavior is for anonymous users to be redirected to the Error (page not found) page rather than the Unauthorized page when they try to access the resource. In Revolution, if Users don't have the "load" permission for a resource, it's as if it doesn't exist — thus the "page not found" response. If you would like them to be sent to the Unauthorized page instead, you can do the following: - -- Create a new Access Policy called "Load" and add a single Permission: Load. -- Create a new Context Access ACL entry for the anonymous User Group with a Context of "web," a Role of "member" and an Access Policy of "Load." - -(credit to [Bob's Guides](http://bobsguides.com/revolution-permissions.html)) - -### FURL Suffixes and Prefixes -> Content Types - -The settings friendly\_url\_prefix and friendly\_url\_suffix are no longer applicable, as Revolution handles those now through [Content Types](building-sites/resources/content-types "Content Types"). +This documentation covers MODX 2.x and 3.x. Notes comparing older 1.x releases are no longer maintained here. diff --git a/en/getting-started/upgrading-to-3.0/breaking-changes.md b/en/getting-started/upgrading-to-3.0/breaking-changes.md index 9062a6d2d..ba5be2307 100644 --- a/en/getting-started/upgrading-to-3.0/breaking-changes.md +++ b/en/getting-started/upgrading-to-3.0/breaking-changes.md @@ -22,7 +22,7 @@ The biggest breaking changes can be summarised as follows: ## Legacy functionality cleanup - `modResource->contentType` field has been removed; that was replaced in Revolution 2.0 with a `content_type` field that maps to a `modContentType` instance. [#14057](https://github.com/modxcms/revolution/pull/14057) -- `modParser095`, `modTranslate095`, and `modTranslator` have been removed. Those were utilities for migrating templates from Evolution syntax. [#14133](https://github.com/modxcms/revolution/pull/14133) +- `modParser095`, `modTranslate095`, and `modTranslator` have been removed. Those were utilities for migrating templates from older 1.x tag syntax. [#14133](https://github.com/modxcms/revolution/pull/14133) - `/manager/min/` directory has been removed; was unused since 2.5. [#12778](https://github.com/modxcms/revolution/pull/12778), [#13194](https://github.com/modxcms/revolution/pull/13194), [#14416](https://github.com/modxcms/revolution/pull/14416) - Unused ExtJS grids have been removed: assets/modext/widgets/resource/modx.grid.resource.security.js, assets/modext/widgets/security/modx.grid.role.user.js, assets/modext/workspace/lexicon/language.grid.js, assets/modext/workspace/lexicon/lexicon.topic.grid.js [#14895](https://github.com/modxcms/revolution/pull/14895) - `@EVAL` binding has been removed from TVs [#13865](https://github.com/modxcms/revolution/pull/13865) diff --git a/en/getting-started/upgrading-to-3.0/system-settings.md b/en/getting-started/upgrading-to-3.0/system-settings.md index 542213b41..27c7b1baf 100644 --- a/en/getting-started/upgrading-to-3.0/system-settings.md +++ b/en/getting-started/upgrading-to-3.0/system-settings.md @@ -10,7 +10,7 @@ MODX 3.0 cleaned up a significant number of old system settings and changed the - `compress_js_max_files`, `manager_js_zlib_output_compression`, `manager_js_cache_file_locking`, `manager_js_cache_max_age`, `manager_js_document_root` which were related to the old dynamic manager js minification [#13859](https://github.com/modxcms/revolution/pull/13859), [#14868](https://github.com/modxcms/revolution/pull/14868) - `editor_css_path` and `editor_css_selectors` have been removed [#14843](https://github.com/modxcms/revolution/pull/14843). These settings may be in by [TinyMCE](https://github.com/modxcms/TinyMCE/issues/30) or other third-party extras which may need to accommodate the setting not being available.) - `manager_language` [#13786](https://github.com/modxcms/revolution/pull/13786), replaced by automatic language detection and on-the-fly switching in the manager [#14046](https://github.com/modxcms/revolution/pull/14046). [Learn more about the manager language in 3.0](getting-started/maintenance/upgrading/3.0/manager-language) -- `resolve_hostnames` and `server_protocol` have been removed [#14877](https://github.com/modxcms/revolution/pull/14877). Deprecated settings from MODX Evolution. +- `resolve_hostnames` and `server_protocol` have been removed [#14877](https://github.com/modxcms/revolution/pull/14877). Deprecated legacy settings. - `upload_flash`, set `upload_files` or `upload_images` or the `allowedFileTypes` on the media source instead. [#14252](https://github.com/modxcms/revolution/pull/14252) - `cache_action_map` as the action map has been removed completely now that modAction is officially gone [#14927](https://github.com/modxcms/revolution/pull/14927) diff --git a/en/index.md b/en/index.md index 63ebf0093..0c34b5675 100644 --- a/en/index.md +++ b/en/index.md @@ -77,9 +77,3 @@ Love MODX? Learn how to get involved in the Community and contribute to the open - [Filing and Discussing Issues](contribute/issues) - [Becoming a Contributor](contribute/code) - [Documentation Style Guide](contribute/documentation/style-guide) - -## What about MODX Evolution? - -Evolution is MODX's classic codebase - the original version released in 2005. [As of April 2017](https://modx.com/blog/evolution-cms-has-a-new-home) Evolution is officially a separate project, no longer under the wings of MODX. That means Evolution has its own leadership, processes, and community. - -All information about Evolution, including documentation and extras, can be found at [evo.im](https://evo.im/). diff --git a/es/getting-started/faqs-and-troubleshooting.md b/es/getting-started/faqs-and-troubleshooting.md index 2a0934456..8712abfe9 100644 --- a/es/getting-started/faqs-and-troubleshooting.md +++ b/es/getting-started/faqs-and-troubleshooting.md @@ -27,23 +27,11 @@ En esta página, encontrarás las siguientes categorías y preguntas: ## 1. MODX 101 -### 1.1. ¿Qué es MODX Evolution y qué es MODX Revolution? ¿Cual es la diferencia? +### 1.1. ¿Qué es MODX? -MODX Evolution es el código heredado en las versiones 1.x. Ha impulsado cientos de miles de sitios web en los últimos cinco años y es lo que ha dado forma a MODX. +MODX es un CMS y framework de aplicaciones de código abierto. Esta documentación cubre MODX 2.x y 3.x (históricamente también llamado Revolution). -MODX Revolution es una reescritura completa de MODX Evolution que comparte las mismas ideas pero se basa en xPDO, una capa de abstracción de base de datos, y finalmente vio la luz del día en 2010. - -En este momento, hay tres tipos de productos MODX : - -- 0.9.6.x – es la base de código original que comenzó con su primera versión de producción/estable como la versión 0.9.0 a finales de octubre del 2005. Ya no es compatible, y REALMENTE debería actualizar a la última versión de Evolution. ¡Las vulnerabilidades en 0.9.6.x han sido reparadas hace mucho tiempo! -- Evolution 1.x – una distribución limpia y refinada de 0.9.6.x con convenciones y terminología más acorde con nuestro totalmente reescrito Revolution. -- Revolution 2.x – una derivación completamente orientada a objetos y completamente nueva que ha estado en desarrollo durante más de 3 años, que aborda las limitaciones encontradas en la base del código original, como tener un analizador verdaderamente recursivo y eliminar el límite máximo de 5,000 documentos. - -Otras lecturas: - -- "La Evolución de una Revolución" -- "¿Cuáles son las diferencias básicas entre Evolución y Revolución?" -- Hay una gran cantidad de temas importantes en los foros, además de discutir evo y revo, que pueden ser interesantes si buscas una discusión más profunda de las diferencias. Dado que Revolution lleva más de tres años en desarrollo, revise la fecha en que se publicó algo para asegurarse de que sigan siendo relevantes. +Las versiones 1.x antiguas quedan fuera del alcance de estos docs. ### 1.2. ¿Qué etiquetas diferentes puedo usar? Que es `[[*pagetitle]]`, `[[Wayfinder]]` etc? @@ -57,7 +45,7 @@ Probablemente la escondiste en algún momento. Hay una flecha sutil en el lado i ### 2.2 ¿Cómo puedo modificar los campos de recursos que son visibles al crear o editar un [Recurso](building-sites/resources "Recurso")? ¿Existe algo como [Administrador del Manager](https://modx.com/extras/package/managermanager) en Revolution? -Puede usar la [Personalización de formularios](building-sites/client-proofing/form-customization "Personalización de Formularios") (que se encuentra bajo el menú de Seguridad) para cambiar los campos. No ofrece todo el complemento ManagerManager (Evolution) pero llega bastante lejos. +Puede usar la [Personalización de formularios](building-sites/client-proofing/form-customization "Personalización de Formularios") (que se encuentra bajo el menú de Seguridad) para cambiar los campos. ### 2.3 ¿Qué significa modDocument/modWeblink/modSymLink/modStaticResource? diff --git a/es/index.md b/es/index.md index 66d2bd76c..757e8394e 100644 --- a/es/index.md +++ b/es/index.md @@ -71,9 +71,3 @@ xPDO es el puente relacional de objetos (ORB) que alimenta MODX. Si sabes lo que - [Presentación y discusión de temas](contribute/issues) - [Convertirse en Colaborador](contribute/code) - [Guía de estilo de documentación](contribute/documentation/style-guide) - -## ¿Qué pasa con MODX Evolution? - -Evolution es la base del código clásico de MODX: la versión original fué lanzada en 2005.. [Desde Abril del 2017](https://modx.com/blog/evolution-cms-has-a-new-home) Evolution es oficialmente un proyecto separado, ya no está bajo las alas de MODX. Eso significa que Evolution tiene su propio liderazgo, procesos y comunidad. - -Toda la información sobre Evolution, incluida la documentación y los extras, se puede encontrar en [evo.im](https://evo.im/). diff --git a/ru/building-sites/settings/tvs_below_content.md b/ru/building-sites/settings/tvs_below_content.md index a556435a5..1e6684a51 100644 --- a/ru/building-sites/settings/tvs_below_content.md +++ b/ru/building-sites/settings/tvs_below_content.md @@ -13,7 +13,7 @@ translation: "building-sites/settings/tvs_below_content" ### Yes -Все TV отображаются под контентом Resource, как и для MODX Evolution. +Все TV отображаются под контентом Resource. ![](tvs_below_content.jpg) diff --git a/ru/building-sites/tag-syntax/output-filters/index.md b/ru/building-sites/tag-syntax/output-filters/index.md index 8f0a18a22..d21ed0203 100644 --- a/ru/building-sites/tag-syntax/output-filters/index.md +++ b/ru/building-sites/tag-syntax/output-filters/index.md @@ -11,7 +11,7 @@ translation: "building-sites/tag-syntax/output-filters" ## Выходной фильтр -В Revolution фильтр вывода применяет один или несколько серий выходных модификаторов, которые ведут себя аналогично вызовам PHx в MODX Evolution - за исключением того, что они встроены в ядро. Синтаксис выглядит так: +Фильтр вывода применяет один или несколько выходных модификаторов, встроенных в ядро. Синтаксис выглядит так: ```php [[element:modifier=`value`]] diff --git a/ru/contribute/issues.md b/ru/contribute/issues.md index e7d7c3d96..a077b06c7 100644 --- a/ru/contribute/issues.md +++ b/ru/contribute/issues.md @@ -71,14 +71,12 @@ Triage это проверка issue на полноту и применимос --- - - Создавайте issues для соответствующего проекта в разделе issues на GitHub: Сообщество может инициировать или помогать с: -- ошибками в MODX (Evolution и Revolution) и некоторыми Extras -- запросами функций для MODX (Evolution и Revolution) и некоторыми Extras +- ошибками в MODX и некоторыми Extras +- запросами функций для MODX и некоторыми Extras - отчётами об ошибках или проблемах с сайтами MODX или их частями Многие feature request и bug report начинаются с обсуждений на форуме. Если вы оформляете issue по теме с форума, приложите ссылку на тему. diff --git a/ru/extending-modx/custom-manager-pages/index.md b/ru/extending-modx/custom-manager-pages/index.md index 03b4a6b7f..8a7ff814b 100644 --- a/ru/extending-modx/custom-manager-pages/index.md +++ b/ru/extending-modx/custom-manager-pages/index.md @@ -9,8 +9,6 @@ CMP расшифровывается как Custom Manager Page, и это пр Если вы как разработчик хотите создать дополнительный компонент, включающий в себя компонент, вы должны следовать [учебному пособию по разработке дополнений для MODX Revolution](extending-modx/tutorials/developing-an-extra), поскольку он проведет вас через все конкретные шаги и терминологию на основе примера пакета, называемого doodles. Эта страница входит в минимальную настройку для пользовательских страниц менеджера. -Эквивалентом CMP или Компонента в MODX Evolution является Модуль, хотя техника, в которой они создаются, совершенно иная. - ## Пространства имен Для CMP требуется пространство имен, чтобы MODX знал, откуда загружать файлы. diff --git a/ru/extending-modx/menus/action-list.md b/ru/extending-modx/menus/action-list.md index e71d2a5e3..2a1dc21a9 100644 --- a/ru/extending-modx/menus/action-list.md +++ b/ru/extending-modx/menus/action-list.md @@ -9,7 +9,7 @@ MODX Revolution использует параметр **a** в массиве `$ В менеджере вы можете получить доступ к списку действий с помощью переменной `MODx.action`. НЕ полагайтесь ни на какой список с идентификаторами действий менеджера, так как эти идентификаторы не жестко закодированы в ядре MODX, а вместо этого они динамически создаются во время установки и просто имеют определенный идентификатор. -В Evolution действительно был фиксированный список, но в Revolution его никогда не было. +В современном MODX фиксированного списка действий менеджера никогда не было. ### До Revolution 2.3 diff --git a/ru/extras/ajaxupload/index.md b/ru/extras/ajaxupload/index.md index c7d1411db..75ecfac5f 100644 --- a/ru/extras/ajaxupload/index.md +++ b/ru/extras/ajaxupload/index.md @@ -19,7 +19,7 @@ description: "динамическая загрузка файлов через ## История и информация -Первоначально AjaxUpload был написан в 2012 году для MODX Evolution и с тех пор поддерживается и развивается [Thomas Jakobi](https://github.com/jako). +AjaxUpload впервые вышел в 2012 году. С тех пор его поддерживает и развивает [Thomas Jakobi](https://github.com/jako). ### Скачать diff --git a/ru/extras/formit/index.md b/ru/extras/formit/index.md index cacdf685e..90e8014c2 100644 --- a/ru/extras/formit/index.md +++ b/ru/extras/formit/index.md @@ -34,7 +34,7 @@ FormIt 3.0 представляет обновление методов шифр ## Как использовать -Просто поместите вызов [Сниппета](building-sites/elements/snippets "Сниппет") FormIt в Ресурс, содержащий форму, которую вы хотите использовать. В отличие от аналогичных предшественников (особенно eForm в MODX Evolution), вы не помещаете форму в Чанк и не ссылаетесь на него в вызове сниппета FormIt: вы буквально помещаете вызов Сниппета рядом с формой, которую хотите обработать. Укажите «hooks» (или сценарии обработки после проверки) в вызове Сниппета. Затем добавьте проверку с помощью параметров `&validate` и `&customValidators`. +Просто поместите вызов [Сниппета](building-sites/elements/snippets "Сниппет") FormIt в Ресурс, содержащий форму, которую вы хотите использовать. Поместите вызов сниппета рядом с формой, которую хотите обработать. Не кладите форму в чанк и не ссылайтесь на этот чанк из вызова FormIt. Укажите «hooks» (или сценарии обработки после проверки) в вызове Сниппета. Затем добавьте проверку с помощью параметров `&validate` и `&customValidators`. Если у вас есть несколько форм на странице, установите для свойства `&submitVar` в вызове Cниппета имя элемента формы (например, &submitVar = `form1-submit`). Это указывает FormIt обрабатывать запросы формы только, если в переданных полях формы (POST) есть эта переменная. Если у вас на одной странице несколько форм, обрабатываемых Formit, следует использовать теги с INPUT type = "submit" name = "form1-submit", элементы button работать не будут. diff --git a/ru/extras/index.md b/ru/extras/index.md index f77c51f3a..6a8eb996b 100644 --- a/ru/extras/index.md +++ b/ru/extras/index.md @@ -103,7 +103,6 @@ sortorder: 5 ### Обновление MODX - [UpgradeMODX](https://bobsguides.com/upgrade-modx-package.html) позволяет обновить MODX Revolution из админки MODX. -- [GoRevo](https://bobsguides.com/why-choose-gorevo.html) (Премиум дополнение от Bob Ray) предоставляет инструмент для перехода с MODX Evolution на MODX Revolution. ## Распространение ваших собственных дополнений diff --git a/ru/getting-started/faqs-and-troubleshooting.md b/ru/getting-started/faqs-and-troubleshooting.md index b4a90c609..0604f5c6a 100644 --- a/ru/getting-started/faqs-and-troubleshooting.md +++ b/ru/getting-started/faqs-and-troubleshooting.md @@ -18,11 +18,11 @@ translation: "getting-started/faqs-and-troubleshooting" ## 1. MODX 101 -### 1.1. Что такое MODX / MODX Revolution / MODX Evolution? +### 1.1. Что такое MODX? **MODX** (также **MODX Revolution**): активно развиваемая CMS, описанная в этой документации. Текущие релизы: **3.x**. Концепции см. в [Обзор MODX](getting-started/what-is-modx). -**MODX Evolution**: отдельная старая ветка 1.x. Эти документы для 3.x её не покрывают. Сайты на Evolution требуют проекта миграции, официального обновления в один клик нет. Исторические заметки: в [Обновление с Evolution](getting-started/maintenance/upgrading/evolution). +Старые релизы 1.x в эту документацию не входят. Если вы переходите с **Revolution 2.x на 3.x**, начните с [Обновление с 2.x до 3.0](getting-started/upgrading-to-3.0). diff --git a/ru/getting-started/maintenance/upgrading.md b/ru/getting-started/maintenance/upgrading.md index c81fec91f..6365dabc5 100644 --- a/ru/getting-started/maintenance/upgrading.md +++ b/ru/getting-started/maintenance/upgrading.md @@ -7,7 +7,6 @@ translation: "getting-started/maintenance/upgrading" - Обновление **с 2.x до 3.0+**: сначала прочитайте [Обновление с 2.x до 3.0](getting-started/upgrading-to-3.0). Меняются пространства имён, процессоры, фиксированный путь к core и требования к PHP. - Убедитесь, что хостинг соответствует актуальным [требованиям к серверу](getting-started/server-requirements). **MODX 3.2+ требует PHP 8.1 или выше** (в 3.0 изначально допускался PHP 7.2+). -- Обновление с Evolution (1.x) официально не поддерживается. Исторические заметки [здесь](getting-started/maintenance/upgrading/evolution). ## Обновление MODX Revolution @@ -100,4 +99,3 @@ cp -fr modx-3.2.0-pl/* /www/public_html/modx 2. [Обновление с 2.x до 3.0](getting-started/upgrading-to-3.0) 3. [Требования к серверу](getting-started/server-requirements) 4. [Обновление до 2.8.2 / 2.8.3](getting-started/maintenance/upgrading/2.8.2) -5. [Обновление с MODX Evolution](getting-started/maintenance/upgrading/evolution) diff --git a/ru/getting-started/maintenance/upgrading/2.0.0-rc2.md b/ru/getting-started/maintenance/upgrading/2.0.0-rc2.md index 2fe2773ee..2075754ea 100644 --- a/ru/getting-started/maintenance/upgrading/2.0.0-rc2.md +++ b/ru/getting-started/maintenance/upgrading/2.0.0-rc2.md @@ -31,7 +31,7 @@ translation: "getting-started/maintenance/upgrading/2.0.0-rc2" - Сокращает размер core.transport.zip и значительно сокращает время сборки и настройки. - Гораздо проще разработка. Просто поместите каталог 'lexicon/' в корень пути вашего пространства имен (как это делают большинство современных дополнений) и постройте его в следующем формате: 'lexicon/\[language\]/\[topic\]. Inc.php'. MODX автоматически проанализирует этот каталог и просмотрит его в Lexicon Management для вас. Вам больше не нужно 'buildLexicon' в сценариях сборки вашего Extra. Однако это означает, что **все пакеты, использующие лексиконы, должны быть перестроены для 2.0.0 RC-2**. Все, что нужно изменить, это то, что им больше не нужно вызывать 'modPackageBuilder::buildLexicon' в своих сценариях сборки, а их каталоги лексикона должны находиться в пути к пространству имен с именем каталога 'lexicon' (аналогично [этому компоненту](http://svn.modxcms.com/svn/modx-components/doodles/trunk/)). Мы приносим свои извинения за неудобства, но мы обещаем, что вы найдете изменения намного, гораздо проще в разработке. -Это также означает, что мы будем упаковывать основные переводы в SVN. Все основные переводы будут совершаться там, как и в Evolution. +Это также означает, что мы будем упаковывать основные переводы в SVN. Все основные переводы будут коммититься туда. ## Изменения в плагине diff --git a/ru/getting-started/maintenance/upgrading/2.0.5.md b/ru/getting-started/maintenance/upgrading/2.0.5.md index 73c336f6a..89b31e33d 100644 --- a/ru/getting-started/maintenance/upgrading/2.0.5.md +++ b/ru/getting-started/maintenance/upgrading/2.0.5.md @@ -71,5 +71,3 @@ And is now: 3. [Обновление с 2.0.x до 2.1.x](getting-started/maintenance/upgrading/2.1) 4. [Обновление с версий ранее 2.0.5](getting-started/maintenance/upgrading/2.0.5) 5. [Обновление до Revolution 2.0.0-rc-2](getting-started/maintenance/upgrading/2.0.0-rc2) -6. [Обновление с MODX Evolution](getting-started/maintenance/upgrading/evolution) - 1. [Функциональные изменения от Evolution](getting-started/maintenance/upgrading/evolution/functional-changes) diff --git a/ru/getting-started/maintenance/upgrading/2.1.md b/ru/getting-started/maintenance/upgrading/2.1.md index 124137643..8750a8e16 100644 --- a/ru/getting-started/maintenance/upgrading/2.1.md +++ b/ru/getting-started/maintenance/upgrading/2.1.md @@ -5,6 +5,6 @@ translation: "getting-started/maintenance/upgrading/2.1" Revolution 2.1 была удалена большая часть [устаревшего кода](getting-started/maintenance/upgrading/evolution/legacy-removed-2.1), которое было помечено как устаревшее в версиях до 2.0. Это частично отвечает за значительные улучшения в скорости и эффективности ядра MODX в этом выпуске. -Многие из наиболее распространенных и популярных дополнений были соответственно обновлены и протестированы до версии 2.1. Хотя у разработчиков Extras было много времени, чтобы начать использовать более современный объектно-ориентированный API и прекратить использование старых вызовов API в стиле Evolution, некоторые Extras могут по-прежнему работать не так, как ожидалось, или вообще работать. В результате очень важно протестировать ваш сайт в безопасной среде перед развертыванием, чтобы убедиться, что изменения в кодовой базе не вызывают проблем. +Многие из наиболее распространенных и популярных дополнений были соответственно обновлены и протестированы до версии 2.1. Хотя у разработчиков Extras было много времени перейти на объектно-ориентированный API и отказаться от старых процедурных вызовов, некоторые Extras могут по-прежнему работать не так, как ожидалось, или не работать вовсе. В результате очень важно протестировать ваш сайт в безопасной среде перед развертыванием, чтобы убедиться, что изменения в кодовой базе не вызывают проблем. При загрузке файлов для обновления все файлы ядра перезаписываются. Вы можете вернуться, только восстановив файлы и базу данных из резервных копий. Вот почему вы должны протестировать перед обновлением рабочего/действующего сайта. diff --git a/ru/getting-started/maintenance/upgrading/2.2.md b/ru/getting-started/maintenance/upgrading/2.2.md index 9a9386800..3c0c26cdf 100644 --- a/ru/getting-started/maintenance/upgrading/2.2.md +++ b/ru/getting-started/maintenance/upgrading/2.2.md @@ -77,5 +77,3 @@ MODX 2.2 представляет «статические» элементы, 3. [Upgrading from 2.0.x to 2.1.x](getting-started/maintenance/upgrading/2.1) 4. [Upgrading from Versions Earlier than 2.0.5](getting-started/maintenance/upgrading/2.0.5) 5. [Upgrading to Revolution 2.0.0-rc-2](getting-started/maintenance/upgrading/2.0.0-rc2) -6. [Upgrading from MODX Evolution](getting-started/maintenance/upgrading/evolution) - 1. [Functional Changes from Evolution](getting-started/maintenance/upgrading/evolution/functional-changes) diff --git a/ru/getting-started/maintenance/upgrading/evolution.md b/ru/getting-started/maintenance/upgrading/evolution.md index bbf46829b..dbe62567d 100644 --- a/ru/getting-started/maintenance/upgrading/evolution.md +++ b/ru/getting-started/maintenance/upgrading/evolution.md @@ -1,37 +1,6 @@ --- -title: "Обновление c MODX Evolution" +title: "Обновление со старых релизов 1.x" translation: "getting-started/maintenance/upgrading/evolution" --- -Из-за значительных различий в кодовой базе, синтаксисе тегов и пользователях, обновление с MODX Evolution до Revolution является более сложным процессом с рядом шагов, выполняемых вручную. - -**Настоятельно рекомендуется создать резервную копию данных перед выполнением любого обновления.**. Как только вы это сделаете, просто запустите обновление **setup/**, и ваши таблицы базы данных будут обновлены. - -Здесь произойдет несколько вещей. Первое - вы вероятно заметите, что большинство ваших сторонних скриптов будут сломаны. Вам нужно будет преобразовать их в ядро Revolution, а также модифицировать все ваши теги в новый [Синтаксис тегов](building-sites/tag-syntax "Синтаксис тегов"). Надеемся, что разработчики компонентов уже преобразуют свои скрипты к этому моменту, поэтому вы сможете найти пакеты, совместимые с Revolution, через [Менеджер пакетов](extending-modx/transport-packages «Менеджер пакетов») или на [modx.com](https://modx.com/extras/) или на [форумах](https://community.modx.com/). - -Также стоит отметить, что больше нет "веб-пользователей" или "пользователей-менеджеров" - только Пользователи. И [новая схема разрешений](building-sites/client-proofing/security "Безопасность (ACLs)") сильно отличается от версии 0.9.6/Evolution. - -Опять же, мы не рекомендуем это делать, но если вы _храбрая_ душа, вы можете сделать резервную копию и попробовать. - -Отличный ресурс по обновлению с Evolution можно найти здесь: - -## Изменения компонентов Evolution - -Некоторые компоненты в Evolution прекратили своё существование или больше не находятся в активной разработке. Ниже приведен список дополнений Evolution и их эквивалентов в Revolution. - -| Evolution | Revolution | -| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Ditto | [getResources](/extras/getresources "getResources"), [getPage](/extras/getpage "getPage"), [tagLister](/extras/taglister "tagLister"), [Archivist](/extras/archivist "Archivist") | -| Jot | [Quip](/extras/quip "Quip") | -| SiteMap | [GoogleSiteMap](/extras/googlesitemap "GoogleSiteMap") | -| MaxiGallery | [Gallery](/extras/gallery "Gallery") | -| eForm | [FormIt](/extras/formit "FormIt") | -| Wayfinder | [Wayfinder](/extras/wayfinder "Wayfinder") | -| DocManager | [Batcher](/extras/batcher "Batcher") | -| AjaxSearch | [SimpleSearch](/extras/simplesearch "SimpleSearch") | -| WebLogin | [Login](/extras/login "Login") | - -## Смотри также - -- [Функциональные изменения после Evolution](getting-started/maintenance/upgrading/evolution/functional-changes) -- [Руководство Боба Рэя по обновлению до Revolution](https://bobsguides.com/migrating-revolution.html) +Эта документация описывает MODX 2.x и 3.x. Гайды по миграции со старых релизов 1.x здесь больше не поддерживаются. diff --git a/ru/getting-started/maintenance/upgrading/evolution/functional-changes.md b/ru/getting-started/maintenance/upgrading/evolution/functional-changes.md index a3f90cdac..3b62a997c 100644 --- a/ru/getting-started/maintenance/upgrading/evolution/functional-changes.md +++ b/ru/getting-started/maintenance/upgrading/evolution/functional-changes.md @@ -1,45 +1,6 @@ --- -title: "Функциональные изменения от Evolution" +title: "Функциональные изменения относительно старых релизов 1.x" translation: "getting-started/maintenance/upgrading/evolution/functional-changes" --- -## Переход от MODX Evolution к MODX Revolution - -Многое изменилось с MODX Evolution в новой версии Revolution. Этот документ попытается обратиться к некоторым из основных. - -### Синтаксис тегов - -Теги изменили свой основной синтаксис. Вы можете просмотреть [Изменения синтаксиса тегов здесь](building-sites/tag-syntax "Синтаксис тегов"). - -### Порядок разбора - -В Evolution страницы были разобраны с помощью eval и выполнены в целом - в Revolution мы реализовали разбор «Source Order». Это означает, что теги анализируются в порядке их появления. - -Так что это значит? Ну и несколько вещей: - -- _Не размещайте вызовы Сниппетов, которые назначают плейсхолдеры в конце ресурса или после ресурса._ Плейсхолдеры будут просто пустыми, так как [Сниппеты](extending-modx/snippets "Сниппеты") еще не выполнены. -- _Теги теперь могут иметь теги в своих свойствах._ `[[mySnippet? &tag=`test`[[call]]``]]` сейчас на 100% хорошо. -- \_С помощью =,?,!,\* теперь все ОК в свойстве сниппета. - -### Лимит не более 5000 документов - -Хотя это было в основном исправлено в более поздних версиях Evolution, в этих версиях все еще наблюдается снижение производительности. С точки зрения кэширования, это было исправлено в Revolution. - -Тем не менее, если вы создаете сайт с более чем 10000 ресурсов, скорее всего, вы не разрабатываете его правильно. Рассмотрите возможность написания пользовательских [Сниппетов](extending-modx/snippets "Сниппеты") которые извлекают из пользовательских таблиц базы данных, а не для похожих страниц (например, из электронной коммерции). - -### Безопасность - -Система разрешений доступа была полностью переписана в новую систему на основе ABAC. Вы можете прочитать больше об этом [здесь](building-sites/client-proofing/security "Безопасность"). - -### Страница ошибок против неавторизованной страницы - -Это изменение от MODX Evolution. В Revolution, если веб-страница защищена во внешнем интерфейсе, так что ее могут видеть только зарегистрированные пользователи, по умолчанию анонимные пользователи перенаправляются на страницу «Ошибка (страница не найдена)», а не на страницу неавторизованного пользователя, когда они попробуйте получить доступ к ресурсу. В Revolution, если у пользователей нет разрешения «загрузить» для ресурса, он как бы не существует - таким образом, отклик «страница не найдена». Если вы хотите, чтобы они были отправлены на страницу неавторизованных пользователей, вы можете сделать следующее: - -- Создайте новую Политику доступа под названием «Загрузка» и добавьте одно Разрешение: Загрузка. -- Создайте новую запись ACL для доступа к контексту для анонимной группы пользователей с контекстом «web», ролью «member» и политикой доступа «Load». - -(спасибо [Руководству Боба](http://bobsguides.com/revolution-permissions.html)) - -### Суффиксы и префиксы FURL -> Типы контента - -Настройки `friendly_url_prefix` и `friendly_url_suffix` больше не применимы, так как Revolution обрабатывает их теперь через [Типы контента](building-sites/resources/content-types "Типы контента"). +Эта документация описывает MODX 2.x и 3.x. Сравнения со старыми релизами 1.x здесь больше не поддерживаются. diff --git a/ru/getting-started/upgrading-to-3.0/breaking-changes.md b/ru/getting-started/upgrading-to-3.0/breaking-changes.md index db88866f6..fa77657d5 100644 --- a/ru/getting-started/upgrading-to-3.0/breaking-changes.md +++ b/ru/getting-started/upgrading-to-3.0/breaking-changes.md @@ -22,7 +22,7 @@ translation: "getting-started/upgrading-to-3.0/breaking-changes" ## Очистка устаревшего функционала - Поле `modResource->contentType` удалено. В Revolution 2.0 его заменило поле `content_type`, которое ссылается на экземпляр `modContentType`. [#14057](https://github.com/modxcms/revolution/pull/14057) -- `modParser095`, `modTranslate095` и `modTranslator` удалены. Это утилиты для переноса шаблонов из синтаксиса Evolution. [#14133](https://github.com/modxcms/revolution/pull/14133) +- `modParser095`, `modTranslate095` и `modTranslator` удалены. Это утилиты для переноса шаблонов из старого синтаксиса 1.x. [#14133](https://github.com/modxcms/revolution/pull/14133) - Каталог `/manager/min/` удалён. Не использовался с 2.5. [#12778](https://github.com/modxcms/revolution/pull/12778), [#13194](https://github.com/modxcms/revolution/pull/13194), [#14416](https://github.com/modxcms/revolution/pull/14416) - Удалены неиспользуемые сетки ExtJS: assets/modext/widgets/resource/modx.grid.resource.security.js, assets/modext/widgets/security/modx.grid.role.user.js, assets/modext/workspace/lexicon/language.grid.js, assets/modext/workspace/lexicon/lexicon.topic.grid.js [#14895](https://github.com/modxcms/revolution/pull/14895) - Привязка `@EVAL` удалена у TV [#13865](https://github.com/modxcms/revolution/pull/13865) diff --git a/ru/getting-started/upgrading-to-3.0/system-settings.md b/ru/getting-started/upgrading-to-3.0/system-settings.md index f005d2433..07e928207 100644 --- a/ru/getting-started/upgrading-to-3.0/system-settings.md +++ b/ru/getting-started/upgrading-to-3.0/system-settings.md @@ -11,7 +11,7 @@ MODX 3.0 очистил значительное количество стары - `compress_js_max_files`, `manager_js_zlib_output_compression`, `manager_js_cache_file_locking`, `manager_js_cache_max_age`, `manager_js_document_root` что связано со старым динамическим менеджером JS minification [#13859](https://github.com/modxcms/revolution/pull/13859), [#14868](https://github.com/modxcms/revolution/pull/14868) - `editor_css_path` и `editor_css_selectors` был удален [#14843](https://github.com/modxcms/revolution/pull/14843). Эти настройки могут быть в [TinyMCE](https://github.com/modxcms/TinyMCE/issues/30) или других сторонних дополнениях, которые могут потребоваться для настройки недоступных настроек.) - `manager_language` [#13786](https://github.com/modxcms/revolution/pull/13786), заменено автоматическое определение языка и переключение на лету в менеджере [#14046](https://github.com/modxcms/revolution/pull/14046). [Узнайте больше о языке менеджера в 3.0](getting-started/upgrading-to-3.0/manager-language) -- `resolve_hostnames` и `server_protocol` были удалены [#14877](https://github.com/modxcms/revolution/pull/14877). Устаревшие настройки из MODX Evolution. +- `resolve_hostnames` и `server_protocol` были удалены [#14877](https://github.com/modxcms/revolution/pull/14877). Устаревшие legacy-настройки. - `upload_flash`, установите `upload_files` или `upload_images` или `allowedFileTypes` вместо медиа источника. [#14252](https://github.com/modxcms/revolution/pull/14252) - `cache_action_map` поскольку карта действий была полностью удалена, теперь официально исчезло modAction [#14927](https://github.com/modxcms/revolution/pull/14927) diff --git a/ru/index.md b/ru/index.md index 762b22a0e..fb3bdfc06 100644 --- a/ru/index.md +++ b/ru/index.md @@ -75,9 +75,3 @@ xPDO - это объектно-реляционный мост (ORB), котор - [Подача и обсуждение вопросов](contribute/issues) - [Стать участником](contribute/code) - [Руководство по стилю документации](contribute/documentation/style-guide) - -## А как насчет MODX Evolution? - -Evolution - это классическая кодовая база MODX - оригинальная версия, выпущенная в 2005 году. [По состоянию на апрель 2017 года](https://modx.com/blog/evolution-cms-has-a-new-home) Официально Evolution - это отдельный проект, уже не под крылом MODX. Это означает, что у Evolution есть собственное руководство, процессы и сообщество. - -Всю информацию о Evolution, включая документацию и дополнительные материалы, можно найти по адресу [evo.im](https://evo.im/).