Advanced Views Docs
Live PlaygroundDownload PluginGet PRO
  • πŸ’‘Help Centre
  • ⚑Getting Started
    • Introduction
      • Key Aspects
      • Creating Your First View
      • Creating Your First Card
      • Plugin Terms
      • Plugin Interface
        • Field Options
    • Installation
      • Advanced Views Lite
      • Advanced Views Pro
      • Comparison Table
      • Upgrading from Lite to Pro
    • Supported data vendors
    • Starter theme
  • 🌟Display Content
    • WordPress
      • Post
      • Taxonomy terms
      • User
      • Comments
      • Menus
    • WooCommerce Product
    • Meta fields
      • Basic fields
        • Number
      • Content fields
        • Image
        • File
        • WYSIWYG
        • oEmbed
        • Gallery
      • Choice fields
        • Select/checkbox/radio
        • True / False
      • Relationship fields
        • Link
        • Post_object
        • Page Link
        • Relationship
        • Taxonomy
        • User
      • Advanced fields
        • Google Map
        • Google Map Multiple Markers
        • ACF OpenStreetMap Field
        • Date/time picker
      • Layout fields
        • Group (Pro)
        • Repeater (Pro)
        • Flexible (Pro)
    • Object fields
    • Custom Data (Pro)
    • Custom Gutenberg Blocks (Pro)
    • Mount Points (Pro)
    • Front-end assets management (Pro)
  • πŸ¦Έβ€β™‚οΈQuery Content
    • Basic Filters
    • Meta Filters (Pro)
      • Current Post
      • Comparison
      • Dynamic Injection
    • Taxonomy Filters (Pro)
    • Pagination (Pro)
    • Custom Data (Pro)
  • πŸ†Shortcode Attributes
    • Common Arguments
    • View Shortcode
    • Card Shortcode
  • πŸ§™β€β™‚οΈTemplates
    • Customizing the Template
    • Template engines
      • Twig
      • Blade
    • CSS & JS
      • BEM Methodology
      • WordPress Interactivity API
    • File system storage
    • Pre-built components
    • Reusable components library (Pro)
    • Live reload
    • Multilingual
    • Custom Ajax & Rest API (Pro)
  • β˜•Guides
    • Display Custom Post Type (CPT) on another post
    • Display Employees (CPT) of a Company (CPT)
    • Display Nested Repeater Fields
    • Map Marker from ACF Image
    • Display all CPT items on a single map
  • πŸ› οΈTools
    • Export/Import
    • Demo Import
    • Settings
    • Preview
  • 🏹Troubleshooting
    • Compatibility
    • Report a bug
    • Payment Issues
    • Lite Support (Forum)
    • Pro Support
  • βš™οΈCustomization
    • Filters and Hooks
      • View
      • Card
    • Suggest a feature
    • Performance
Powered by GitBook
On this page
  • Get current post ID
  • Compare current post with field value
  • Compare with a query ($_GET) argument
  • Compare with a custom argument
  • Compare date to current date and time
  • Extended support for Post_object and Relationship fields
  • Step by step guide

Was this helpful?

  1. Query Content
  2. Meta Filters (Pro)

Dynamic Injection

PreviousComparisonNextTaxonomy Filters (Pro)

Last updated 1 month ago

Was this helpful?

The value field in the Meta Filter supports dynamic injection. This means you don’t need to use only static values, but have the option to also define page id/field and datetime aliases. These aliases will be replaced dynamically with the current value depending on the page and/or current date and time respectively.

Get current post ID

Note: $post$ will be replaced with the current post id.

Example usage: find all posts where post_object/relationship field contains the current page in the list.

Compare current post with field value

To compare with a field value, you can use $post$.field-name, where 'field-name' should be replaced with the name of your target field. In this way, the plugin will automatically get and use a value of the field from the current page in the query.

Example usage: find all posts where a 'select' field has the same option chosen, as the option chosen on the current page.

Compare with a query ($_GET) argument

To compare with a query ($_GET) value, you can use $query$.field-name, where 'field-name' should be replaced with the name of your target query argument. In this way, the plugin will automatically get and use a value of the query (url) from the current page in the posts query.

Compare with a custom argument

You can also insert a into the query, making the Card context-dependent. Use $custom-arguments$.field-name to dynamically get the shortcode argument. This allows you to copy the Card shortcode to different places and use different values, like so:

[avf_card custom-arguments="genre=my-slug"]
[avf_card custom-arguments="genre=my-another-slug"]

Note: This method is useful for manually defined cases. If you need to pick it up from the current page metadata, use the $post$ constant described above."

Compare date to current date and time

To compare the value in an ACF Date or an ACF Date/Time field to the current date and time.

Note: $now$ will be replaced with the current date and time the page is viewed. You can also add or remove periods. For example, you can use '$now$ + 1 day' or '$now$ - 1 week'. The following period keys are supported: minute, hour, day, week and month.

Example usage: find all posts where 'date' field value is "Bigger than" current date and time. So as to show only upcoming events in the posts grid or list.

Extended support for Post_object and Relationship fields

Advanced Views Pro supports Post_object and Relationship field types in the Meta filters.

Step by step guide

See the on how to display Employee CPT items on a Company CPT post.

πŸ¦Έβ€β™‚οΈ
custom argument from the shortcode
step by step guide