discuss.answer
Is this not what Static Elements are for?
TinymceWrapper: Complete back/frontend content solution.
Harden your MODX site by
passwording your three main folders:
core, manager, connectors and renaming your
assets (thank me later!)
5 ways to sniff / hack your own sites; even with renamed/hidden folders, burst them all up, to see how secure you are not.
PHP goes into plugins and snippets.
HTML and client-side stuff go into Templates and Chunks.
Whatever that is permissible in an element is also permissible in its static form.
If Template can hold MODX snippet tags and placeholders, so can a its static form.
I am not sure I understand .php templates ... but I hope this helps
TinymceWrapper: Complete back/frontend content solution.
Harden your MODX site by
passwording your three main folders:
core, manager, connectors and renaming your
assets (thank me later!)
5 ways to sniff / hack your own sites; even with renamed/hidden folders, burst them all up, to see how secure you are not.
Plugins, Snippets, Chunks, and Templates, can all be marked as static. That creates a file containing their content that you could deploy to the remote.
Note that MODX doesn't actually use the file. It still uses the version in the DB. The file is just a copy of that. You can update either way: 1) edit in the Manager and save the file. 2) Edit the file and reload the page in the Manager.
Be careful, though. If you delete or empty the file and reload the element in the Manager, your content is lost for good.
Be careful, though. If you delete or empty the file and reload the element in the Manager, your content is lost for good
MODX Static Electricity! that shock is not a friendly one: "where's ma content???"
TinymceWrapper: Complete back/frontend content solution.
Harden your MODX site by
passwording your three main folders:
core, manager, connectors and renaming your
assets (thank me later!)
5 ways to sniff / hack your own sites; even with renamed/hidden folders, burst them all up, to see how secure you are not.
LOL.