search

modxcms / revolution

MODX Revolution - Content Management Framework
https://modx.com/
GNU General Public License v2.0
1.36k stars 529 forks source link

Static resources without content area #10334

Open frogabog opened 10 years ago

frogabog commented 10 years ago

frogabog created Redmine issue ID 10334

This occurs in various installations, versions 2.2.8-2.2.10-pl, new installs, Cloud installs, and existing installs.

Change existing resource to static, assign file, and the content area does not appear. New resources set to static also do not show a content area. Create new resource, set to static, assign file, no content area.

I have this issue in multiple installations on new clouds, new standard server installs, existing installs, etc. I used to think it was just when I changed a resource, but I just installed two clouds and tested creating static resources both with quick create and standard create and it happened on both brand new installs.

I recently installed with a temporary url on my server and do not have this issue. Same host today, with a sub-directory install and the issue exists. I can't see any real pattern for why. It just happens.

I set this to major, as it's a real PITA when I need to be able to see and edit static files both inside and outside of MODX.

rtripault commented 10 years ago

Not sure to get the problem here... the [[*content]] field stores the path to the file (so that the field used to select the "static file")

pk-informatics commented 10 years ago

you could use a chunk for this function?

rtripault commented 10 years ago

Sorry, probably due to a lack of coffee i did not read the last sentence, which explained the desired behavior... (somehow similar to static elements)

The issue i see with the request is that a static resource could be a link to a binary file (ie. a PDF). What would be the purpose of being able to edit that kind of file ?

A work around could be to define (and/or allow user defined) "text" file types (relying on file extensions ?), and display the content of the file when appropriate.

pk-informatics commented 10 years ago

Maybe a checkbox "is binary" will be an option too or simply use chunks

rthrash commented 10 years ago

I think @frogabog was having an issue with the input/field not working or showing.

That being said, there is certainly merit to having an editor for static content work just like the file tree, which is awesome with the Ace editor installed. Personally, I've used it for Sass editing and other quick fixes for CSS. All of which merits another issue.