Would you please check if the new version has any sort of conflict with another plugin?
- IMPORTANT STEP! Create a backup of your website. Or better approach will be to test this on a copy/staging version of the website to avoid any disruption of a live website.
- Switch to the default theme such as "TwentyTwenty" by going to "WordPress Dashboard > Appearance > themes".
- Go to "WordPress Dashboard > Plugins" and deactivate all plugins except Toolset plugins
- Check if you can still recreate the issue.
- If not, re-activate your plugins one by one and check the issue each time to find out the plugin that causes the problem.
Thanks.Hi there,
Would you please check if the new version has any sort of conflict with another plugin?
- IMPORTANT STEP! Create a backup of your website. Or better approach will be to test this on a copy/staging version of the website to avoid any disruption of a live website.
- Switch to the default theme such as "TwentyTwenty" by going to "WordPress Dashboard > Appearance > themes".
- Go to "WordPress Dashboard > Plugins" and deactivate all plugins except Toolset plugins
- Check if you can still recreate the issue.
- If not, re-activate your plugins one by one and check the issue each time to find out the plugin that causes the problem.
I deactivated all of my plugins except for the three toolset plugins. The issue still persists.
I am hosted with Kinsta who does do caching but I have cleared the cache even with all plugins deactivated and the issue still happens.
I have another website hosted with Kinsat using the exact same setup for Toolset and there are no issues with it.
hidden link
Same username and password I provided before.
The issue persists here on staging as well.
The issue is not present on another install with the same host, same theme, and same toolset plugin set up.
I have tried clearing the server and object cache, and nothing changes, unfortunately.
Thank you for looking into this. If staging is not good for the situation, please feel free to copy from staging to your host.
So I keep trying to figure this out on my own, but no luck. I did notice though that when I tell the custom fields to show on any post type - they show up fine on pages - but they still refuse to show up when adding or editing a property... Hopefully, that helps whoever is working on resolving this ticket.
Sorry, one last update here. I noticed that if I change the property slug to something else, they show up completely fine. It's only when they are named "property" that there is an issue.
Hi there, let me reply directly to you now, as Christopher won't be back until Sunday, so as not to keep you waiting.
The issue happens on the online test site (as well as your site), but it doesn't happen when I download a copy to work on locally.
I've been working on trying to debug the issue on the remote server, but that is difficult and time consuming, and after 2-3 hours doing that I'm no closer to identifying the root cause.
In the end I decided it would possibly be quicker and easier to just delete the problem field group and reconstruct it, and I just did that and it works correctly.
Sorry for the inconvenience but I'm going to have to request you do the same—it took me about 2 minutes, because you can add back the fields you already created, you don't need to set those up again.
So:
1. Make a note of your existing field group details (e.g. take a screenshot of the included fields)
2. from Toolset > Custom Fields delete the existing field group.
3. Make a new field group, and before adding any fields assign it to the property post type, then go edit a property post and verify that the empty field group is shown on the post edit screen.
4. Recreate your field group.
When you add a field to the field group note the button "Choose from previously created fields", which you can use to add back your existing fields. Repeat that until you have added back all of the fields.
That should work, but do let us know if it doesn't.
