UAU Ready
Descrição
O GravityView transforma entradas do Gravity Forms em listagens públicas no front-end do WordPress, exibindo submissões como diretórios, perfis de membros, anúncios imobiliários ou catálogos de negócios. O complemento adiciona um editor drag and drop ao admin para escolher quais campos aparecem em cada visualização, define filtros de pesquisa para o visitante e habilita edição de entradas pelo próprio autor diretamente na página renderizada.
Características Principais
- Editor visual de campos
Monta cada View arrastando os campos do formulário pra layouts pré-construídos. - Layouts prontos para uso
Inclui modelos de tabela, lista, mapa, DataTables e visão única por entrada. - Pesquisa e filtros no front-end
Adiciona barra de busca, filtros por campo e ordenação configuráveis pelo visitante. - Edição de entradas pelo autor
Permite que o usuário logado edite ou apague sua própria submissão na página pública. - Controle de acesso por papel
Restringe visualização, edição e exclusão de entradas conforme o papel do usuário no WordPress.
Benefícios do GravityView
- Sites orientados a dados sem código
Cria diretórios, classificados e listagens reaproveitando formulários que já existem. - Conteúdo gerado por usuários no ar
Aceita submissões do público e publica imediatamente sob regras de moderação configuráveis. - Reuso do investimento em Gravity Forms
Aproveita campos, lógica condicional e notificações já configuradas no formulário original. - Áreas de membros com dados próprios
Cada usuário enxerga e mantém apenas as entradas que enviou, sem plugin extra.
Para Quem é Indicado?
- Agências que entregam portais de diretório, classificados ou listagens imobiliárias sobre WordPress.
- Sites de associações, clubes e comunidades que mantêm cadastro público de membros e profissionais.
- Profissionais que já usam o Gravity Forms e querem publicar as submissões como conteúdo navegável.
Dentro do ecossistema GravityKit, o GravityView é o componente que cobre a ponta de exibição: enquanto o Gravity Forms cuida da coleta, este addon assume a renderização pública, a busca e a edição contextual das entradas. O resultado prático é encurtar o caminho entre receber um cadastro e ter uma página de diretório no ar, sem desenvolvimento sob medida.
Perguntas Frequentes
O plugin GravityView é GPL?
Sim. O GravityView é 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 GravityView em mais de um site?
Sim. Você pode instalar o GravityView em quantos sites quiser. Só as atualizações automáticas pelo Ultrapack Auto Updater têm limite: de 3 a 80 sites, conforme o plano.
Quanto custa o plugin GravityView no Ultrapack?
O GravityView sai por R$ 14,90 na compra avulsa, e também está incluído nos planos de assinatura a partir de R$59/mês (VIP I).
O plugin GravityView inclui atualizações?
Sim. A versão atual do GravityView é a 3.6.0, publicada no Ultrapack em 02/10/2026. Assinantes atualizam direto do painel do WordPress com o UAU (Ultrapack Auto Updater).
O plugin GravityView é seguro para baixar e instalar no meu WordPress?
Sim. Cada versão do GravityView passa por varredura de malware (ClamAV e regras YARA, no UltraHub) antes de ser publicada.
Quais são os requisitos do plugin GravityView?
Requer WordPress 4.7 ou superior e PHP 7.4.0 ou superior. Testado até o WordPress 7.1.1.
O que mudou nesta versão
Versão 3.6.0
- This update makes removing files in Edit Entry safer, includes security fixes, and resolves issues with Edit Entry, Populate Anything fields, search, and View layouts. We recommend updating.
- Note: GravityView now requires Gravity Forms 2.9.4 or newer.
- ✨ Improved
- File removal in Edit Entry, which now takes effect only after clicking Update (leaving the page without updating keeps the files).
- 🔒 Security
- Improved security when deleting uploaded files in Edit Entry.
- Fixed a data disclosure issue in Edit Entry, limited to users already allowed to edit the entry.
- The "Hide View data until search is performed" setting did not hide entries from the REST API, CSV and TSV exports, or `[gravityview detail]` counts, and blank searches or searches on fields the View did not offer still showed entries.
- Issues with choice fields populated by Populate Anything
- Saving an entry in Edit Entry changed or erased choices beyond the first 501, the default maximum Populate Anything loads
- Inline editing with GravityEdit did not offer saved choices that were not among the loaded choices, so saving erased them
- Merge tags used outside Custom Content fields showed the stored value instead of the label
- Custom entry slugs built from these fields switched between the stored value and the label (they now always use the label).
- Issues in Edit Entry
- Conditional logic restored the wrong value to a dynamically populated field whose parameter name matched an entry property, such as `ip`
- Calculation fields stopped updating after the first save when the entry had no stored value for them
- With Gravity Forms 3.1.2, files uploaded to a multi-file field were rejected when the form was resubmitted after a validation error
- Multi-file upload errors showed "Array" instead of the message for each file.
- Gravity Flow assignees could not delete uploaded files on User Input steps while GravityView was active.
- DataTables column filters had no effect after updating to GravityView 3.5.0.
- View settings added by add-ons, such as GravityMath's Calculation Row Background, went missing from the View editor in GravityView 3.0.
- Search Bar widget issues
- A large gap appeared between each search field and the Search button in the Horizontal layout on Views not using the Vantage theme
- Labels for radio, checkbox, date, date range, and number range fields ignored the theme's label styling and appeared at body text size
- Searches that did not specify a search mode ignored the Search Mode saved on the View and matched any field.
- Layout issues
- List and Layout Builder Views set to more than one column showed every entry in the first column
- Entries in Vantage Layout Builder Views lost the space between them
- Vantage Table Views grew wider than the page when a field held long text instead of wrapping it within the column widths.
- 💻 Developer Updates
- Deprecated `GravityView_Edit_Entry::delete_file` and removed GravityView's handler for the `rg_delete_file` AJAX action, since Edit Entry now deletes removed files when the entry is updated.
- 🔧 Updated
- [Foundation]
Versão 3.5.0
- This release adds default values for Search Bar fields, improves screen reader navigation, and fixes several search, sorting, and display issues.
- Note: GravityView now requires WordPress 6.5 or newer.
- Default Value setting for Search Bar fields, which pre-fills the field and filters the View until a visitor searches, offering a picker of choices for fields that have them.
- "No value" option setting for radio button search fields, adding a choice that clears the field since radio buttons cannot otherwise be deselected.
- ✨ Improved
- Screen reader navigation
- The Search Bar is a search landmark, the entries are a named region, and the View title names both
- Pagination arrows and First/Last links have accessible names
- Radio, checkbox, date, date range, and number range Search Bar fields announce their field name, which screen readers previously skipped
- Links search fields read as a named list of choices, announcing the field name and the active option.
- Readable query keys in search, sort, and pagination links (for example, `sort[3]` rather than `sort%5B3%5D`).
- Vantage theme styling of DataTables Views: pagination buttons match the rest of GravityView, the page-length control sits at the end of the toolbar, and focus outlines are fully visible.
- 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.
- Issues in Views that combine entries from multiple forms ([Multiple Forms]( extension)
- A Search Bar field from a joined form searched the View's main form instead, matching the wrong entries or none at all
- Filters on a joined form's fields did not work with relative dates such as "yesterday"
- Sorting by a field did nothing on sites running Gravity Forms older than 3.0.0.1.
- Vantage theme issues in the Search Bar
- A single-checkbox search field showed its checkbox below the field name instead of beside it
- Fields in the Advanced Search section ignored the Search Bar's grid, losing their column widths, spacing, and single-column layout on mobile.
- Choosing an option in a Links search field cleared the other search fields' values.
- Views added to a block theme's template or template part through the Site Editor were not recognized as part of the page.
- The `:diff` merge tag modifier (for example, `{date_created:diff}`) was off by the site's UTC offset, so an entry created two hours ago could show as "2 hours from now".
- A `form:` merge tag showed a value from the main form when the target form no longer had that field.
- Filters 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.
- 💻 Developer Updates
- Added the `GET /wp-json/gravityview/v1/views/{view_id}/refresh` endpoint, used by GravityKit layouts and extensions to fetch a View's entries, entry total, and page window for a given query, and enabled per layout with the `gk/gravityview/view/refresh/live` filter (documented in `docs/view-refresh.md`).
- Added sorting by a joined form's field on any layout with a `sort[ : ]` URL parameter, ignoring keys that name a form the View does not join.
- Search Bar fields from a joined form now render the matching `filter_ : ` key.
- The `gk/gravityview/view/entries/query/sorting-parameters` filter now provides a `form_id` key on each sorting parameter, identifying the form the sort column belongs to.
- Added the `gk/gravityview/view/output` filter to modify a View's fully rendered HTML before it is returned.
- Added the `gk/gravityview/search/field/default-value` filter to provide or override a Search Bar field's default value.
- The `{gv_entry_link}` merge tag wrote a deprecation notice to the debug log every time it rendered.
- Search Bar fields that hold a group of inputs (radio, checkbox, chained select, date, date range, number range, and entry date) now render as ` ` with a ` ` instead of a ` ` with a ` `
- Class names, IDs, input names, and the per-choice `.gv-check-radio` labels are unchanged
- Custom CSS works with both versions when it leaves the element name off the class (`.gv-search-box`, not `div.gv-search-box`) and targets both field-name elements (`.gv-search-box > label, .gv-search-box > legend`).
- 🔧 Updated
- [Foundation]
Versão 3.4.0
- This release strengthens the "Prevent Direct Access" setting and fixes several Single Entry, Edit Entry, Custom CSS, and merge tag issues.
- ✨ Improved
- Views with "Prevent Direct Access" enabled now return a "not found" page at their own URL and are excluded from the WordPress sitemap, feeds, archives, and previous/next links, while still working wherever they are embedded and remaining accessible to administrators and editors.
- The Edit Entry, Delete Entry, and Duplicate Entry link fields did not appear on a user's own Single Entry when that entry was not on the View's first page.
- Single Entry pages in Views with joined forms ([Multiple Forms]( extension) showed "You are not allowed to view this content." when an Entry Slug was set.
- Long column headings in Table Views using the Vantage theme did not wrap, overlapping the next column.
- Custom CSS and Vantage theme styling did not apply in several places
- Custom CSS on Views using the Vantage theme had no effect on the Single Entry page unless it used `VIEW_SELECTOR`
- Custom CSS written with `VIEW_SELECTOR` or `VIEW_WRAPPER`, and Custom CSS on Views using the Vantage theme, had no effect on the Edit Entry page
- The Vantage theme's typography and style settings did not apply to the Edit Entry page.
- The `{now}`, `{yesterday}` and `{tomorrow}` merge tags showed the wrong time on sites not set to UTC, and did not return UTC when the `:no_tz_offset` modifier was used.
- The `gravityview/template/field/label` filter had no effect on field labels on the [Maps]
- 💻 Developer Updates
- New `gk/gravityview/view/output/direct/404` filter to show the previous message page instead of a "not found" response when a View that prevents direct access is visited at its own URL (return `false`).
- The Edit Entry wrapper (`.gv-edit-entry-wrapper`) now also carries the `gv-container gv-container-{View ID}` classes and a `gv-view-{View ID}-edit-{Entry ID}` id.
Versão 3.3.5
- This update restores Address field Country searching and fixes merge tag pickers in the View editor, both broken by changes in recent Gravity Forms releases.
- A View setting supplied by an add-on could place unfiltered markup in the View editor.
- The View editor showed every merge tag picker open and unstyled on Gravity Forms 3.1.1 and newer.
- Address field Country issues
- Searching by country returned no entries submitted since Gravity Forms 3.0.3, which stores the country as its two-letter code
- The Country input added to a View on its own showed the code (for example, "PR") instead of the country name
- Searching Country matched every country whose name contains what was searched, so "US" also returned entries from Australia and Austria.
- 🔧 Updated
- [Foundation]
Versão 3.3.4
- This release fixes an incompatibility with Gravity Flow on Gravity Forms 3.0 and newer, improves accessibility of the Entry Approval chooser, and includes many other fixes.
- Edit Entry could not be submitted on Gravity Forms 3.0 and newer when Gravity Flow was active: clicking Update or Next did nothing, with no error and no changes saved.
- A search field's Input Type and other field-specific settings disappeared from its settings window after saving the View until the field was removed and re-added. This affected fields added from your form, including the Gravity Flow workflow fields.
- Edit Entry logged an "Unsupported submission flow detected" warning to the browser console every time it was displayed.
- The Entry Approval field could show and change another form's entry in Views with joins using the [Multiple Forms]
- Entry Approval buttons showed HTML code instead of the approve, disapprove and reset icons when another plugin loaded its own copy of the Tippy tooltip library.
- GravityView's bundled Tippy and Popper libraries broke tooltips in other plugins that bundle their own copies.
- Searching by entry creator on a page showing more than one View could search using another View's settings, returning the wrong entries.
- The Approval Status chooser is now fully usable with a keyboard and a screen reader, in the Gravity Forms Entries list and in Views on your site alike
- Press Enter or Space on an entry's approval button to open the chooser, the arrow keys to move between Approve, Disapprove and Reset Approval, and Enter or Space to choose one. Escape or Tab closes it and returns you to the approval button
- A screen reader now says which status an entry is set to, and reports the new status once it changes
- Opening the chooser with the keyboard no longer jumps the page to the bottom, leaving the chooser and its entry off screen
- The approval button and the three options are now large enough to be a comfortable target on a touch screen.
- The approval status chooser did not work in a DataTables View until the table was redrawn by sorting or paging.
- 💻 Developer Updates
- Added the `gk/gravityview/edit-entry/form-tag` filter, which modifies the opening ` ` tag of the Edit Entry form.
- Removed the `gravityview_entries_list-popper` and `gravityview-field-approval-popper` script handles. The bundled tooltip library includes Popper, so the separate file was never used.
- 🔧 Updated
- [Foundation]
Notas de versão publicadas pelo desenvolvedor.
Como instalar
Atualização automática: este item é atualizado pelo Ultrapack Auto Updater. Com ele instalado, a versão nova aparece no seu painel como qualquer outra atualização do WordPress (como configurar).
- Baixe o arquivo
gravityview.zip. - No painel do WordPress, vá em Plugins > Adicionar novo > Enviar plugin.
- Selecione o arquivo
gravityview.zipe clique em Instalar agora. - Clique em Ativar.
Requisitos: Requer WordPress 4.7 ou superior e PHP 7.4.0 ou superior. Testado até o WordPress 7.1.1.
Travou em algum passo? Abra um chamado dizendo em qual deles parou.
