Modx revo — установка системы

Troubleshooting / Errors

In progress… trying to document problems and solutions…

Setup Errors

You may encounter problems when re-running Setup on the new server. Sometimes re-running setup fails, but copying the files and database ends up with a working site. Remember: re-running setup is only necessary if you have loose-ends somewhere that broke during the transfer.

Class xPDODriver_ not found

This manifests itself as an error message like the following:

This is usually a sign that your configuration file got mangled. Re-open your core/config/config.inc.php and verify that its contents are in place. A mangled config file contains placeholders instead of values.

Installation Summary shows Incomplete Items

This can be a bad omen: the Installation Summary page does not describe messages. This can be a sign that permissions are not correct somewhere.

When that page is working correctly, you should see messages next to each «Ok»:

Check your Database Encoding

It can be hugely problematic if your database on one server does not use the same encoding as the new server. Things like single-quotes etc. will get broken, and in some cases, you might even get a 500 error when trying to view your site.

See Also

Mac OS X Users

If you’re copying the extracted folder in Mac OS X, be careful, as OS X will «replace» folders when you drag and drop them over each other. Make sure that you use the «ditto» command from the command line, rather than drag/dropping from Finder, otherwise your core/config/config.inc.php file will be erased. A sample ditto command after you’ve extracted the zip could be:

The effect is the same if you use the humble cp command:

The «-fr» bit forces a recursive copy (i.e. a directory merge). Using a backslash before the «cp» command lets you avoid all the prompts asking «Are you sure?» to every overwrite operation.

See the note above about FTP clients that support directory merging.

Related Articles

  1. Troubleshooting Upgrades
  2. Upgrading to 2.2.x
  3. Upgrading from 2.0.x to 2.1.x
  4. Upgrading from Versions Earlier than 2.0.5
  5. Upgrading to Revolution 2.0.0-rc-2
  6. Upgrading from MODX Evolution
  7. Functional Changes from Evolution

История MODX

История создания системы управления содержимым под названием MODX начинается в 2004 году. В тот год MODx стал первым серьезным модулем для поддержки DocVar, работающим на системе управления Etomite 6. Разработчиками, работавшими над проектом, были Реймонд Ирвинг (Raymond Irving) и Райан Треш (Ryan Thrash).

Но вскоре разработчики Etomite отказались от развития своей CMS как открытого продукта, и весной 2005 г. авторы MODX сделали форк системы. С того момента она стала развиваться в виде самостоятельного продукта.

В 2010 году происходит «революция», и на свет появляется совершенно новый MODX – MODX Revolution.

Installation Instructions

Step 2: Set up the MIGX Configurator Custom Manager Page (CMP) and Package Manager

Since Version 2.8 this steps (1-19) are not longer needed.

Note: It would be prudent to create a snapshot of your MODX database before setup as this process will change your database structure.

  • Open the «System» menu from within the Revolution Manager
  • Click the «Actions» menu item
  • Find the MIGX category from the list of actions on left. Right click on it.
  • Click «Create Action Here»
  • Type «index» for controller
  • Ensure «migx» is selected for the namespace
  • Select «No Action» for the parent controller
  • Click «Save»
  • Refresh the page
  • Find the Components category from the list of top menu items on the right. Right click on it.
  • Click «Place Action Here»
    • Lexicon Key: migx
    • Description: Configurator and Package Manager
    • Action: migx — index (there are multiple pages sorted alphabetically. Make sure you go past all the core actions)
    • Icon: (leave blank)
    • Parameters: &configs=packagemanager||migxconfigs||setup
    • Handler: (leave blank)
    • Permissions: (leave blank)
  • Click «save»
  • Refresh the page
  • Open the «Components» menu
  • Click the new MIGX Action item you created.
  • Click the Setup / Upgrade tab
  • WARNING: Before this next step, you probably want to ensure that you’ve created a snapshot of your database.
  • Click the Setup button
  • Done!

Что такое MODX шаблоны?

MODX шаблоны это простые HTML/CSS шаблоны с тегами MODX внутри для динамичной функциональности. Это очень упрощенное определение, но в моей голове сложилось именно такое определения для MODX шаблона. Если вы знаете как программировать HTML/CSS или можете разобраться в таком коде, то остальное для вас не будет проблемой. Вот что делает MODX  очень удобным для дизайнера.

Для этого урока я решил использовать тему студии Themeforest для своего сайта. Если вы хотите следовать точно моим шагам, то можете взять этот же шаблон или же взять другой шаблон, вашу собственную разработку либо скачанный с другого ресурса (в Google поищите ‘бесплатные css шаблоны’). Порядок действий для разработки шаблона будет аналогичным.

В этом уроке я буду использовать 7 in 1 Business Success Site шаблон потому что он имеет отличный вид и в то же время достаточно сложный, чтобы его было интересно портировать в сайт MODX . В комплекте 7 различных цветовых стиля, я буду использовать синий, а вы выбирайте какой вам нравится. Ну что ж начнем!

Первое, что я хочу отметить: способ построения шаблона показанный в этом уроке — это не единственный или единственноверный способ, это просто один из способов, которые я использую. MODX не ограничивает ни в том куда положить файлы или как разбивать шаблон… Как вам удобно, так вы и делайте ваш шаблон или как удобно вашему клиенту. Поэтому держите это в уме и можете отступать в порядке построения и изобретать свои более оптимальные способы, как говорится — делай как я, делай лучше меня.

Troubleshooting

Nothing Happens

Before you go banging your head on a wall, have you checked to make sure that this extra is actually installed on your site?

Array of Attributes is Dumped

You forgot to include the parameter. Without the parameter, the Snippet will retrieve the specified resources, but you didn’t tell it how to format them. Be sure you include the parameter in your Snippet call, e.g.

Or, perhaps you misspelled the chunk name. Perhaps you DO have a specified, but does that chunk actually exist? If you name a chunk that does not exist, getResources will not know how to format your results.

Or, even though you have correctly specified the parameter, you may have inadvertently forgotten the ampersand on one of your _other_parameters. E.g.

will cause the Snippet call to fail and the attributes to be dumped. The correct format should be

The Content isn’t There

You are retrieving the correct resources and you are seeing _some_of the results formatting correctly, but your placeholders don’t contain anything. What’s going on? You must include the &includeContent= argument to get the content.

Caching problems using tpl, tpl_N, tpl_nN, tplFirst, tplLast or tplOdd

If you are using this parameters you may have thought about reusing your tpl chunk to avoid repeating code. For example:

Generic Tpl Chunk:

Fourth Tpl Chunk ( tpl_nN):

If you have problems with this, having blank or strange results, is due to MODX caching. Calling the chunk uncached won’t work. You have to use a trick: a dummy tag when calling the generic chunk.

Note: You don’t need to call the chunk uncached.

Seen at: http://forums.modx.com/thread/43748/chunk-inside-getresources-template-not-processed-correctly

Step-by-step

Downloading Packages

You have a few options: you can download remotely via the Provider option, by selecting the modx.com provider from the menu (or just by clicking ‘Download Extras’ in the grid toolbar).

To download the packages, simply select the package you wish to download and click the «Download» button.

Or, packages can be downloaded directly from a browser via MODX’s Extras section, located at https://modx.com/extras/. The package zips are loaded simply by uploading them to your core/packages/ directory, and then running the Package Management section of the manager. From there, click on «Add New Package», and select the «Search Locally for Packages» option. MODX will then scan the core package directory, and add any packages you have.

Downloading Packages requires you to either have cURL or sockets installed on your web server. If you do not have these installed, the list of packages will show blank.

The Official Provider of modx.com has a URL of:
http://rest.modx.com/extras/
and comes packaged in with MODX Revolution 2.0.0.

Installing Packages

You can easily install packages by right-clicking on the package and clicking «Install». A console will load showing you the details of the package installation.

If the package should have a License Agreement, you’ll need to agree to it before you can proceed. Also, the package might provide a README file for you to purvey before installing.

Finally, the package may or may not have some pre-install options and settings for you to set, such as:

The package should then install on your MODX installation.

Updating Packages

You can easily update any package that has been downloaded from a provider. Simply click the ‘Check for Updates’ context menu item (after right-clicking on the package), and MODX will load a window showing any newer versions. Should your package be already up-to-date, a message will appear.

You can then select the version you would like to install, and MODX will download the package and start the install process.

Now, if you want to revert back, you’ll simply uninstall the package, and click the ‘Revert’ option, which will revert back to the prior package that was installed.

Uninstalling Packages

You can click on any package to either remove or uninstall a package. Removing a package removes the zip file entirely from your core/packages directory. Uninstall simply uninstalls it.

Note the three modes when you uninstall a package:

Pre-Installation Checks

MODX will then proceed with a list of checks to verify that your system is ready for installing. If any of these fail, you’ll need to proceed with the directions that it suggests to make sure your environment meets the Server Requirements and has the correct directories writable.

Once you’re ready, and all the checks pass, click ‘Install’ to proceed.

If you get a blank screen or cannot proceed after clicking ‘Install’, verify these steps:

  1. Make sure the directories «/», «/core/config», «/core/packages»,»/core/cache», and «/core/export» are writable. (root will be the actual directory you are installing to.)
  2. Make sure your php.ini setting sets memory_limit to 128M, and max_execution_time to 120
  3. Ensure that MODX can create the manager and connectors directories; this is done by making the parents of those directories writable (since you can change where they are installed)
  4. Post a message in the Revolution forum regarding your issue. State your server setup and installation info, and we’ll try and help you find a solution.

Evolution CMS 1.4.0

For half a year, a lot of work has been done (more than 600 commits), so this is the second major release of Evolution CMS. The first one can be read here (https://github.com/evolution-cms/evolution/releases/tag/1.3.0). The main emphasis of this release is stability of the system, as well as updating and replacing old snippets by new ones. So it is possible now to create sites even faster, as well increasing the performance of already existing sites. One main reason for better performance is DocLister, the replacement for Ditto.

Most important facts:

  • Demo Site has been updated, all old components have been replaced by new ones, while old components are still available in the extras-repository, but are not recommended for use.
  • Ditto -> DocLister
  • Wayfinder -> DLMenu
  • Breadcrumbs -> DLCrumbs
  • Eform -> FormLister
  • WebLogin -> FormLister
  • WebChangePwd -> FormLister
  • WebSignup -> FormLister
  • Added DLSitemap
  • AjaxSearch moved to Extras
  • FirstChildRedirect moved to Extras
  • Jot moved to Extras
  • MemberCheck moved to Extras
  • Personalize moved to Extras
  • Reflect moved to Extras
  • UltimateParent moved to Extras
  • Upgraded phpMailer to 6.0.3
  • New feature «Global tabs»
  • Grinding TV
  • Widget changes the color scheme of the admin area, the button is fullscreen and creates a new document in the menu
  • Modifiers disabled by default
  • At-Syntax (@-syntax) disabled by default
  • New
  • Custom Placeholders get replaced before TVs — allows {{chunk? &param=}} with ] as content inside (useful in conjunction with YAMS)
  • added CSS-minify to manager theme
  • Fixed popup window from the context menu. Closing a popup window when «saving» or button press «cancel». Hot keys: Esc->Close, Ctrl+S -> Save, Ctrl+Q -> Save and quit (if focus is in codeMirror editor)
  • friendly_url_suffix = / and aliaslistingfolder
  • fixed special chars in passwords via htmlspecialchars()

Upgrade to version 1.4

In order to correctly update from older versions and also exclude the possibility, that there are unnecessary files and security problems left on the site, do the following:

  1. Do Backup files and DB
  2. Update to version 1.3.6 — it includes all the old add-ons that were removed in 1.4.0, it provides the opportunity to update all add-ons such as Ditto, EForm, WebLogin
  3. Delete all the old admin themes (manager / media / style), except «default» and «common»
  4. Delete the file index-ajax.php — it was used only for AjaxSearch prior to version 1.0.10, leave if you use it for other purposes and you know what you are doing.
  5. As well as to remove garbage to the maximum, you need to delete the manager folder after making a backup of the file , then copy files from version 1.4.0
  6. We strongly recommend that you remove all unused old snippets such as: Ditto, Wayfinder, Eform, Breadcrumbs, WebLogin, WebChangePwd, WebSignup
  7. There is a problem when updating the ManagerManager plug-in from older versions, to solve the problem delete the managermanager folder and install/copy latest version
  8. TinyMCE3: It is also recommended to disable and delete all its files if you do not use it.
  9. If you use Modifiers and/or @-syntax then check in the settings if they are enabled. By default in 1.4 these options are disabled.

Replacing old snippets with new ones

  1. As an example, you can install Evo with a demo site, which is already using new snippets.
  2. To migrate from Ditto to DocLister, the following examples will help:
  • https://github.com/Nicola1971/Doclister-Tags-in-Ditto-Style
  • https://github.com/Nicola1971/Ditto-to-DocLister-Reference-Tables
  1. To migrate from Wayfinder to DLMenu

http://docs.evo.im/en/03_extras/dlmenu.html

  1. To migrate from BreadCrumbs to DLCrumbs
  2. To migrate from Eform, WebLogin to FormLister

Where to find Extras

The official source of extras is MODX.com. You can browse hundreds of (free) extras and every installation of MODX is already configured to download and install extras from MODX.com through the package manager.

There are also third-party sources and marketplaces available, which typically offer a combination of free and premium extras. These include:

Name # of extras Support
modx.com/extras/ Over 800 add-ons Community forum
modstore.pro (Russian) 100+ (EN), 300+ (RU) Community forum, and private ticketing for premium extras
modmore.com 20+ Community forum and email support for premium extras
extras.io 5 Email support for premium extras
bobsguides.com 47 Email support for Bob Ray’s extras

To use third party extra providers, you’ll usually need to create an account in order to access their Package Provider. You can find more information on how to do that in the documentation for each of the mentioned vendors.

Commonly used Extras

With almost 1000 extras available, it can be hard when getting started to determine which extras you should use. The extras in the following list are considered an excellent choice depending on your project requirements.

This does not mean however that these are your only options. Browse the repository, read the forums, and share interesting extras that you find with the community.

Navigation and content

  • pdoTools is a collection of useful snippets that aims to be a modern (and mostly drop-in) replacement for older (but still supported) extras:
    • pdoResources is the equivalent of getResources, which can be used to list resources. These can also be used for RSS feed or Sitemap generation.
    • pdoMenu is the equivalent of Wayfinder, which is used for generating (multi-level) menus from your resource tree.
    • pdoPage is the equivalent of getPage, which wraps snippets like getResources/pdoResources with pagination capabilities
    • pdoCrumbs can be used in a similar way to Breadcrumbs to create a breadcrumbs trail of the current resource.
  • getResourceField, pdoField or fastField retrieve a single resource field.
  • AdvSearch or mSearch2 (premium extra from modstore) adds a search function to your site
  • Collections is used for large quantities of resources, such as blogs or product listings, and will list child resources in a grid instead of the tree
  • NewsPublisher allows users to create resources in the front-end without needing access to the MODX Manager (includes rich text editing and file/image browser).

Rich text/code editing

  • TinyMCE RTE is a rich text editor based on TinyMCE 4. (The package called simply TinyMCE uses the older TinyMCE 3)
  • TinymceWrapper is a TinyMCE implementation using the latest version from CDN.
  • Redactor (premium extra by modmore) is a MODX integration of Redactor.
  • CKEditor integrates the CKEditor RTE into MODX.
  • Ace enables code-editing on your elements in the manager.

Media

  • Gallery can be used to add image albums to your site
  • MoreGallery (premium extra by modmore) for managing image and video (YouTube/Vimeo) galleries, implemented as a special resource type

Forms

  • FormIt is the standard in handling form submissions
  • Formalicious (premium extra available from modmore and modstore) is a form builder based on FormIt
  • SPForm simple, spam-proof contact form

Multi-site, multi-lingual, multi-domain, contexts

  • xRouting is a flexible context router that supports (sub)domains and directories with minimal configuration
  • LangRouter is a context router that chooses the context based on the visitors’ language
  • Babel is used to connect translations in different contexts

E-commerce

  • MiniShop2 is a powerful open source ecommerce solution, with many (paid and free) extensions predominantly available from modstore
  • Commerce is a powerful premium ecommerce solution from modmore
  • SimpleCart is a simpler premium ecommerce solution, originally built by OostDesign, now available from modmore

Users

  • Login is a suite of tools to help you integrate front-end user functionality, including login and profiles.
  • HybridAuth can be used to let users login through social services
  • Personalize can show different chunks depending on if a user is logged in or not

Blogging

  • Collections to list child resources in a grid in the manager (instead of in the resource tree)
  • Quip or Tickets to add commenting functionality
  • Tagger to add tags you can filter and search posts by

Versioning & Workflow

  • VersionX keeps a copy of changes to your resources and elements for an easy restore.
  • Preview and Workflow (premium extras from Extras.io) provide previews and publishing workflows.
  • MagicPreview (free extra from modmore) gives you a preview button that allows you to see your resource changes, without the changes having to be saved.
  • StageCoach allows staging of page changes so they will be applied at a future date.

Development tools

  • modDevTools adds additional functionality to the manager to help developers building sites.
  • MyComponent is a complete development environment for creating MODX extras.

Updrading MODX

  • UpgradeMODX allows you to upgrade MODX Revolution from within the MODX Manager.
  • GoRevo (premium extra from Bob Ray) provides a tool for migrating from MODX Evolution to MODX Revolution.

Plugin Examples

Plugins can be used for a variety of different applications, below are a couple of examples:

Message the User

Description: Send a custom message to the user as they create/edit a page… a custom header.
System Events: OnDocFormPrerender

Custom Validation

Description: Do some custom validation on saving a page resource
System Events: OnBeforeDocFormSave

The trick here is that what you want to message the user has to be passed to the $modx->event->output() function; any text you want to write to the logs can simply be returned by the plugin. If you pass validation, simply return null.

No HTML Allowed
The output you set in $modx->event->output() must not contain any HTML! Use plain text only! This is because the message is passed to the user via a Javascript modal window.

Return value must be a string. If your return value will be a number, concatenate it with an empty string.

Page-Not-Found Redirector

Description: Redirects a user to selected document and sends a message
System Events: OnPageNotFound
System Settings:

  • pnf.page: Error Resource ID
  • pnf.mailto: Mail To Address
  • pnf.mailfrom: Mail From Address

Examples

Also see the Examples sub section of this documentation for more detailed examples and tutorials.

Output a list of child Resources of the current Resource, using the ‘myRowTpl’ chunk:

Output all resources beneath the Resource with ID ‘5’, with the exception of resource 10, using the ‘myRowTpl’ chunk:

Output only the resources specified, using the ‘myRowTpl’ chunk:

Output the top 5 latest published Resources beneath the Resource with ID ‘5’, with tpl ‘blogPost’:

Output a list of child Resources of the current Resource, based on the Resource-template:

Output a list of child Resources of the current Resource, where the Resource-template ID is 1 or 2:

Output a list of child Resources of the current Resource, where the Resource-template ID is 1, 2 or 3 (you cannot use the same key name more than once):

Display a message when no results found (equivalent of «empty» parameter in Ditto):

Example using an inline Tpl

Wrapping a getResources result in other markup (like an &outerTpl property, which doesn’t exist for getResources from version 1.6.0 you can still do it like that or use the &tplWrapper property).

Final thoughts

It would be wise to keep backups from the old server until the new site has undergone a couple of backup generations and everything has been verified.

If you run into trouble after successfully running Setup, try manually deleting all files in the core/cache directory and clearing your browser cache and cookies.

Your site should now be up and running in its new location!

Final Checkup
It’s common for there to be problems during a site migration. There is a script available that will run tests on your MODX site to ensure that the configuration file is configured correctly. See the test_config.php script available as one of the MODX utility scripts here: https://github.com/craftsmancoding/modx_utils. It is quite old and since MODX 2.5.x some connectors don’t exists anymore. If you need a better supported check, you could try the commercial SiteCheck package.

Загрузка файлов шаблона

Любой шаблон содержит в себе много файлов – css файлов, яваскрипт, рисунков, флеш файлов… Все это нужно где-то хранить на вашем сервере, чтобы ваш шаблон имел к этим файлам доступ. Я предпочитаю хранить все файлы, которые относятся к шаблону в середине директории assets. Вы можете положить куда угодно и установить соответствующие пути в вашем шаблоне.

Распакованные файлы шаблона имеют приблизительно вот такую файловую структуру:

Таким образом 1 шагом в нашей разработке шаблона является копирование трех папок с файлами шаблона на сервер, это папки sample-data/, scripts/ и styles/. Я создал папку в середине assets и назвал ее templates, а также я создал папку 7in1, в которую поместил вышеназванные папки с файлами шаблона. Если вы запутались, то посмотрите на картинку и все станет понятно:

Теперь эти файлы доступны для любого шаблона, который вы будете делать.

Updating your Extras settings

Some extras, such as Gallery, store information on where certain files can be found in their own settings. To take Gallery as the example, it stores the path to its assets, core, files and phpthumb folders on the filesystem. Depending on your setup these will change when moving and in order to keep using these addons you will need to update those paths. While every addon can decide for itself where to store paths, one of the popular locations is in the system settings.

Go to System -> System Settings in your manager, and find the namespaces dropdown, as seen on the image to the right (click to enlarge). Open it and look for the extra of your choice, for instance Gallery. Not all extras specify system settings but most of them will show up on the list anyway. Now that you have found where these paths are stored you can update them to reflect the new location.

If you are using MODX Revolution 2.2, you may also need to check the extension_packages system setting (found under the System & Server area in the System Settings). This setting is used for custom resource classes (such as the Articles addon) and defines the path to its model — this may need to be updated after moving your site.

Параметры базы данных

В следующем окне вы увидите форму с запросом информации о вашей базе данных:

Вы можете создать свою базу данных и пользователя до этого шага. Убедитесь, что пользователь вашей базы данных связан с новой базой данных, и ему предоставлено разрешение на все привилегии для этой базы данных.

  • Добавьте название сервера базы данных, которое является URL-адресом, по которому находится ваша база данных. Для большинства пользователей это будет ‘localhost’.
  • Введите имя пользователя вашей базы данных. На некоторых хостах вашему имени пользователя базы данных предшествует название каталога владельца сайта, например . В этом случае необходимо ввести полное название базы данных. Зайдите в раздел управления базами данных хостинга или проверьте саму базу данных, если такой префикс имеется.
  • Ваше имя пользователя также может иметь префикс с тем же именем каталога владельца сайта. Если это так, нужно указать этот префикс перед вашим именем пользователя, то есть .
  • Введите ваш пароль.
  • В данной форме, если вы хотите, вы можете указать другой префикс таблиц базы данных. Все таблицы во время установки MODX будут созданы с данным префиксом — это полезно, если вы хотите сделать несколько установок MODX в одной базе данных.
  • По завершении нажмите ссылку ‘Проверить соединение с сервером базы данных и отобразить список доступных сопоставлений’. Если у вас есть какие-либо ошибки, они будут показаны ниже. При наличии ошибок, проверьте правильность имени пользователя и пароля вашей базы данных. Кроме того, если у вашего пользователя нет доступа к созданию базы данных, вам может потребоваться сделать это вручную.

Where to find Extras

The official source of extras is MODX.com. You can browse hundreds of (free) extras and every installation of MODX is already configured to download and install extras from MODX.com through the package manager.

There are also third-party sources and marketplaces available, which typically offer a combination of free and premium extras. These include:

Name # of extras Support
modx.com/extras/ Over 800 add-ons Community forum
modstore.pro (Russian) 100+ (EN), 300+ (RU) Community forum, and private ticketing for premium extras
modmore.com 20+ Community forum and email support for premium extras
extras.io 5 Email support for premium extras
bobsguides.com 47 Email support for Bob Ray’s extras

To use third party extra providers, you’ll usually need to create an account in order to access their Package Provider. You can find more information on how to do that in the documentation for each of the mentioned vendors.

Подготовительный этап:

  1. Скачивание дистрибутива CMS MODX Revolution.

    Для скачивания дистрибутива CMS MODX Revolution открываем в браузере официальную страницу http://modx.com/.

    На данной странице в меню открываем раздел «Get MODX», в котором выбираем пункт «MODX Revolution», находящийся в подразделе «DOWNLOADS».

    На странице «MODX Revolution Downloads» скачиваем традиционную версию дистрибутива, посредством нажатия на кнопку «Traditional — 9.5MB*».

  2. Скачивание и установка программного комплекса Denwer.

    Скачивание дистрибутива «Denwer» осуществляем с веб-страницы http://www.denwer.ru/.

    После завершения загрузки программы, запускаем файл и следуем инструкциям по установке, которые появляются на экране. В конце установки у Вас на рабочем столе должны появиться 3 ярлыка: «Start Denwer» (для запуска локального сервера), «Stop Denwer» (для остановки локального сервера) и «Restart Denwer» (для перезагрузки локального веб-сервера).

    Инструмент Denwer включает в себя все необходимые программы: веб-сервер Apache, препроцессор гипертекста PHP, систему управления базами данных MySQL и веб-приложение «phpmyadmin» для администрирования MySQL.

  3. Создание домена и распаковка архива MODX Revolution

    Создание домена в Denwer осуществляется путём создания папки с одноимённым названием в каталоге «home», находящимся на диске «Z:» или на «C:\WebServers».

    Например: создадим домен mysite.ru.

    После создания домена, в папке «mysite.ru» создадим ещё одну папку с именем «www». В эту папку мы будем распаковывать содержимое архива CMS MODX Revolution.

Post-Installation Summary

MODX will then let you know if any errors occurred during install, and prompt you to attempt reinstallation should any of those errors have occurred.

When install is successful, click ‘Next’ to proceed, and you’ll be presented with one final option:

MODX recommends that you make sure to remove the directory after installing, to safeguard your site from anyone else trying to run setup on your site. You can do this by clicking the ‘Check this to DELETE the setup directory from the filesystem.’ checkbox.

WARNING: the setup application grants powerful and far-reaching control over your server. DO NOT leave it in place, after you’ve finished installing MODX.

When ready, click ‘Login’ to be presented with the Login form for the manager interface. You’re finished!

Оцените статью
Рейтинг автора
5
Материал подготовил
Андрей Измаилов
Наш эксперт
Написано статей
116
Добавить комментарий