var MODX_MEDIA_PATH = "media";

Hello

Ive just downloaded the latest release and am starting to play around with it.

Sometime ago I asked why the reference to the "media" path was shown in the header as I wanted to remove it, I was instructed to update to the latest version for safe removal - now its time but its still there!

Ive tested a little and found that when I use TV’s and allocate them to templates the reference to the media path is shown. If I dont allocate the TV’s to a template then the reference isnt shown - Is this a bug or is it supposed to work in this way.

Any help would be grateful

Cheers

Certain TV widgets require this at the current time and they are added by the process responsible for parsing the TV’s. It will go away in future releases, but will require completely new widgets, so we have hesitated to take them away at this point.

@OpenGeek

Thanks for the quick reply.

One final question - my understanding may not be correct but "[*#content*]" is also a TV.

Why does the path not show when only [*#content*] is used?

cheers

Your understanding is correct - [*content*] is indeed a TV, although it’s more commonly referred to as a ’Document Variable’ (as are any of the other core document variables such as pagetitle, longtitle, published, deleted etc.) - just distinguishes core variables from user-added template variables.

However, only TV’s that use certain output widgets will need the additional JS path being inserted. As [*#content*] doesn’t use an output widget, it doesn’t need the path to be inserted.

@garryn

Cheers for making things clearer

Conclusion:

If I understand correctly - if TV’s are not using widgets then it should be safe to use the plugin that "ram" has created above