[Resolved] Visual Composer + AJAX Filters

[Author]

Posts

[Scott Poliseno]

Whenever Visual Composer is used inside views, alongside AJAX search filters (hidden link) -- then the official response from WP Types has been "this is unsupported" -- because the admin-ajax.php file returns a string of raw, uninterpreted visual composer shortcodes as the AJAX response.

I searched through many threads and they all had that same "official" response. However, someone posted this little bit of code that fixes the problem for me:

if ( is_admin() ) {
add_action('init', function() {
WPBMap::addAllMappedShortcodes();
});
}

I hope you guys integrate this little bit of code into WP Types and save a lot of people a lot of headache.

[Beda]

I am aware of this issue, and as far I know it is not entirely due to Toolset.

To be sure we speak about the same issue, please check this ticket:
https://toolset.com/forums/topic/visual-composer-image-grid-not-showing/

VC tries to render the grid short codes via an AJAX call, which assumes that the grid ID is stored in a post meta, attached to the current page.
While, when using VC with Content Templates, the grid ID is saved with Content Templates's post meta.

So, it requires to hijack the AJAX call and replace the ID with a correct ID of the attached content template.

The main problem here is that VC stores some modules data in the relevant post postmeta.

When a Content Template uses VC, it follows the same pattern: the grid metadata is stored in the Content Template postmeta.
However, when rendering the post in the frontend, the current post (and this is also the one that gets passed on AJAX operations like this one to render a grid) is supposed to store that postmeta data, which it does not.

So, long story short, when using VC on a Content Template, some VC modules require that the current post they manage is the actual current post (for example, on modules for post author, etc etc), and other modules require that the current post is the Content Template involved (like this grid one).

Each module has its own data and rendering management, so what we will need here is a filter on that current post ID on at least all the modules that store and work over data stored in the Content Template.

We are aware of the issues and we are trying to find the best solution together with VC.