UAU Ready
Descripción
GravityView transforma entradas de Gravity Forms en listados públicos en el front-end de WordPress, mostrando envíos como directorios, perfiles de miembros, anuncios inmobiliarios o catálogos de negocios. El complemento añade un editor drag and drop al admin para elegir qué campos aparecen en cada vista, define filtros de búsqueda para el visitante y habilita la edición de entradas por el propio autor directamente en la página renderizada.
Características Principales
- Editor visual de campos
Arma cada View arrastrando los campos del formulario a layouts preconstruidos. - Layouts listos para usar
Incluye plantillas de tabla, lista, mapa, DataTables y vista única por entrada. - Búsqueda y filtros en el front-end
Añade barra de búsqueda, filtros por campo y ordenación configurables por el visitante. - Edición de entradas por el autor
Permite que el usuario registrado edite o elimine su propio envío en la página pública. - Control de acceso por rol
Restringe visualización, edición y eliminación de entradas según el rol del usuario en WordPress.
Beneficios do GravityView
- Sitios orientados a datos sin código
Crea directorios, clasificados y listados reutilizando formularios que ya existen. - Contenido generado por usuarios en línea
Acepta envíos del público y publica inmediatamente bajo reglas de moderación configurables. - Reutilización de la inversión en Gravity Forms
Aprovecha campos, lógica condicional y notificaciones ya configuradas en el formulario original. - Áreas de miembros con datos propios
Cada usuario ve y mantiene solo las entradas que envió, sin plugin adicional.
¿Para Quién Está Indicado?
- Agencias que entregan portales de directorio, clasificados o listados inmobiliarios sobre WordPress.
- Sitios de asociaciones, clubes y comunidades que mantienen registro público de miembros y profesionales.
- Profesionales que ya usan Gravity Forms y quieren publicar los envíos como contenido navegable.
Dentro del ecosistema GravityKit, GravityView es el componente que cubre la punta de exhibición: mientras Gravity Forms cuida la recopilación, este addon asume la renderización pública, la búsqueda y la edición contextual de las entradas. El resultado práctico es acortar el camino entre recibir un registro y tener una página de directorio en línea, sin desarrollo a medida.
Preguntas frecuentes
¿El plugin GravityView es GPL?
Sí. GravityView 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 GravityView en más de un sitio?
Sí. Puedes instalar GravityView 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 GravityView en Ultrapack?
GravityView 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 GravityView incluye actualizaciones?
Sí. La versión actual de GravityView es la 3.5.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 GravityView en mi WordPress?
Sí. Cada versión de GravityView pasa por un análisis de malware (ClamAV y reglas YARA, en UltraHub) antes de publicarse.
¿Cuáles son los requisitos del plugin GravityView?
Requiere WordPress 4.7 o superior y PHP 7.4.0 o superior. Probado hasta WordPress 7.1.1.
Qué cambió en esta versión
Versión 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]
Versión 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.
Versión 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]
Versión 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]
Versión 3.3.3
- This release fixes multiple minor View editor problems that could lose your widgets or your most recent changes, and cleans up field settings that showed up where they do not apply.
- 🔒 Security
- Hardens how the Support Port identifies you to our support system.
- Issues in the View editor
- Updating a View before the Widgets area fully loaded removed the View's configured widgets
- Checking one of two mutually exclusive field options, such as opening a link in a lightbox or in a new window, left the other option checked, so both were saved
- Changes made after a save that another plugin interrupted were missing from the next save
- Field settings added by other plugins under their own grouping did not appear in the field settings dialog.
- The "Open in a lightbox?" and "Open link in a new tab or window?" field settings appeared when configuring Single Entry and Edit Entry fields, where they do nothing.
- URLs entered with a leading space were rejected as invalid.
- Fields with a Custom CSS Class were missing the separator line above them on single entry screens using the Layout Builder layout.
- 💻 Developer Updates
- Added the `gravityview/merge-tags/setup` JavaScript trigger, fired on `document.body` before GravityView sets up Merge Tag autocomplete in the View editor. Handlers get the textarea and the `wp.codeEditor` instance, and can call `preventDefault` to take over the field with their own merge tag picker.
- 🔧 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.zip. - En el panel de WordPress, ve a Plugins > Añadir nuevo > Subir plugin.
- Selecciona el archivo
gravityview.zipy haz clic en Instalar ahora. - Haz clic en Activar.
Requisitos: Requiere WordPress 4.7 o superior y PHP 7.4.0 o superior. Probado hasta WordPress 7.1.1.
¿Te trabaste en algún paso? Abre un ticket diciendo en cuál te detuviste.
