On Mar 14, 5:27 pm, The Editor <[email protected]> wrote:
> On Sun, Mar 14, 2010 at 10:07 AM, Markus <[email protected]> wrote:
> > 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
>
> But this is only expected because you understand the inner workings of
> BoltWire. Take a new user, decided they don't need an action.zones
> page or some other system page, so they press delete. Using your
> approach BoltWire would say, page deleted, and then it is immediately
> recreated. What? I thought I deleted that! So he deletes again--as
> many times as he likes with no effect. Throws up his hands in
> confusion--how do I get rid of that page...
Not if action.delete checks if a system page with that name exists and
tells the user "Your field copy of action.edit was deleted, the system
page will be used from now on."
I don't think anyone who does not understand the inner workings would
delete pages they don't understand. At least I hope so.
> Under the current system of course, he clicks delete, and the page
> vanishes. Granted, it is really an illusion in this case--but it is
> the closest thing to what the normal user would expect I can think of.
> I'd be more inclined to change the documentation, if needed, than to
> change the feature. Admins should have a way to delete system pages
> they don't want on their site.
Admins would have that option: create an empty page named after a
system page.
> > Example: Delete your top
> > - you no longer have a top page in your field
>
> But go to page top--and it shows up in your browser as if it were there...
And now you know that the system page is used as action.delete told
you. ;)
> > - system/pages/top is used but not copied to your field
> > - if you decide to create a custom top, do it
>
> These are true either way. The question is only whether or not that
> page can be deleted when you want it to be. Under the current system
> it can at least act as if deleted, and literally be deleted (the
> second time you hit delete). Under your proposal, you only have the
> one option, not the other. I like options. And keeping things more
> intuitive for new users. We old times can adapt to anything. :)
For me this delete-twice thing does not even work... empty page
remains. But please don't fix it! ;)
New users also get confused if they deleted a hundred pages and were
presented action.missing each time and this does not happen for
action.edit. My proposal would only confuse people who don't read the
first (?) doc page or who don't read what BoltWire tells them. Confuse
them instead of the careful readers.
Okay, as said my proposal allows all options: create an empty page
("delete system page"), use local page, use system page.
Concerning the old times... We can also adjust to creating an empty
page.
Most importantly, deleting twice is like... dying twice. It just makes
no sense at all. :) You cannot delete something deleted because it is
(should be) already deleted.
Markus
> Cheers,
> Dan
--
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.
