Descripción
GravityCalendar muestra las entradas de Gravity Forms en una vista de calendario, transformando los envíos con campo de fecha en eventos en los que se puede hacer clic en las vistas mensual, semanal y diaria. La extensión se integra directamente con GravityView para mostrar agendas, calendarios de reservas y cronogramas de citas a partir de los datos ya recopilados por los formularios, sin requerir un plugin de eventos independiente ni sincronización externa con servicios como Google Calendar.
Características principales
- Múltiples vistas de calendario
Muestra las entradas en los modos mensual, semanal, diario y lista de agenda. - Mapeo de campos de fecha
Vincula cualquier campo de fecha o fecha/hora de Gravity Forms como origen de los eventos. - Colores y categorías por entrada
Permite asignar colores y etiquetas según el valor de los campos del formulario. - Ventana modal de detalles al hacer clic
Abre los datos completos del envío en una ventana emergente o redirige a la página de GravityView. - Filtros y búsqueda integrados
Aplica los filtros de GravityView al calendario para limitar las entradas que aparecen.
Beneficios de GravityCalendar – Display Entries on a Calendar
- Aprovecha los datos existentes
Reutiliza los envíos de Gravity Forms sin migrarlos a otro plugin de eventos. - Vista clara para los visitantes
Sustituye tablas y listas largas por un panel mensual fácil de leer en el front-end. - Configuración dentro de GravityView
Reduce la curva de aprendizaje al mantener todas las opciones en el mismo editor de la View. - Versatilidad de uso
Abarca reservas, citas, plazos y eventos a partir de un único formulario.
¿Para quién está indicado?
- Sitios que recopilan reservas, citas o inscripciones mediante Gravity Forms y necesitan mostrar los registros públicamente.
- Escuelas, iglesias, asociaciones y clubes que mantienen calendarios internos de eventos a partir de formularios.
- Equipos que ya utilizan GravityView para listar envíos y desean añadir una capa visual de calendario.
Dirigido a quienes ya han estructurado flujos en Gravity Forms y usan GravityView para presentar los datos, este complemento amplía la variedad de diseños disponibles sin duplicar registros en otro sistema de eventos. El resultado es un calendario front-end alimentado en tiempo real por los propios envíos, que mantiene el control de los filtros, permisos y visualización en el mismo panel administrativo.
Preguntas frecuentes
¿El plugin GravityCalendar – Display Entries on a Calendar es GPL?
Sí. GravityCalendar – Display Entries on a Calendar se distribuye bajo la licencia GPL (GNU General Public License). Puedes usarlo, modificarlo y redistribuirlo legalmente en todos los sitios que quieras.
¿Puedo usar el plugin GravityCalendar – Display Entries on a Calendar en más de un sitio?
Sí. Puedes instalar GravityCalendar – Display Entries on a Calendar en todos los sitios que quieras. Solo las actualizaciones automáticas con Ultrapack Auto Updater tienen límite: de 3 a 80 sitios, según el plan.
¿Cuánto cuesta el plugin GravityCalendar – Display Entries on a Calendar en Ultrapack?
GravityCalendar – Display Entries on a Calendar cuesta US$ 2,99 en la compra individual, y también está incluido en los planes de suscripción desde US$12/mes (VIP I).
¿El plugin GravityCalendar – Display Entries on a Calendar incluye actualizaciones?
Sí. La versión actual de GravityCalendar – Display Entries on a Calendar es la 2.23.0, publicada en Ultrapack el 24/09/2026. Los suscriptores actualizan directamente desde el panel de WordPress con UAU (Ultrapack Auto Updater).
¿Es seguro descargar e instalar el plugin GravityCalendar – Display Entries on a Calendar en mi WordPress?
Sí. Cada versión de GravityCalendar – Display Entries on a Calendar pasa por un análisis de malware (ClamAV y reglas YARA, en UltraHub) antes de publicarse.
¿Cuáles son los requisitos del plugin GravityCalendar – Display Entries on a Calendar?
Requiere WordPress 5.6 o superior y PHP 7.4 o superior. Probado hasta WordPress 7.1.
Qué cambió en esta versión
Versión 2.23.0
- This release makes conditional logic more accessible and fixes matching on product prices.
- Note: GravityCalendar now requires WordPress 6.5 or newer.
- ✨ Improved
- Keyboard and screen reader accessibility of conditional logic: focus stays in place when adding or removing a condition, the AND/OR switch is a single control, and date fields and buttons identify the field they belong to.
- Wider Custom Value box in narrow settings panels.
- Conditional logic on product prices matched the wrong entries, especially with currencies that use a comma for decimals or place the symbol first (such as Pound Sterling).
- The page scrolled when a date picker calendar was opened or closed.
- 🔧 Updated
- [Foundation]
Versión 2.22.0
- This release adds a GravityCalendar widget for Elementor, allows overriding calendar height when embedding, and fixes some bugs. GravityCalendar now requires WordPress 5.6 or newer.
- A GravityCalendar widget for Elementor. Drag it onto the page, pick a calendar, and it renders in the editor as it will on the page — no shortcode to paste. The widget is under the GravityKit category in the widget panel.
- Ability to override the calendar's defined height when embedding a calendar
- Shortcode: `[gravitycalendar id="5" height="400px"]`. Accepts the same values as the Calendar Height setting — `400px`, `100%`, `10vh` — plus `auto`
- GravityCalendar block: a Height field under Calendar Size in the block settings
- Elementor widget: a Height slider on the Style tab.
- ✨ Improved
- Added support for the Block Editor's version 3 block API.
- Calendars whose feed was created outside the settings screen — through the API, or before the Sizing setting existed — logged a PHP warning every time they rendered.
- Only administrators could open a form's GravityCalendar feed settings. Now, anyone who can edit forms can edit the feed.
- Administrators on sites running the Members plugin could not see the feed settings.
- Merge tag pickers were not showing in the calendar feed settings screen.
- The Active/Inactive toggle on the All Calendars screen displayed as a plain, unstyled button.
- Calendar toolbar buttons showed HTML character codes instead of punctuation in some languages — in French, the "Today" button read "Aujourd'hui" rather than "Aujourd'hui".
- The calendar's Filter control did nothing on calendars whose Localization is set to a language other than English.
- GravityCalendar block preview in the WordPress editor
- Did not recover when a feed was selected again after its settings had failed to load
- In the WordPress 7.1 editor
- Showed "This block has encountered an error and cannot be previewed" instead of the calendar
- Did not switch the active Stack/Grid button of the multi-month layout
- Kept the Filter button instead of replacing it with the search box, so events could not be filtered
- Opened event tooltips away from their event when the `interactive` option is turned off.
- Showed JavaScript errors in the browser console
- Clicking the export link in the GravityCalendar Buttons block preview downloaded the calendar file.
- 🔧 Updated
- [Foundation]
Versión 2.21.0
- This release speeds up calendar subscriptions, keeps them up to date when entries change, and fixes several subscription and timezone issues.
- ✨ Improved
- Completely reworked how calendar subscriptions are generated to improve performance.
- Large calendar feeds now generate without a sweat (tested on forms with more than 20,000 entries)
- Now served from a stored copy that refreshes hourly and when you save the feed.
- Downloading a single event, or attaching one to a form notification, is much faster.
- Conditional logic date filters have a clear button and an improved date picker, and Dynamic Lookup filters use the Lookup plugin's own API when available (Gravity Forms Lookup Field 1.8 or newer).
- Events using "Entry Date (Created)" or "Entry Date (Updated)" were displayed in UTC instead of the site's timezone.
- Entry changes did not reach calendar subscriptions until the stored copy expired. Now, new, edited, and deleted entries update subscriptions immediately.
- Improves support for changes made through GravityView, GravityEdit, GravityRevisions, and GravityImport.
- Deleted, disabled, or regenerated feeds returned a server error instead of reporting that the feed no longer exists.
- Subscription links kept the site's previous domain after a move. Saving the feed now updates the link without breaking existing subscriptions.
- A subscription too large for the server's time limit now properly reports a server error.
- Pressing Enter while editing feed settings regenerated the subscription URL and broke existing subscriptions. The URL now changes only when you click "Regenerate URL".
- 💻 Developer Updates
- Added filters for the stored calendar: `gk/gravitycalendar/ics-export/cache/enabled` (turn it off site-wide or per feed), `gk/gravitycalendar/ics-export/cache/lifetime` (default: one hour), and `gk/gravitycalendar/ics-export/cache/rebuild-timeout` (default: ten minutes).
- 🔧 Updated
- [Foundation]
Versión 2.20.0
- This release adds support for appending `.ics` to calendar subscription links and fixes subscribed calendars duplicating events on every refresh.
- Support for appending `.ics` to the generated calendar subscription link, for calendar applications that only accept URLs ending in `.ics` (existing links continue to work without the suffix).
- Events in a calendar subscription received a new identifier on every refresh, causing subscribed calendars to re-add all events on each sync instead of updating the ones they already have.
- 🔧 Updated
- [Foundation]
Versión 2.19.0
- This release removes an unnecessary database query from every calendar load and makes the event limit work correctly on calendars that read their events from the database.
- ✨ Improved
- Removed an unnecessary database query that ran, and returned no results, every time a calendar's events were loaded.
- Setting the event limit to a negative value now means "no limit", as it does elsewhere in WordPress, instead of dropping the last event.
- The warning logged when the event limit is reached now appears only when entries were actually left out, not when the number of events merely equals the limit.
- 💻 Developer Updates
- The `gravityview/calendar/settings/total-event-limit` filter now applies to events read from the database, where it previously had no effect. The limit defaults to unlimited for database entries, so calendars without a filter callback display exactly as before — but a callback returning a positive number now takes effect on those calendars. Events supplied through the `gravityview/calendar/events/source_data` filter still default to 1000. The limit counts only events the calendar displays, so it is never spent on entries that other filters remove.
- 🔧 Updated
- [Foundation]
Notas de versión publicadas por el desarrollador.
Cómo instalar
Actualización automática: este ítem se actualiza con el Ultrapack Auto Updater. Con él instalado, la versión nueva aparece en tu panel como cualquier otra actualización de WordPress (cómo configurarlo).
- Descarga el archivo
gravityview-calendar.zip. - En el panel de WordPress, ve a Plugins > Añadir nuevo > Subir plugin.
- Selecciona el archivo
gravityview-calendar.zipy haz clic en Instalar ahora. - Haz clic en Activar.
Requisitos: Requiere WordPress 5.6 o superior y PHP 7.4 o superior. Probado hasta WordPress 7.1.
¿Te trabaste en algún paso? Abre un ticket diciendo en cuál te detuviste.

UAU Ready