[ZCM] [ZC] 1328/ 2 Reject "Write Back Support of FSObjects wich are customized"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #1328 Update (Reject) "Write Back Support of FSObjects wich are customized"
 Status Rejected, Zope/feature+solution medium
To followup, visit:
  http://zope.org/Collectors/Zope/1328

==============================================================
= Reject - Entry #2 by tseaver on May 13, 2004 11:02 am

 Status: Pending => Rejected

A couple of issues:

  - The CMF collector is at http://zope.org/Collectors/CMF

  - I won't accept the writeback part of the patch there,
    because we *never* allow through-the-web actions
    (which are untrusted) to modify filesystem code
    (which is trusted).

The part of the patch which records the original path
(during customization) is probably a reasonable feature;
in fact, I have often thought about copying the original
source of the file to an "fs_original" attribute or
property, to make it possible to diff the two, even
(especially) if the filesystem version has been updated.

Assuming that we do merge the customization part of the
patch, here is how I would suggest that you get writeback
working;  either:

  - Release an external method which can be invoked
    via URL on a customized skin method (or maybe the
    custom folder?), e.g.:

     http://example.com/cmf/portal_skins/custom/main_template/writeback


  - Release a derived version of the SkinsTool which
    has the logic in the tool (e.g., it offers a
    "Writeback" button on the folder contents view of
    custom folders).
________________________________________
= Request - Entry #1 by kaihoppert on May 13, 2004 5:27 am


Uploaded:  "feature.py"
 - http://zope.org/Collectors/Zope/1328/feature.py/view
It's something for people who can't develop on their own local zope server. With this funktion you have the possiblility to write back customized file system objects like page templates, python scripts etc. to file system. I think some of you would know the following situation. You developed a new Product an played it to the server where it should be used. Then you noticed a failure in scripts or templates. You have many possibilities in solving this bug. fixing the bug and play the fixed version to the server, fixe the bug on the server on file system, or fixe it in customizing the fstemplate or script. I prefere the last because i also use external editor to have more compfort in editing files and i think it's the fastest way. The only disatwantage is that you sometimes want to bring back thes changes to file system because you use this product also in a nother instance or server. But this is a little bit circular. So i write a little method which provide writing back these changes to filesystem. You can use it on linux or windows.

Some description for the method you can find in the attachement.
==============================================================