I’ve found that when my users start with polls, they make all kinds of errors which often aren’t realised until the poll is well underway.
Unfortunately, any edits to a poll cause the poll data to be wiped. This is understandable for poll integrity, but is sometimes highly undesirable when a simple tweak can fix a big problem for the user.
It is, however, doable via the rails console. Hacking a live poll changes the behaviour of the poll whilst preserving the data, but the markdown is not touched. I’m not sure what happens when you rebake the post, but suspect that the poll will revert to its original behaviour. By then it is likely to be old and forgotten so this isn’t a big deal.
The key is finding the post id; an easy way to find it is this SQL query (the poll of interest should be near the top):
SELECT post_id as postid, *
FROM polls
ORDER BY id desc
Here is an example poll hack, for when the user accidentally made a poll single rather than multiple:
I’ve moved this one over to installation rather than have it as an endorsed guide as it falls under the ‘sidestepping UI in rails’ scope (similar to the email in one previously).
I think we could do with some kind of halfway house for these kinds of tips as they are useful, but have an element of ‘at your own risk’ to them. Let me check back in and see what current opinions are.
Perhaps one tag more would be helpful, like #unofficial-tip or #dig-your-own-grave. Then categories could be more… on topic, but there would be an indicator telling that there is demand of some knowledge and a risk to fail miserably.
