Home › Toolset Professional Support › [Resolved] Toolset Relationship error message
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)
Tagged: Post-relationship
This topic contains 3 replies, has 2 voices.
Last updated by Christian Cox 6 years, 6 months ago.
Assisted by: Christian Cox.
Hello,
We are experiencing an issue with Toolset Relationship.
We have a many to many relationship between a Products table and a Suppliers table.
It has been working fine until yesterday.
Now when we create a new product, or edit an existing one, and try to connect it to an existing supplier, we get an error message:
“there has been an error, please try again later.’
Please see attached screenshot.
However, if I then reload the page, the Supplier appears correctly added.
Please refer to second screenshot.
Please advise,
Thank you,
Imanol.
Hi, can you try the following troubleshooting steps first?
- Temporarily activate a default theme like Twenty Seventeen and deactivate all plugins except Types. If you need to activate a maintenance mode plugin during testing that's fine.
- Open the browser console and test again. If any browser errors are logged, please copy + paste them here for me to review.
- If the problem was resolved, please reactivate your theme, then other plugins, one by one until the conflict returns.
- If the problem was not resolved, please activate server logs to see if any backend error messages are triggered. If you're not familiar with server logs, I can show you how to activate them temporarily. Go in your wp-config.php file and look for define(‘WP_DEBUG’, false);. Change it to:
define('WP_DEBUG', true);
Then add these lines, just before it says 'stop editing here':
ini_set('log_errors',TRUE); ini_set('error_reporting', E_ALL); ini_set('error_log', dirname(__FILE__) . '/error_log.txt');
Attempt to connect posts again. If any backend messages are logged, this will create an error_log.txt file in your site's root directory. Please send me its contents. Once that is done, you can revert the changes you made to wp-config.php.
More on this issue: Doing some testing i my local server, everything was working fine, until I updated the wp_views plugin. I tested again de-activating this plugin, and confirmed this is the culprit. I was able to reproduce the same scenario on the prod server. The buggy Views version is 2.6.1 (June 19)
Okay thanks for the additional information. Were you able to find anything in the browser console or in the server logs? If not, I'll need to create a clone of your site so I can do some further investigation without disturbing your live site. If that's okay with you, please provide login credentials in the private reply fields here. I will install the Duplicator plugin to clone your site and begin those tests.