Comunidad Guías…

Ayuda y problemas de revel-backend

Pregunta a la comunidad o invita a KiBot con contexto del repositorio.

Publicar un problema

No publiques contraseñas, tokens ni claves privadas. HostingByte aplica una redacción básica de secretos evidentes antes de guardar el texto.

Problemas en HostingByte

Todavía no hay problemas publicados.

Issues abiertas upstream

#1364 chore(common): settings-derived field defaults get frozen into migrations · 0 comentarios #1346 fix(integrations): hidden external ticket classes stay purchasable via access codes · 0 comentarios #1341 fix(events): editing a linked tier's purchase rule can make it stricter than its series pass · 0 comentarios #1317 epic: member register (legal membership records) + day memberships for Vereine · 0 comentarios #1311 Series passes: bulk-granted pass tickets never remove the holder from the event waitlist · 0 comentarios #1270 notifications: delivery paths crash on a missing NotificationPreference row instead of creating defaults · 0 comentarios #1269 notifications: a guest's one-click opt-out is reset when the guest converts to a full account · 0 comentarios #1262 wallet: update existing Google Wallet objects when ticket fields change · 1 comentarios #1258 compliance: tax-advisor confirmations for small-business invoicing (DE/AT) · 1 comentarios #1259 invoicing: VAT-charging organizers with only a tax number (no EU VAT ID) · 0 comentarios #1097 compliance(FR): later layers (revenue statement, SIBIL, declaration pack) · 1 comentarios #1102 compliance(BE): later layers (Peppol) · 1 comentarios #1223 chore(email): raise DMARC to pct=100 after BIMI soak (~2026-11-09) · 0 comentarios #1148 Epic: organization branding and custom-domain white-label · 0 comentarios #1187 refactor(common): remove common's imports from accounts and events · 0 comentarios #1158 Backlog: send org emails from the organization's own domain · 0 comentarios #1140 Subscribe the Brevo webhook to 'unsubscribed' and map it to a per-type opt-out · 0 comentarios #1139 Brevo open/click tracking is on for transactional mail (conflicts with the privacy policy) · 0 comentarios