On Mar 14, 3:41 pm, The Editor <[email protected]> wrote: > Can you explain what you would like to see happen? If you completely > delete a local copy of a system page, it pulls the system page back > in--immediately--which is quite confusing. So a blank page is probably > our best alternative. To get rid of the page completely (and revert to > the system page) delete the blank page a second time. You should not > have to use ftp for anything...
The only thing that would not confuse me is this (ah, yes, I easily get confused): - read in the BoltWire introduction that whenever my field has a page named after a system page that one is used instead of the system page - after creating a page named after a system page, I see the local page and have it saved in my field - after deleting a page named after a system page, I see the system page and have it not saved in my field Straightforward, expected behavior (at least for me), no unnecessary files in the field. Also updates of system pages will not be "hidden" from you unless you created a local copy (and did not delete it). Example: Delete your top - you no longer have a top page in your field - system/pages/top is used but not copied to your field - if you decide to create a custom top, do it And it's consistent. Delete deletes the page. Create creates a local page. And the rule you learned (first local, then system) holds true. There are only two pages I can think of that should be copied to the field. code.style and code.skin if you use a custom skin. Your turn. :) Markus > As for the differences between top and other system pages--if you look > at the pages folder, you'll see deleting them does exactly the same > thing. That is, go to page "top" and notice what happens in the main > zone when you delete it. Evidently the skin pulls in the system page > for a skin zone if the local page is blank I suspect this is a good > thing rather than a bad one though, as it could mess up a skin pretty > easily. But we could explore this in more detail if you are convinced > it should be changed. > > Cheers, > Dan > > On Fri, Mar 12, 2010 at 3:32 AM, Markus Weimar > > > > <[email protected]> wrote: > > Hi, I mentioned this is another thread but this deserves its own. > > > Create a local copy of a system page, delete it and it will leave an empty > > file in the file system that you can only get rid off via FTP or root > > access. Users have almost complete control of BoltWire from the web > > interface. Users are told that if there is no local copy of a page, > > BoltWire will use the one in the system pages folder. But if you click > > delete, you don't expect to have a local copy any longer. You rather wonder > > why your plugins page which you accidentally messed up and restored just > > displays an empty page. > > > To make things even more inconsistent _some_ pages will not leave an empty > > one. Delete top and you get a copy of the system page in your field folder. > > > It's also the only circumstance I am aware of that could push someone > > without knowledge of FTP or server access into a dead end. This is sad > > because you cannot install BoltWire for someone and be sure that everything > > that can happen can be solved from via the web interface. > > > The "use system page if no local page exists" feature is awesome and I > > think we should use it consistently and not at the same time undermine the > > power of the web interface. > > > Markus > > > -- > > You received this message because you are subscribed to the Google Groups > > "BoltWire" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/boltwire?hl=en. -- You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/boltwire?hl=en.
