MODX Revolution 2.4.3 — A Variety of Bug Fixes and Enhancements

- MODX Staff
- 10,725 Posts
opengeek Reply #1, 8 years, 2 months ago
Another patch release of MODX Revolution 2.4, 2.4.3 is now available. If you missed the 2.4.0 announcement, check out the details here.

Highlights from the changelog:
- Prevent uncacheable elements from being cached in cacheable elements
- Fix loading rich text editors on non-document resource types
- Cache-busting token added to manager js and css links to force refresh after upgrades
- Corrected dashboard's save button action
- Fix modX->getUser to force load settings when parameter is passed
- Various config_check improvements
- …and a variety of other improvements & bug fixes
Important: 2.3.6 contains a security patch and is considered a mandatory update. 2.4.0 contains all patches from 2.3.6, and also closes the security issue. 2.4.3 is a non-critical patch of the 2.4 branch.

Contributors on this Release
Let’s take the time to thank the individual contributors to this release (in no particular order):Mark-H, pixelchutes, Alroniks, hansek, inreti, oori, jpdevries, whitebyte, Jako, tehsquidge, rtripault, ViieeS, yoleg, tyllo, theboxer, along with many other contributors who log & triage issues, review PRs, and commit code. The MODX Community is Amazing.

Security is an Ongoing Process
We cannot stress how important it is to run the most current version of MODX. We are always improving security. Upgrade regularly to reduce the chance of your site getting hacked. If you need help upgrading your MODX site, let us know.

Get Started with Revo 2.4
Here’s what you need to get started or upgrade to MODX Revolution 2.4:
- Download Revolution 2.4
- What’s required to run Revolution 2.4.x
- How to install MODX Revolution
- How to upgrade MODX Revolution
- Read the MODX Revolution Documentation
Ask Not What MODX Can Do For You
MODX is only as good as it is because of the many individual community members and users that take the time to report issues, request new features, and submit code to the project. Make sure you read the documentation,post feedback and share your experiences in the MODX community forums.

On behalf of the entire MODX Team,
We thank you! [ed. note: smashingred last edited this post 8 years, 2 months ago.]
Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek
- 24,544 Posts
BobRay Reply #2, 8 years, 2 months ago

Cache-busting token added to manager js and css links to force refresh after upgrades

Yes!!!
Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting
- 293 Posts
Murray Reply #3, 8 years, 2 months ago

Quote from: BobRay at Feb 11, 2016, 08:36 PM
Cache-busting token added to manager js and css links to force refresh after upgrades

Yes!!!

Wooo!
I'm lead developer at Digital Penguin Creative Studio in Hong Kong. https://www.digitalpenguin.hk
Check out the MODX tutorial series on my blog at https://www.hkwebdeveloper.com
- ☆ A M B ☆
- 536 Posts
Last Of The Romans Reply #4, 8 years, 2 months ago

if I understand correctly...2.4.3 support php 7?
palma non sine pulvere
- 212 Posts
lettis Reply #5, 8 years, 2 months ago
Quote from: opengeek at Feb 11, 2016, 03:50 PM

Cache-busting token added to manager js and css links

What exactly does this mean? Can you give a simple example for me?

We only recognized that calling chunks cached like this
```
[[$chunk? &variable=``]] or [[$chunk]]
```
doesn´t work anymore with a chunk-content like this:
```
echo [[+variable:default=`10`]];
```
This only works since the update when the cunk-content is modified into (added '!' for uncached):
```
echo [[!+variable:default=`10`]];
```
[ed. note: lettis last edited this post 8 years, 2 months ago.]
- 24,544 Posts
BobRay Reply #6, 8 years, 2 months ago

That update won't affect placeholders, since it only applies to the Manager JS and CSS and won't do anything to the front end. Even in the Manager, it will only affect the first page load after upgrading MODX.

I don't know what the actual technique is, but it will be something like adding a query string containing the MODX version onto the end of the URL for Manager CSS and JS.

Browsers cache JS and CSS, so as long as the URL is the same, they don't actually bother to load it if they have it cached locally. Adding the version to the end of the URL will force the browser to reload those files after an upgrade(since the URL has changed), and prevent some of the problems we used to solve by clearing the browser cache and cookies after upgrading MODX.

It's possible that this change is causing what you're experiencing:

Prevent uncacheable elements from being cached in cacheable elements
Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting
- ☆ A M B ☆
- 24,524 Posts
sottwell Reply #7, 8 years, 2 months ago

install script updated. https://github.com/sottwell/installer
Studying MODX in the desert - http://sottwell.com
Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
Join the Slack Community - http://modx.org
- 212 Posts
lettis Reply #8, 8 years, 2 months ago
After upgrading to 2.4.3 we got big problems with our chunks. They now only work if everything is uncached. Code like this doesn´t work anymore:
```
[[$chunk? &variable=``]]
```
Chunk-Content:
```
echo [[+variable:default=`10`]];
```
We now have to use it everywhere uncached like this:
```
[[!$chunk? &variable=``]]
echo [[!+variable:default=`10`]];
```
Maybe this is because of these changes in 2.4.3:

- Prevent uncacheable elements from being cached in cacheable elements [#12835]

Do you think this is a bug?

We unfortunately had to downgrade to 2.4.2. otherwise our complete website wouldn´t work anymore.
- 212 Posts
lettis Reply #9, 8 years, 2 months ago

We are running another MODx (also upgraded to 2.4.3) on the same server where this problem doesn´t appear (there it is not necessary to call chunks uncached and it is not necessary to use placeholders in a chunk uncached. This seems to be very "crazy" for us.

Does anybody have an idea where these differences may come from?

I compared the system settings but on first look I couldn´t find differences but may be I overlooked something?
- ☆ A M B ☆
- 24,524 Posts
sottwell Reply #10, 8 years, 2 months ago

Where is that "echo" business coming from?
Studying MODX in the desert - http://sottwell.com
Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
Join the Slack Community - http://modx.org

This discussion is closed to further replies. Keep calm and carry on.