Hi Andreas
On 08.09.2009, at 09:31, Andreas Weder wrote:
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!
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.
-will
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
