I'm trying to use cred-delete-relationship shortcode to unlink event and gallery posts in a many-many relationship. I have the shortcode set up inside a view as the docs say to do:
Regular "Administrator" users can see and use the link just fine, but my custom "Gallery Manager" user cannot. I've given the Gallery Manager role the "manage_options" which I've read was necessary.
Solution:
In order to delete the relationship with shortcode [cred-delete-relationship]:
Acceptance criteria:
- when you visit the post in the frontend as admin: you should see a list of post related entities AND a button to delete the relationship between each of them.
- when you visit the post in the frontend as a user that HAS NO permissions to edit one of the post types: you should see a list of post related entities and NO button.
Problem:
How are image uploads affected by the changes in Toolset Forms 2.4 and what does it mean for validating the image uploads?
Solution:
Prior to Forms 2.4 a bespoke ajax uploader was used to pre-upload images (i.e. upload images as soon as selected rather than waiting for the form submission).
Since Forms 2.4 the native WP uploader is used for logged-in users (subject to the settings in the form). It cannot be used for guest users, for whom images are uploaded along with the form submission.
When using the native WP uploader the cred_form_ajax_upload_validate hook can still be used, otherwise the cred_form_validate hook should be used.
Problem:
How can I update or create Repeating fields using WordPress's API to manipulate meta fields (get_post_meta/update_post_metae/add_post_meta)?
Solution:
Toolset doesn't offer a specific API for this, and our Support Guidelines don't allow direct support on such custom code, we can, however, give an example that will help understand how repeating fields (not repeatable field groups, but repeating fields) can be retrieved and updated.
With repeating fields we have meta key, meta value, and the position of each of the values, to consider in our code.
To update, or post such fields, you need not only to pass an array of those values to the field but also the position of each item in the repeating field.
Below link holds a full example code, that can be used as a starting point for further customization.
Problem:
A JavaScript library is used to add a masonry layout for posts output with a View. After custom search or pagination the masonry effect no longer happens.
Solution:
The masonry code is initially loaded with the DOM ready event. It needs to be reinitialised when the View output has been replaced using ajax (because of a search or pagination).
The precise requirements depend on what library is being used, but the code to initialise the JS library should be structured something like this, which uses custom JS events available with Views. These custom events can be found in the JS editor of the Search and Pagination section of the View using the Frontend events button.
// 1. Define a function that does "the thing"
function theThing() {
//do the thing
}
(function ($) {
// 2. Do the thing on initial pageload (DOM ready)
$(document).ready(function () {
theThing();
});
// 3. Do the thing after ajax custom search
$(document).on('js_event_wpv_parametric_search_results_updated', function (event, data) {
theThing();
});
})(jQuery);
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.
