Problem:
The user was encountering the following PHP notice on his website: Notice: ob_end_flush(): failed to send buffer of zlib output compression (0)
By adding the following code to theme's functions.php
/**
* Proper ob_end_flush() for all levels
*
* This replaces the WordPress `wp_ob_end_flush_all()` function
* with a replacement that doesn't cause PHP notices.
*/
remove_action( 'shutdown', 'wp_ob_end_flush_all', 1 );
add_action( 'shutdown', function() {
while ( @ob_end_flush() );
} );
isplay a post form to create a post, in a Bootstrap modal,
the dropdown select was limited to 10 entries and the search facility does not function in Firefox browser.
jQuery(document).on( 'cred_form_ready', function($) {
// ALL YOUR CRED form JS code goes here. Add your JS code here
jQuery.fn.modal.Constructor.prototype.enforceFocus = function() {}
});
The issue here is that the user is getting the fatal error
An error of type E_PARSE was caused in line 66 of the file /XXX/wp-content/plugins/wp-views/application/controllers/cache/meta/manager.php.
After they updated their views plugin to 2.8.1 Solution:
Our team was aware of this issue and we've recently released our views version 2.8.1.1 which should resolve this issue for you.
Problem: I would like to create a conditional that tests the ID of a parent post against the ID of another post created by the current User. I can use Views with post relationship filters and I can use nested Content templates to display the correct IDs, but the conditionals always fail because there is extra space around the ID output by the View.
Solution: You can use the new View option that removes the wrapping div around the output, or you can use the older filter that strips those extra elements. If you use the older filter, you must manually delete all line breaks and spaces from the View's loop editor.
Problem:
Check if current user is the same as the author of a post. Solution:
This can be done by using our views conditional code.
[wpv-conditional if="( '[wpv-current-user info="id"]' eq '[wpv-post-author format="meta" meta="ID"]' )"]
We document known issues and their solutions in Toolset errata. Save time by checking there first and seeing if what you are facing is a known issue. This list is kept short. We do our best to resolve all known issues with every release of Toolset plugins.
Support Policy
Toolset staff will help you use the Toolset plugins correctly, provide any information you need, help troubleshoot problems and advice on best-practices.
Please make sure to issue only one topic per each support ticket.
