I understand that currently discourse can only handle one unpublished draft and that this draft is shared across devices, right? It works fine and I love it, but every now and then, when I start a new reply to a topic, the editor contains an old draft of some previous reply which I either dismissed or which I already published (possibly from another device). So it looks like drafts are also stored locally but not deleted under certain circumstances such as when the draft is published from another device.
1 me gusta
One draft new topic, but one draft reply for every topic.
6 Me gusta
Earlier this week, I started a reply in one topic, then navigated to another topic and posted it there. When I returned to the first topic (on a different device), my “draft” post was still there. That sounds like what Christoph is describing.
Is there a specific repro?
Not sure. I’ve only had it happen once, and attempting to reproduce it now on try, I’m not seeing it.
2 Me gusta
Creo que lo solucioné recientemente.
Antes teníamos una clave de borrador “createtopic”, una clave de borrador “reply as new topic” y una clave de borrador “new topic”.
Esto causaba todo tipo de confusión. Ahora todo está normalizado.
4 Me gusta
¿Qué tenemos ahora? ¿Solo una clave de borrador normal?
Tenemos:
- Clave única para “nuevos temas”
- Clave única para “nuevo mensaje”
- Clave única por “tema” (abarca: responder como nuevo tema, responder como MP, editar publicación, responder al tema)
6 Me gusta
Este tema se cerró automáticamente después de 3 días. Ya no se permiten nuevas respuestas.