so i create a static resource, point it to a HTML file on my web server. if i edit that file and reupload a new copy, the main website doesn't change unless I clear cache (template is a static resource).
this makes statics require me to login to my modX manager, where i'd have liked to have them managed by something like dreamweaver or espresso etc, (by other members who have access to the statics but not the manager)
-
☆ A M B ☆
- 24,524 Posts
In a case like that, you'd need to have your resources and elements all uncached. MODx cannot possibly know what files have been modified.
You could also create a custom Dashboard so the users wouldn't get anything except a button to "Update site" which would clear the cache.
I also figured out that if i edit the HTML file in my manager it updates real time, (since its clearing the resource cache)
but on a positive this works good enough to sync, and then commit to a GIT repository.
still wish I had versioning system but i think static resources are a step closer! nothing like being able to save my whole site to GIT, edit some resources, and then commit another GIT push.