PHP 8.4.15 MODX Manager doesn't open some *.js files

[patrickatwsrn]

Bug report

Summary

I have about a dozen *js files in assets/theme/... and I can't open a single one of them.

Step to reproduce

1. Download this js file from themeforest and upload it to assets/...
   https://html.webtend.net/2024/limestone/assets/js/aos.js
2. try to open it in your manager

Observed behavior

If I click a file to open it, this happens:

The file isn't loaded and the manager stays the same.

So far I believe I can rule out a server, plesk or firewall problem:

• I have checked for permission (server and modx) related issues.
• I have checked error logs (apache, firewall, modx)

No Chrome Browser related problems:

• The developer console doesn't show any javascript related issues.

So far, I have tries the following "solutions":

Doesn't help:

• Deactivating Ace
• Changing the extension from *.js to *.txt
• Removing most of the original javascript code from the original file
• Testing this on another server running 8.3.28 and 8.4.15
• Unminiyfy and renaming the js file
• rebuilding core/cache (yes, i am this desperate)

Occationaly helps (i have problems to reproduce this):

• Removing the original content and put some random javascript code inside (comments, alerts, etc.).

Always helps:

• Downgrade php from 8.4.15 to 8.3.28

My best guess this is somehow related to the content of a file. File size doesn't seem to be the problem.

Expected behavior

Opens file as expected

Environment

• MODX 3.1.2
• PHP 8.3.28 and 8.4.15 (same settings, see below)
• Apache/Plesk
• Ubuntu Server 20.04.6 LTS

[halftrainedharry]

I can't reproduce this.
I used the file you linked above (aos.js) and tested it locally with MODX 3.1.2 and PHP 8.4.15. The file opens without any issues.

---

When you open the "Network" tab of the developer tools in the browser and then try to open the *.js file, what is the response of the request to manager/?a=system/file/edit&file=assets/js/aos.js&wctx=mgr&source=1 (or similar) that should appear in the list. Is this request successful (response status code = 200)?

---

If this only happens to certain *.js files and the behaviour is dependent on the file content, then my best guess is, that it's firewall related.

[JoshuaLuckers]

Have you tried creating a new file with the same content? Via the manager? And does it work then?

[patrickatwsrn]

Sorry for the late reply. * I created a new file. No content. No problem. * Same file with a few lines of JS Code. Also no Problem * Same file with some of the code included in one of the blocked files. Bam. * Same file with the complete code. Bam again. The whole time I don't see any traces in my firewall that would explain what is going on here. Over the weekend I'll copy the whole thing to a third server and see if it works there. To be honest this issue this gives me supernatural vibes. Thanks for your time. BTW. I'm a huge fan of your videos!

…

On Thu, 4 Dec 2025, 19:21 Joshua Lückers - Jacobsen, < ***@***.***> wrote: *JoshuaLuckers* left a comment (modxcms/revolution#16790) <#16790 (comment)> Have you tried creating a new file with the same content? Via the manager? And does it work then? — Reply to this email directly, view it on GitHub <#16790 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQJHNLJG6QU6KU5XYLV3E234AB3RTAVCNFSM6AAAAACNTE7SZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMJTG4YTCMJYHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- *WSRN UG (haftungsbeschränkt)* Vertreten durch Susanne Drescher Amtsgericht 67061 Ludwigshafen, HRB 69029 wsrn.de  <https://wsrn.de> ***@***.*** ***@***.***>+49 (0) 6205 908 30 10An den Brunnengärten 12  |  67271 Neuleiningen