I have created a relationship form for many to many relationship. Now I would like to give the user the option to disconnect the relationship. How this can be done?
I'm assuming that you're referring to disconnecting the relationship on the frontend correct?
Unfortunately this is not possible to do as you can only disconnect them through the backend.
What I would suggest that you do is to open a feature request for this so that it can be reviewed by our development team and get added sometime later in the future.
Thank you.
Yes on the front end.
In this case I am thinking to create an other post and link the two posts to this post as one to many relationship. In my case I have property post and agent post. The property can have 0 to 3 agents and the agent can have 0 to many properties. So, may be I can add a post called "Property agent" and link property to this post as one to many and do the same with agent post. The I create form for property agent where I can link current property with any agent. However, in this case I my have a duplicate . Is there a way to avoid duplicate?
Can this be a practical solution?
Based on your explanation it would get quite complex because you would essentially edit the property agent cpt to disconnect an Agent from a Property.
It would work essentially since you are using the Property Agent CPT as a kind of link between both and you can use a Form on the frontend to disconnect the associations.
I think it is a practical solution, however when displaying the Agents of a property you will need to use 2 views instead of one.
Where 1 view will be for Property Agent and the second would be for the Agents. So how it would work is that Property is the Parent of Property Agents and Agents is the Child of Property Agents.
So your relationship would look like this Grandparent -> Child -> Grandchild.
Hi, Shane is out on holiday this week so I am looking into his tickets. I'm a bit concerned about the post relationship approach Shane proposed:
"So how it would work is that Property is the Parent of Property Agents and Agents is the Child of Property Agents. So your relationship would look like this Grandparent -> Child -> Grandchild."
The problem I see here is that in a one-to-many relationship between Property Agent (one) and Agent (many), an Agent can only ever be associated with one Property Agent post. In other words, one Agent cannot have multiple Property Agent parents, hence cannot be associated with multiple Properties. If I understand the scenario correctly, this setup would not be ideal because you want to be able to associate one Agent with many Properties, am I correct? If so, then this type of hierarchical relationship isn't going to work. Agents must be a parent of Property Agents if you want to be able to link Agents with multiple Properties.
Like you already mentioned, you would create a new Form that creates Property Agents. I think the best way to prevent duplicates here is to use custom code with the Forms API cred_form_validate and the Post Relationships API toolset_get_related_posts. The cred_form_validate API will let you trigger some code to validate the selected parent when the Form is submitted. The toolset_get_related_posts API will let you query related posts to determine if the selected parent has already been linked to the current post. If so, you would return an error to the User submitting the Form, and the duplicate would be blocked.
Christian is on vacation. He will get back to work this Sunday. I'm stepping in, hope this is ok.
Yes - you can use the post-relationship API function toolset_disconnect_posts() to delete the many-to-many connection but you need to find a way to trigger it using some custom shortcode or if you are using post form then you can use the Toolset Form's API hook - cred_save_data.
Please note that there is no API hook available with Toolset post-relationship forms.
- Where 'book-book-author' is many-to-many post relationship slug.
As you may know, that connections for many-to-many post-relationship will be stored in the intermediary post type. The intermediary post type is automatically created when you created the many-to-many relationship that will hold the connections.
I have moved it to toolset custom code and the problem was fixed. However, I want to know where I have to add the shortcode. Can I add it in view ( I have a view that shows all agents related to one property) as a link next to each agent. If yes then what will be
$parent = ?;
$child = ?;
In the content template of property I display a view of all agents connected to the property. Can I add a remove link (in this case the shortcode)next to each agent so the user can disconnect property and agent on front end?
Can you please share the link of the content template you are using to display property, once I review that I will be in better position to guide you in the right direction.
*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.
I have set the next reply to private which means only you and I have access to it.
Created the following page and there I've added the [delete_relationship] shortcode to its post body:
=> hidden link
-The shortcode code is adjusted as given under within the custom code section offered by Toolset:
// Put the code of your snippet below this comment.
function func_delete_m2m_relationship($atts) {
$parent = $_GET['parent'];
$child = $_GET['child'];
if(!is_admin()) {
toolset_disconnect_posts('properties-agents', $parent, $child );
$location = $_SERVER['HTTP_REFERER'];
wp_safe_redirect($location);
exit();
}
}
add_shortcode("delete_relationship", "func_delete_m2m_relationship");
Please check the following single property page on different browsers where you are not logged in as admin- click on the "Disconnect posts" link: hidden link
Can you please confirm the workaround I shared help you to disconnect the posts.
