MODX Evolution 1.0.13 Brings More than 110 Fixes and Improvements

MODX Evolution 1.0.13 is now available. This is the fourth release from the Ambassador-led Evolution team. Evo 1.0.13 includes 24 improvements, 44 refactors, 42 fixes and 1 security enhancement.

We'd like to thank the lead contributors for this release who are: Dmytro Lukianenko (Dmi3yy), Thomas Jakobi (Jako), Segr Kaparov (Segr), DivanDesign studio, esszett, and Eoler.

We'd also like to thank the translators who helped ensure the language files were current: Marc (fourroses), NL; luigif, Nicola (banzai) IT; Masanori Yamamoto (yama), JP; Dmytro Lukianenko (dmi3yy), Alex (Extremum), Pathologic, Segr Kaparov (Segr), RU; PontusAgren, SV; Witek Galecki (witq), pmfx , PL; everton_seib , PT; Thomas Jakobi (jako), DE.

To everyone who filed bugs and made feature requests. Thanks and keep them coming!

To keep your MODX sites safe and performing their best, we strongly recommend upgrading to the latest version of Evolution. If you need someone to assist you with your MODX Evolution upgrade, check out our MODX Professionals directory.

Here are the highlights of the 1.0.13 release:

  • KCFinder - change uploaded image/file names with TransAlias
  • ManagerManager updated up to 0.6.1
  • Updated API functions: clearCache, now you can call it with parameter full ($modx->clearCache('full');)
  • Updated API functions: getDocuments, getTemplateVars, getTemplateVarOutput, getDocumentChildren, getDocumentChildrenTVarOutput, you can call getDocumentChildren with parameter all for view all documents (not only published or unpublished, and the same with deleted)
  • Updated Wayfinder to 2.0.2 (available document specific placeholders [+pagetitle+], [+longtitle+] etc.; fixed work of @INHERIT for custom TVs)
  • Managers with role = 1 can see all documents in manager panel and in front-end (in earlier versions documents with restrictions to special groups could not be seen by those manager users)
  • Added API function: $modx->parseText()
  • Added document ID to title during editing document, also added to QM+
  • Breadcrumbs 1.0.4 (you can exclude documents with the specified templates)
  • phpthumb 1.2 (if images on page processed already, phpthumb class will not included)
  • eForm 1.4.5 (added parameters: &attachmentFields/&attachmentPath)
  • FirstChildRedirect 2.0 (added parameters: &default, &sortBy, &sortDir, &responseCode)
  • Read a complete list of changes in the changelog.txt file located at /install/

Download Evolution 1.0.13 now.

Here are the important links to get you on your way:

Details of Key Changes

The following notes will be of significant value to MODX Evolution site builders and developers.

API Changes

$modx->getDocument, $modx->getDocuments, $modx->getDocumentChildren, $modx->getDocumentChildrenTVarOutput, $modx->getTemplateVarOutput, $modx->getTemplateVars

Added ability not consider parameters published and deleted during getting document.

 @param $published {0; 1; 'all'} - Document publication status. Once the parameter equals 'all', the result will be returned regardless of whether the documents are published or they are not. Default: all.

 @param $deleted {0; 1; 'all'} - Document removal status. Once the parameter equals 'all', the result will be returned regardless of whether the documents are deleted or they are not. Default: 0.   


Method allows get document ID by its alias (used in search in manager panel), available since 1.0.12.

$docid = $modx->getIdFromAlias('blog.html');
$docid = $modx->getIdFromAlias('catalog/tovar.html');

Method used for send mails by API (available since 1.0.12). Works with settings, sending emails using mail() or SMTP according to the specified settings in the manager panel. Usage:

#simple variant
    $param = array();
    $param['from']    = "{$site_name}<{$emailsender}>";
    $param['subject'] = $emailsubject;
    $param['body']    = $message;
    $param['to']      = $email;
    $rs = $modx->sendmail($param);

#variant with additional settings 
    $modx->mail->From       = $from;
    $modx->mail->FromName   = $fromname;
    $modx->mail->Subject    = $subject;
    $modx->mail->Body       = $report;
    if(!$modx->mail->send()) return 'Main mail: ' . $_lang['ef_mail_error'] . $modx->mail->ErrorInfo;

MODX is only as good as it is because of many individual community members and users that take the time to report issues and request new features. Make sure you read the documentation, post feedback and share your successes in the MODX community forums.

On behalf of the entire MODX Team,

Hi. We’re MODX.

We’re here to help you fix, build and grow fantastic sites. How can we help?

How can we help?

Tell us the general reason for reaching out so we can connect you with the right team.

MODX Diagnostics

MODX’s Open Source software is 100% free for anyone to download and use. As the team behind it for more than a decade, we know it inside, out, and then some.

Like any software, sometimes things break; we can usually fix them very fast. But, we do have to charge for our time to support our families and fund its ongoing development. There are almost an unlimited variety of things that can cause problems, including server upgrades, corrupt files, accidental changes, outdated software, database hiccups and more. We will save you a lot of time and frustration, and get you back in action.

With our MODX Diagnostic service, we determine the source of issues, and often fix them on the spot. For more extensive problems needing more time, like hacked sites or overdue upgrades, we provide additional estimates and guidance. MODX Diagnostics cost $99 for standard business hours support (US Central Time), or $500 for priority, rush or after-hours emergencies.

If you don’t have budget for professional support from the source, you look for answers in the MODX Forums or Documentation, or seek help from MODXers in the Community Slack, or from MODX Professionals near you.

  I’m not ready to pay, let’s talk…

After submitting this form and completing payment, we will collect your access credentials in a secure support ticket. We look forward to helping restore your site back to full health.

Hi! We’d love to work together.

If you have a simple problem that needs our assistance, please request quick fix help here.

What should we keep in mind?

The project involves:
(select all that apply)
What are you planning?
(select all that apply)

Some other considerations

Specific project information

Commercial Support Customers

Customers with a current Commercial Support agreeement can get help using this form. Learn more about MODX Preferred Support.

Let’s get started

What seems to be the issue?

Contact MODX

We welcome conversations, ideas, inquiries and even the occassional cold sales call, but support and requests about how to use MODX software sent via this form cannot be guaranteed a response. That said, we try to respond to everyone that reaches out to us within two business days.

To report a security issue or file a bug for MODX software, please email security [at] to reach our security team. If you are looking for help with MODX, many times you can find an answer in the MODX Forums or MODX Documentation, from MODXers in realtime at the MODX Community Slack Channel, or from a MODX Professional near you.

How can we help?