-
- 24,544 Posts
Some objects (e.g. chunks and templates) have both a delete.php and a remove.php. The same work seems to be done by both. It looks like remove calls delete and appears to redundantly invoke the events, log the deletion, and clear the cache.
Is one or the other deprecated, or am I just confused about their roles?
Delete should mean "marked for deletion" and remove is actually being removed from the database, but delete should only apply to Resources, since that is the only objects we support marking for deletion with.
[Sorry, not sure how I missed these original postings, but thought I’d find unanswered questions this AM...]
-
- 24,544 Posts
Quote from: OpenGeek at Mar 13, 2010, 02:25 PM
Delete should mean "marked for deletion" and remove is actually being removed from the database, but delete should only apply to Resources, since that is the only objects we support marking for deletion with.
[Sorry, not sure how I missed these original postings, but thought I’d find unanswered questions this AM...]
Thanks, I still needed answers and all were really helpful.
Either I was confused or things have changed, but you’re right, it looks like only resources have a delete processor now.