Hi Will, >> it's been a while since I last worked with Magnolia - my last >> projects used >> the then newly launched 3.0. I can see that many things have changed >> and >> the CMS has further matured. The new STK templating looks great. > > Welcome back! >
Thanks :) It's been a while... >> On the side of things that haven't changed, is it true that: >> >> - deleting a node still immediately leads to an activation from >> author to >> public - deleting a node thus always also deletes it immediately on >> the >> published website? > > Yes. How would you otherwise be capable of deleting a node on public > when it has already been deleted in author? > >> Does this also hold, if I use workflows? > > I would say so. Again: There really would be no clean way to delete a > public node when the author node has already been deleted before. > >> - once a node has been deleted, this single node can't be recovered >> from a >> backup, since it's GUID has already been used? > > Hm... not sure I understand what you mean. Of course any deleted data > can be recovered from a backup you've made before. > >> Thus the only way to recover if a user accidentally deletes a node >> is to >> restore an entire, previously backed up state of the site, possible >> loosing all work done he or she has done in the mean time. > > No. As said above: You can easily restore content from the backup. > That is what backups are for in general ;-) > >> - I can't prevent a user from deleting nodes in general, since the >> ACLs only >> know the read and write rights? There's no delete right, but >> deletion is >> actually covered by the write right. > > Same as in UNIX. Hmm... without raising too much of an argument with my first email already: don't you think this is somewhat counter-intuitive? Let me explain. Magnolia is about simplicity. If I explain a customer the idea of the activation and the workflows, he immediately grasps it. He'll allow his media people to fill in content, which he then reviews and publishes. Then I have to tell him that his media people can delete nodes without him being able to say anything about it. They might even only do so accidentally and change the published website immediately. If I see this correctly: - even with versioning and workflows activated, I can't choose the parent node, choose "Versions" and restore its previous version to get back the deleted sub nodes. - I thus have to take a backup to restore the deleted node. Can I simply restore the node I just deleted? Or do I rather have to restore all nodes in the backup? I'm not quite sure here. - if there was a "delete" right, I could only allow my customer to delete nodes, and prevent his media people from causing havoc. I see the technical reason behind why this is working the way it currently does. I just find it somewhat surprising and difficult to sell. Andreas -- Andreas Weder Senior IT Consultant mp technology consulting GmbH Brauerstrasse 60 CH-8004 Zürich, Switzerland [email protected] Phone: +41 43 322 04 82 Fax: +41 43 322 04 09 http://www.mptechnology.ch ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
