Descrição
O GravityCalendar exibe entradas do Gravity Forms em uma visualização de calendário, transformando submissões com campo de data em eventos clicáveis nas vistas mensal, semanal e diária. A extensão integra-se diretamente ao GravityView para renderizar agendas, calendários de reservas e cronogramas de compromissos a partir dos dados já coletados pelos formulários, sem exigir plugin separado de eventos ou sincronização externa com serviços como Google Calendar.
Características Principais
- Múltiplas visualizações de calendário
Renderiza as entradas em modos mensal, semanal, diário e lista de agenda. - Mapeamento de campo de data
Vincula qualquer campo de data ou data/hora do Gravity Forms como origem dos eventos. - Cores e categorias por entrada
Permite atribuir cores e rótulos com base no valor de campos do formulário. - Modal de detalhes ao clicar
Abre os dados completos da submissão em popup ou redireciona para a página do GravityView. - Filtros e busca integrados
Aplica filtros do GravityView ao calendário para limitar quais entradas aparecem.
Benefícios do GravityCalendar – Display Entries on a Calendar
- Aproveita dados já existentes
Reutiliza submissões do Gravity Forms sem migração para outro plugin de eventos. - Visualização clara para visitantes
Substitui tabelas e listas longas por um painel mensal de fácil leitura no front-end. - Configuração dentro do GravityView
Reduz curva de aprendizado ao manter todas as opções no mesmo editor da View. - Versatilidade de uso
Cobre reservas, agendamentos, prazos e eventos a partir de um único formulário.
Para Quem é Indicado?
- Sites que coletam reservas, agendamentos ou inscrições via Gravity Forms e precisam exibir os registros publicamente.
- Escolas, igrejas, associações e clubes que mantêm calendários internos de eventos a partir de formulários.
- Equipes que já utilizam o GravityView para listar submissões e desejam adicionar uma camada visual de calendário.
Voltado para quem já estruturou fluxos no Gravity Forms e usa o GravityView para apresentar os dados, este complemento amplia o repertório de layouts disponíveis sem duplicar registros em outro sistema de eventos. O resultado é um calendário front-end alimentado em tempo real pelas próprias submissões, mantendo o controle de filtros, permissões e exibição no mesmo painel administrativo.
O que mudou em cada versão
Versão 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]
Versão 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]
Versão 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]
Versão 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]
Versão 2.18.0
- This release enhances conditional logic filtering, makes the single entry "Go Back" button return to the calendar the event was clicked on, and clears PHP notices that could appear when rendering calendars.
- ✨ Improved
- Calendar events that link to a single entry now remember the page the calendar is on: the "Go Back" button on the Single Entry page returns to the calendar instead of the View's Multiple Entries page, including after editing the entry.
- Enhanced conditional logic
- Choice-based filters now offer a searchable dropdown whose results page in as you scroll, so fields with large option lists stay fast and usable instead of trying to render every choice at once. This covers the standard choice fields (Drop Down, Checkbox, Radio, Multi Select) as well as Dynamic Lookup and Populate Anything fields, which draw their options from large external data sets
- Use a field merge tag (e.g. `{Threshold:2}`) as a filter value to compare two fields of an entry instead of a static value
- Compare against a field on a joined form
- The "has ALL of" operator on checkbox and other multi-value fields matched every entry instead of only those containing all the selected values
- Switching a condition between single-value and multi-value operators could save a mismatched value shape.
- A `_load_textdomain_just_in_time` notice (WordPress 6.7+) appeared because some plugin components loaded translations too early.
- Two `Undefined array key "controls"` PHP notices appeared when rendering a calendar whose feed had no header/footer controls setting saved.
- Internal Ajax parameters (nonce, date range, calendar ID) appeared in single entry links generated by calendars that load events dynamically.
- 🔧 Updated
- [Foundation]
Notas de versão publicadas pelo desenvolvedor.
Perguntas Frequentes
O plugin GravityCalendar – Display Entries on a Calendar é GPL?
Sim. O GravityCalendar – Display Entries on a Calendar é distribuído sob a licença GPL (GNU General Public License). Você pode usar, modificar e redistribuir legalmente, em quantos sites quiser.
Posso usar o plugin GravityCalendar – Display Entries on a Calendar em mais de um site?
Sim. Não há restrição de domínios: você pode instalar o GravityCalendar – Display Entries on a Calendar em quantos sites (domínios) desejar.
Quanto custa o plugin GravityCalendar – Display Entries on a Calendar no Ultrapack?
O GravityCalendar – Display Entries on a Calendar sai por R$ 14,90 na compra avulsa, e também está incluído nos planos de assinatura a partir de R$ 59,00/mês (VIP I).
O plugin GravityCalendar – Display Entries on a Calendar inclui atualizações?
Sim. Cada nova versão do GravityCalendar – Display Entries on a Calendar é sincronizada automaticamente no Ultrapack. Você baixa a última versão quando quiser, e os assinantes atualizam direto do painel do WordPress com o UAU (Ultrapack Auto Updater).
O plugin GravityCalendar – Display Entries on a Calendar é seguro para baixar e instalar no meu WordPress?
Sim, pode baixar com tranquilidade. Cada versão do GravityCalendar – Display Entries on a Calendar é escaneada antes da publicação pelo motor próprio do Ultrapack (UltraHub), que combina ClamAV e regras YARA, tecnologias usadas para detectar malware e código malicioso. Assim você instala no seu WordPress sem preocupação.

UAU Ready