Skip to main content
Topic: We can haz auto deletion of used drafts? (Read 1936 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

We can haz auto deletion of used drafts?

Was wondering if it's possible to set drafts up so that they get automatically zapped as soon as they are used in a post.

So presumably this would have to have a tie between the draft ID and the post ID, so you could edit the draft and then post it without the software losing the plot.

This would be cool, because then you wouldn't be crudding up the db with oodles of drafts[1] (if using a long time limit on storage), and you wouldn't have to worry about losing ones you had saved but not used yet (if using a short time limit on storage).

Can be done? Easy? ZOMFG?
Incidentally, we found that having oodles of drafts linked to a thread can make the post editor respond really slowly, for some weird reason. As soon as the majority of the linked drafts were zapped (by changing the time limit in admin) response times went back to normal.

This was on an 800 page thread, which gives you some idea of the number of drafts that could build up. Also gives you some idea of Elk's ability to handle really long threads (seems to do it very well).
Master of Expletives: Now with improved family f@&king friendliness! :D

Sources code: making easy front end changes difficult since 1873. :P

Re: We can haz auto deletion of used drafts?

Reply #1

QuoteZOMFG
No kitteh? ZOMG??

(blarg)
LiveGallery - Simple gallery addon for ElkArte

Re: We can haz auto deletion of used drafts?

Reply #2

There is an option in the admin panel that auto-deletes drafts after a certain amount of time.

Drafts are deleted when posted, though it's not always true because... for sure several edge cases, I think @Spuds kept a somehow conservative approach to avoid losing data needed, because usually it's easier to delete something rather than recover it. :P
Bugs creator.
Features destroyer.
Template killer.

 

Re: We can haz auto deletion of used drafts?

Reply #3

Hmm. Given the number of them that we had building up there must have either been a lot of edge cases or, more likely, people simply weren't using them for posts. Or a combination of the two.
Master of Expletives: Now with improved family f@&king friendliness! :D

Sources code: making easy front end changes difficult since 1873. :P