Modx 2.8.2 tag not rendered in static resources

tillilab · April 29, 2021, 9:48pm

Summary

After upgrading to 2.8.2 my static resources show the tag not parsed in the frontend, i.e.
[[++site_url]] but also link like [[~12]] and so on.
Does it happen only to me?.. Is it a wanted behaviour with the new version?
If so… can I enable somehow in order not to break existing websites?
Thanks!

Environment

Modx 2.8.2, php 7.4

raffenberg · April 30, 2021, 8:46am

It looks like there was introduced a little bug in 2.8.2 / static resources. Probably be related to your problem.

collst256678 · April 30, 2021, 11:11am

And also doesn’t show any files in CKEditor or tinymce

markh · April 30, 2021, 11:27am

@tillilab likely this is the same issue you’re having:

github.com/modxcms/revolution

Static resources not working correctly in 2.8.2

opened 07:42AM - 30 Apr 21 UTC

muzzwood

bug urgent

## Bug report ### Summary When viewing a static resource (web context) in 2.8.…2, only the content field renders. The rest of the template is ignored. I noticed the issue when upgrading a site from 2.8.1 that relies on static resources. As a quick fix, I have copied over `modstaticresource.class.php` from 2.8.1 and that works as expected. ### Step to reproduce Create an HTML file, create a static resource and link to the file. Be sure to use the new system settings `resource_static_path` or `resource_static_allow_absolute`. Assign a template that's not empty and has the `[[*content]]` tag specified. ### Observed behavior Only the content field renders. The rest of the template isn't there. If the `[[*content]]` tag is removed from the template, then the template renders fine (obviously without the content). ### Expected behavior Template should render as normal with the static resource content being added via the `[[*content]]` tag. ### Related issue(s)/PR(s) Could be something to do with a change made here: https://github.com/modxcms/revolution/pull/15656 ### Environment MODX version 2.8.2

@collst256678: That has been fixed, you can apply it manually if you need to before an update:

github.com/modxcms/revolution

Pass auth token to the config in the Browser controller

modxcms:2.x ← Mark-H:v282-browser-rte

opened 01:11PM - 29 Apr 21 UTC

Mark-H

+1 -1

### What does it do? After #15644, the modx config is only available when an …authentication token is provided in the parameters. The ?a=browser controller is a special one used by extras (in particular tinymce rte, probably tinymce as well) that provices the regular media browser (?a=media/browser) without the manager frame. It's meant to be opened in an iframe. This PR adds the necessary token (which is already being set in the BrowserIndexController) to the request to restore the functionality of third party editors. ### Why is it needed? Without it, ?a=browser is broken and editors like TinyMCE RTE fail to access the media browser. ### How to test You could install TinyMCE RTE and try adding an image to the page. That will show you a few warnings in the console and an empty panel. Alternatively, simply browse to ?a=browser and verify that before this fix nothing was shown, and after this fix it shows the functional media browser as expected. ### Related issue(s)/PR(s) Regression from #15644. Reported on Slack.