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.
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.