Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Do standalone (non-event) forms ever need payment collection?

Abierto
  • ¿Algo no está bien?
#2,590 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Área
payments

Línea de trabajo

Start by reviewing PR #2588 and the standalone form flow at /f/:slug, then inspect how payment_method, someone_else_will_pay, and additional_forms currently attach to EventRegistration. The next step is stakeholder confirmation of whether standalone payments are needed and, if so, what they charge and where their records belong; otherwise, mark these fields as event-only on the Smart field settings page.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

blocked stakeholder-question

🤖 From Claude: Filed on behalf of the team while working on the standalone-form smart-field parity work (PR #2588).

The question

Do we need standalone forms (collab / agreement forms filled out at /f/:slug, not attached to an event) to collect payment?

Why it's blocked

We made person and organization smart fields behave the same on standalone forms as on event registration forms (PR #2588). The one group we could not bring over is payment — payment_method, someone_else_will_pay, and additional_forms (Invoice / W-9):

  • Those fields all write to an EventRegistration, and the pay-now flow starts a Stripe checkout using the event's cost.
  • A standalone form has no event and no registration, so there is nothing to attach a payment to and no cost to charge.

So "handle payment on standalone forms the same as event forms" isn't implementable without deciding what a payment on an event-less form even means.

What we need from stakeholders

  1. Is there a real need to take payment on a form that isn't tied to an event? If so, for what (a flat fee? a donation? a membership)?
  2. If yes, what should it charge against, and where should the money/record land (no EventRegistration exists today)?
  3. If no, we'll leave payment as event-only and mark those payment smart fields as event-only on the Smart field settings page.

Until we hear back, payment stays event-only.

Lenguaje dominante
Ruby
Estrellas
15
Forks
28
Merge medio
1 d 12 min
PR fusionados (30 d)
262

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de rubyforgood/awbw

Todos los issues de rubyforgood/awbw

Issues similares

Más issues de Ruby

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.