axew3

<p>W3IMAGES FEATURES</p>
<p>Upload single or multiples images.<br />
Unlimited sections and subsections.<br />
Set slide show for images to be displayed on three different ways:</p>
<ol>
<li>Simple js/html popup</li>
<li>Slide in the same page (inline)</li>
<li>Shadowbox ajax mode</li>
</ol>
<p>All control over images gallery can be done from administration while any user (or specified users group you need)<br />
can upload images on any section. Moderation provided for images (enable or disable) and more features</p>
<h3>Upgrade</h3>
<ol>
<li>To upgrade the w3images plugin, simply upload all files to respective folders<br />
overwriting old files with latests where necessary. Remember that to let work the<br />
w3images plugin after 1.0.4 version with the ‘ajax Shadowbox’ slideshow instead of js/html popup or inline gallery,<br />
it is necessary to add few lines of code as reported in the ‘w3images how to use page’:<br />
http://www.axew3.com/b10g/w3images-for-wordpress-how-to-use-it/</li>
</ol>


w3images

The w3images, Images Gallery for WordPress.

BrightLeaf Digital

<p>GravityOps Search is a free, powerful shortcode for searching Gravity Forms entries on the front end and displaying the matching results anywhere on your site. Instead of paging through the admin entries screen, you can drop a single shortcode into a page, post, GravityView, or custom template and surface exactly the data you need. It works like an Excel-style lookup for Gravity Forms entries: you define which forms and fields to search, how to compare the values, and what to output for each match.</p>
<p>The core <code>[gravops_search]</code> shortcode lets you target one form, several forms, or even all forms at once. You can filter by one field or many, pass in values directly in the shortcode content, and control whether entries must match all conditions or any of them. The same shortcode can handle simple lookups (showing a single field from the latest matching entry) or more complex reporting-style views that combine fields, entry properties, and custom HTML. Because everything is driven by attributes, you stay in full control of which entries are included and how their data appears on the front end.</p>
<p>Results are rendered through a flexible <code>display</code> attribute, which understands both simple comma-separated field lists and advanced custom display strings with placeholders. You can output raw values, mix multiple fields into labeled text, or construct HTML lists, tables, and cards with links, CSS classes, and nested shortcodes. This gives you a fully custom front-end listing of Gravity Forms entries that you can drop into any layout, theme, or builder, without building a custom query or touching PHP.</p>
<p>GravityOps Search fully supports Gravity Forms entry properties (such as entry ID, form ID, created-by, and more) alongside regular fields, and it includes options for sorting, limiting, and deduplicating results before they are rendered. You can sort by field values or entry properties, choose ascending, descending, or random ordering, add a secondary sort key, and request unique values only. When no entries match, you can show fallback text or per-field default values, so front-end visitors never see a broken layout or confusing blank output.</p>
<p>This plugin is built explicitly for front-end entry search and display. It does not add live search tools to the Gravity Forms admin area and does not replace the Entries screen. Instead, it focuses on one thing and does it well: querying Gravity Forms entries in the background and printing clean, formatted results on the pages your users actually see.</p>
<h3>Features</h3>
<ul>
<li>Front-end search for Gravity Forms entries using a single, flexible shortcode.</li>
<li>Target all forms, a single form, or a comma-separated list of form IDs using the <code>target</code> attribute.</li>
<li>Filter entries by a comma-separated list of field IDs or entry properties via the <code>search</code> attribute.</li>
<li>Pass search values in the shortcode content, separated by a pipe (<code>|</code>) to match positions with the fields in <code>search</code>.</li>
<li>Choose whether entries must match all search conditions (default) or any condition by setting <code>search_mode=\"any\"</code>.</li>
<li>Use the <code>operators</code> attribute to control how each value is compared to its field, with support for equals, not-equals, partial matches, SQL-style <code>LIKE</code>, “in” / “not in” arrays, and numeric comparisons (greater than / less than / greater-or-equal / less-or-equal).</li>
<li>Display one or many fields and properties for each result using the <code>display</code> attribute, which supports both simple lists and rich custom templates.</li>
<li>Include entry properties and field values in your output using placeholder formats like <code>{13}</code>, <code>{id}</code>, <code>{form_id}</code>, and <code>{gos:id}</code> where appropriate.</li>
<li>Build fully custom HTML output (lists, tables, cards, badges, buttons, links) directly inside the <code>display</code> string.</li>
<li>Insert CSS classes and inline markup into the output so results adopt your theme’s design and layout patterns.</li>
<li>Use the <code>separator</code> attribute to control how multiple entry results are separated (including HTML separators or no separator at all using <code>__none__</code>).</li>
<li>Sort entries using <code>sort_key</code>, <code>sort_direction</code>, and <code>sort_is_num</code>, with optional <code>secondary_sort_key</code> and <code>secondary_sort_direction</code> for tie-breaking.</li>
<li>Limit the number of results returned with <code>limit</code>, including support for <code>limit=\"all\"</code> when you need to show every matching entry.</li>
<li>Turn on <code>unique</code> to return only unique result values, great for building deduplicated lists such as unique email addresses, user IDs, or other fields.</li>
<li>Search for empty or blank values with the <code>search_empty</code> attribute and an empty shortcode content, to find incomplete or missing data.</li>
<li>Provide fallback values when no entries match—or when individual fields are empty—using the <code>default</code> attribute.</li>
<li>Add an admin link to each result with the <code>link</code> attribute so power users can jump directly from the front end to the entry in the Gravity Forms admin.</li>
<li>Designed to work smoothly alongside GravityView, GravityMath, and other shortcodes that can be nested inside the output.</li>
<li>Compatible with the legacy <code>gfsearch</code> snippet approach while offering ongoing updates and a more robust, plugin-based implementation.</li>
</ul>
<h3>How It Works</h3>
<p>At its core, GravityOps Search evaluates your shortcode attributes and content to determine which entries to fetch, then formats each matching entry according to the <code>display</code> string you provide. The <code>target</code> attribute defines which forms to query: pass <code>0</code> to search all forms, a single form ID to target one form, or a comma-separated list of IDs for multi-form searches. The <code>search</code> attribute specifies the field IDs and entry properties to filter on, and the shortcode content supplies the corresponding values, separated by the pipe (<code>|</code>) character in the same order.</p>
<p>You can configure the <code>search_mode</code> attribute to determine matching logic. The default mode (<code>all</code>) requires each entry to satisfy all conditions, while <code>search_mode=\"any\"</code> returns entries that meet at least one of the conditions listed. This gives you the flexibility to build both strict, multi-field filters and more permissive, keyword-style searches. If you need to perform a global search across all fields for a given value, you can leave the relevant search ID blank, and the plugin will look for that value anywhere in the entry.</p>
<p>Sorting, limiting, and uniqueness are handled after the search conditions are applied. You can specify a <code>sort_key</code> (field ID, entry property, or meta key) with <code>sort_direction</code> set to <code>ASC</code>, <code>DESC</code>, or <code>RAND</code>. If you are sorting by numeric data, <code>sort_is_num</code> ensures values are compared correctly rather than as plain strings. When you need a consistent secondary ordering—such as sorting first by date and then by name—you can use <code>secondary_sort_key</code> and <code>secondary_sort_direction</code>. Once ordered, the plugin applies the <code>limit</code> attribute to control how many entries are actually returned and optionally filters down to unique results based on the full rendered output when <code>unique</code> is enabled.</p>
<p>Defaults and fallbacks keep your front-end output robust. The <code>default</code> attribute can define text to display when no entries are found or when specific fields are empty, and the plugin can handle multiple default values mapped to multiple display fields. The <code>separator</code> attribute governs how multiple entries are joined, making it easy to build line-separated lists, HTML <code>elements, or table rows. Because each [gravops_search]</code> shortcode runs its own live database query, you can place different instances around your site to build different views of the same underlying Gravity Forms data.</p>
<h3>Display and Formatting</h3>
<p>The <code>display</code> attribute is the heart of how results are shown. In its simplest form, you can pass a comma-separated list of field IDs or entry properties, such as <code>display=\"13,14,15\"</code>. For each matching entry, GravityOps Search outputs those values in order, using sensible default separators between fields and entries. This mode is ideal when you simply need to surface raw values: a quick list of email addresses, a set of IDs, or basic single-column output.</p>
<p>For more control, <code>display</code> supports custom display strings with placeholders. Instead of a list of IDs, you can provide a template like <code>display=\"Name: {13}, Email: {14}\"</code>, which will be rendered for each matching entry. Placeholders like <code>{13}</code> insert the value of field 13, while placeholders such as <code>{id}</code> and <code>{form_id}</code> work with entry properties. When you need to reference non-numeric properties or use merge tags in contexts that parse standard tags (such as GravityView content fields, confirmations, or notifications), you can use the special <code>{gos:id}</code> syntax. This gives you a consistent way to assemble complex messages, labels, and markup that incorporate both field data and meta data.</p>
<p>The <code>display</code> attribute also accepts full HTML, including tags, attributes, and CSS classes. You can wrap values in <code>,</code>, <code>,</code>, “, or any other markup to build lists, tables, cards, or media objects. Because the <code>separator</code> attribute supports HTML as well, you can structure your markup so that each entry becomes one list item, table row, or card component. This makes it straightforward to integrate entry results into existing sections of your design, matching your theme and layout without a custom PHP query.</p>
<h3>Nesting Shortcodes and Advanced Templates</h3>
<p>GravityOps Search supports nesting other shortcodes inside the <code>display</code> attribute via a double-curly-brace syntax: <code>{{ ... }}</code>. This means you can embed tools like GravityMath, another <code>gravops_search</code>, or any other shortcode directly inside the output template for each entry. The outer <code>[gravops_search]</code> processes its own placeholders first and then hands the rendered string to the nested shortcodes, allowing you to feed entry values into calculations, secondary lookups, or formatting helpers.</p>
<p>When you nest a second <code>gravops_search</code> inside the <code>display</code> attribute, each shortcode runs its own search and display logic in sequence. The outer shortcode resolves placeholders such as <code>{13}</code> and <code>{gos:id}</code> in its <code>display</code> string, while the nested shortcode uses its own <code>display</code> template and attributes. In nested scenarios where you need to reference placeholder values as input to another shortcode or formula, you can use the <code>gos:id</code> pattern without braces (for example, <code>gos:21</code>) to avoid conflicts with merge-tag parsing. This lets you do things like passing a field value into a GravityMath filter or dynamically controlling filters and IDs inside the nested shortcode configuration.</p>
<p>Because nested shortcodes are fully supported and the plugin respects all standard shortcode attributes, you can construct sophisticated, layered outputs without custom PHP. For example, you can build a front-end summary that uses one <code>[gravops_search]</code> to list matching entries, another to pull related entries, and a GravityMath shortcode to compute totals—all wrapped in your own HTML structure. GravityOps Search handles placeholder substitution and nested processing order so that each piece of your template receives the data it needs at the right time.</p>
<h3>Search Operators and Multi-Input Fields</h3>
<p>The <code>operators</code> attribute lets you tell GravityOps Search exactly how to compare each search value against its corresponding field or property. You define a comma-separated list of operators that line up with the IDs in the <code>search</code> attribute. Supported operators include equality (<code>=</code> or <code>is</code>), inequality (<code>!=</code>, <code>isnot</code>, <code>is not</code>), partial matches (<code>contains</code>), SQL-style wildcard matches (<code>like</code>), membership tests (<code>in</code>, <code>not in</code>), and numeric comparisons (<code>gt</code>, <code>lt</code>, <code>gt=</code>, <code>lt=</code>). If you provide fewer operators than search fields, remaining fields default to exact matches; extra operators beyond the number of fields are ignored. When you omit <code>operators</code> entirely, all fields use exact matching by default.</p>
<p>For more advanced scenarios, certain operators expect specific value formats. When using <code>in</code> or <code>not in</code>, for example, you can pass a PHP-style array in the shortcode content—such as <code>array(\'item one\',\'item two\',\'item three\')</code>—to test whether the field value appears in that list. This makes it easy to filter entries against multiple acceptable values for a single field without duplicating field IDs. Combined with <code>search_mode</code>, you can express a wide range of conditions: from strict multi-field comparisons to flexible multi-value lists and keyword-style filters.</p>
<p>Multi-input Gravity Forms fields (like Name, Address, and Checkbox fields) are fully supported, but they behave differently for display versus search. When displaying, using the base field ID in a placeholder (e.g., <code>{13}</code>) automatically combines all sub-inputs (such as first name and last name) into a single string separated by spaces. If you need to display a specific sub-input—like first name only—you can use its input ID directly, for example <code>{13.3}</code>. When searching, checkboxes are best handled by searching the base field ID so that changes to individual options or dynamic checkboxes do not break the search. Other multi-input fields (like Name and Address) should be searched using their individual input IDs (e.g., <code>13.3</code>, <code>13.6</code>), as searching by the base ID will not work for those types.</p>
<h3>Performance and Access Control</h3>
<p>Every <code>[gravops_search]</code> shortcode runs a live database query against Gravity Forms entries, so thoughtful usage is important for both performance and privacy. On the performance side, heavy use of <code>limit=\"all\"</code>, many nested shortcodes, and large forms with complex conditions can slow down page loads. To keep pages responsive, it is recommended to set a reasonable <code>limit</code> where possible, minimize unnecessary nesting, and consider caching the rendered page output using your preferred caching plugin or server-level caching tools. These simple steps help ensure that even data-heavy views remain fast and reliable.</p>
<p>On the access-control side, the shortcode does not enforce any special permission checks by itself. Anyone who can view the page where the shortcode is placed will be able to see whatever Gravity Forms entry data you choose to display, including potentially sensitive information. To protect private or restricted data, you should place the shortcode inside pages or templates that are protected by membership plugins, password protection, role-based visibility, or other gating mechanisms. This keeps the plugin flexible and focused on data retrieval and formatting, while allowing you to decide how and where to expose entry data based on your site’s security model.</p>
<p>GravityOps Search is designed to be both powerful and predictable: you define the forms, fields, filters, and display template, and the plugin takes care of querying and rendering. Used thoughtfully, it becomes a core tool for building dynamic, entry-driven front-end experiences on top of Gravity Forms, without custom development or complex integrations.</p>


GravityOps Search – Search and Display Gravity Forms Entries

Search Gravity Forms entries on the front end and display matching results anywhere. Filter by any field value. Output custom formatted data.

w3images vs GravityOps Search – Search and Display Gravity Forms Entries