This thread is resolved. Here is a description of the problem and solution.
Problem: I would like to update my website to use the new post relationships features, but I'm seeing some error messages and my Forms stopped working as expected.
Solution: Turning off AJAX submission seems to have resolved the Forms submission issues.
You can inspect each post relationship migration message for additional information about what's happening. In this case, it appears that the messages do not indicate any serious problems. The logs are quite detailed for debugging purposes, but these messages all seem to indicate posts that were deleted or old relationships that do not need to be migrated.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | - | - |
| 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | - | - |
Supporter timezone: America/New_York (GMT-04:00)
This topic contains 9 replies, has 3 voices.
Last updated by 6 years, 5 months ago.
Assisted by: Christian Cox.
Hi Beda,
Thank you for looking into this issue.
1. Regarding the form - yes you are right, this has to do with an AJAX submitted form, I solved this by simply turning off AJAX, so I count this solved now as I might return to this later if I want to use AJAX in the future.
2. The unexpected ";" error seems to have been triggered by the form itself as it has radio inputs and if I submit one of the inputs without a value it triggered the error, once I set up the form to operate properly the error disappeared. I will still need help making this validate properly as I have not found a way to make any of the three value fields be required, but this issue is not critical as of now so I will leave this for later too.
*To further understand the issue you can see this screen recording:
hidden link ..
First of all I would like to mention that this is the "Add new product" form where users can add products to their farms.
Here I have the "Опаковка:" Field (means package) and then I have three radio buttons with respecting inputs fields for each type of package:
- user must input kgs, if the package is "теглова" (or package by weight),
- or milliliters if the package is "обемна" (volumetric),
- or pcs, in the case where the package is "количествена" (quantitative).
My problem is that it must be mandatory for the user to select one of the radios AND input a value in the field so they can properly define what type of packaging their product has, but I have not been able to make this work. I have made the field required but it validates upon selecting the radios, not upon selecting the radio and giving a value to the field below. If the user selects the radio and does not input a value in the field the form is submitted and the ";" error is shown.
I use this to visualize a calculation of the product price: price per kig / price per liter / price per piece.
3. Regarding the validation of registration code - okay, count this solved then.
4. Since I have already made a lot of progress regarding the previous issues I would like to get some help on the following first:
Regarding the migration to the new post relationships methods.
When I run the migration wizard I get the following error: (screenshot attached)
When I try to click the link above the "Run the migration" button that reads:
"Please read our comprehensive guide to learn how to use Toolset to leverage the power behind post relationships." - the link is not active, I guess the guide is not ready yet?
So here is the code that triggers the warning:
(This code helps auto-assign the parent post relationship when submitting via front-end-form)
/* Autofill Product > Farm; Product > Workshop; Seed > Seed Bank relationships */
add_action('cred_save_data', 'my_first_save_data_action',10,2);
function my_first_save_data_action($post_id, $form_data){
// if a specific form
if ($form_data['id']==979) {
$parent_id = url_to_postid($_SERVER['REQUEST_URI']);
update_post_meta($post_id, '_wpcf_belongs_farms_id', $parent_id);
}
}
add_action('cred_save_data', 'my_second_save_data_action',10,2);
function my_second_save_data_action($post_id, $form_data){
// if a specific form
if ($form_data['id']==298) {//change this accordingly
$parent_id = url_to_postid($_SERVER['REQUEST_URI']);
update_post_meta($post_id, '_wpcf_belongs_seed-bank_id', $parent_id);
//also edit this, since it's another post type!
}
}
add_action('cred_save_data', 'my_third_save_data_action',10,2);
function my_third_save_data_action($post_id, $form_data){
// if a specific form
if ($form_data['id']==979) {//change this accordingly
$parent_id = url_to_postid($_SERVER['REQUEST_URI']);
update_post_meta($post_id, '_wpcf_belongs_workshop_id', $parent_id);
//also edit this, since it's another post type!
}
}
This code came from another ticked where I asked for help and you did great helping me solve the issue:
https://toolset.com/forums/topic/auto-assigning-parent-post-via-cred-api/
Just it seems like now it needs an update too.
Thank you for taking the initiative to help me again!
