[Resolved] Change of CPT Slug creates issues with Relationsship

[Author]

Posts

[philipS-3]

Hey there,

I changed the slug of a CPT which is in a relationship with another CPT. Now the relationship seems to be affected in that I cannot add or create a new item through the relationship anymore. The relationships on the frontend are still there, I updated the content templates to reflect the change as well. But I cannot get the relationship link itself to work. I tried resaving the relationship itself by editing it (it also still sees the relationship because it tells me a minimum number of posts that I have to have as part of the relationship) but it hasn't helped me in fixing the issue of adding a new item or linking to an existing one.

How can I fix the issue?

Thanks a lot in advance.

[Mateus Getulio]

Hey there,

Thank you for contacting our support forum!

We have settled up a clean install having only Toolset plugins, in order to replicate this issue you reported, but with no luck so far. This makes me believe that we might be facing an interaction issue with a third-party functionality, in this case:

- Deactivate all the plugins that are not related to Toolset
- Switch for a moment to a WordPress default theme like Twenty Twenty-one
- If the issue is gone, activate one by one to see with which one there is an interaction issue

Could you please tell me the results of this investigation? Also, can you enable the debug mode? Just add the following code in your wp-config.php file:

// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
  
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
  
// Disable display of errors and warnings 
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
  
// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
define( 'SCRIPT_DEBUG', true );

Please check the following links to read more about debugging with WordPress.
- https://codex.wordpress.org/Debugging_in_WordPress
- https://codex.wordpress.org/Debugging_in_WordPress#Example_wp-config.php_for_Debugging

After adding the code above, try to reproduce the issue again and check if you'll find a debug.log file inside the wp-content folder. If you locate it there, kindly send us the last lines here in the ticket.

If you also want to try to replicate the issue in the Sandbox we created, I'll share with you the automatic login link in my next private reply. Please let us know the step-by-step in order to reproduce it, if you manage to do so.

Regards,
Mateus.

[philipS-3]

Hey Mateus,

thanks for getting back to me. So I just tested the slug change on my dev env again and there it worked fine. Unfortunately, on my live site it does not 🙁 So, I did a few quick additional tests:

I changed the slug to something totally different - no difference, still cannot add or edit
I then wanted to change the slug back to the original and now it says that the slug is still taken, as you can see in the screenshot. The bizarre thing is that if I try to access the domain fslci.org/university/ it forwards me to /universities/ - something I did not configure but might be related to the issue.

I'll test a bit further tomorrow but if you have any idea in the meantime, please let me know 🙂

Kind regards, Philip

[Mateus Getulio]

Hello Philip,

Thanks for your reply.

If you want to use the previous slug, you would need to delete it first. You can do that by following this method: https://toolset.com/forums/topic/warning-field-slug-is-already-being-used/#post-550336

In case the issue persists, or you want to use the new slug, I would like to request temporary access (wp-admin and FTP) to your site to take better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.

Our Debugging Procedures

I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.

Privacy and Security Policy

We have strict policies regarding privacy and access to your information. Please see:
https://toolset.com/privacy-policy-and-gdpr-compliance/#data-shared-with-our-support
**IMPORTANT**

- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link

Please, let me know if you need any additional details. Have a nice day.

[philipS-3]

Dear Mateus,

I am happy to report that I solved the issue! The culprit was the WP Extended Search Plugin (https://wordpress.org/plugins/wp-extended-search/). Maybe you can look into why it is creating that conflict, but I'm happy that I now know what's been causing the issue.

Kind regards, Philip

[philipS-3]

My issue is resolved now. Thank you!