The user is seeking the most efficient way to determine if two posts are related using Toolset. They have developed a function but find it inefficient as it connects and disconnects the posts. They are also exploring alternatives.
Solution:
For simple cases, HTML conditionals or Custom Code can be used. Check the following links for examples:
- Go to Toolset > WordPress Archives
- Click the trash option to delete the WordPress archive
- Go to the Trash filter in the list and delete the archive from there too.
- Re-create the archive
Upon reviwing the site's logs customer found that the following error was repeating often:
2023/07/12 15:41:21 [error] 232#232: *14491 FastCGI sent in stderr: "PHP message: PHP Warning: is_writable(): open_basedir restriction in effect. File(/www/) is not within the allowed path(s): (/deploy:/:/usr/share:/tmp) in /www/wp-content/plugins/types/vendor/toolset/types/embedded/views/image.php on line 390" while reading response header from upstream, client: xx, server: domain.com, request: "GET /product/elite-bb-clarinet-mouthpiece/ HTTP/2.0", upstream: "fastcgi://unix:/var/run/php8.1-fpm-php.sock:", host: "domain.com:21852"
Solution:
Our 2nd tier team detected that the problem relates to processing the image field wpcf-customer-review-image. Checking the entries in wp_postmeta they noticed that there were multiple entries with the key but no value. After fixing this, the error ceased.
The post type template is not displaying, and the user discovered that a PHP template (single.php) is required for rendering Toolset post types. The user is inquiring about the possibility of using a Full Site Editing (FSE) template or if they have to use an old theme with PHP templates.
Solution:
Toolset currently relies on PHP templates, and it does not support Full Site Editing (FSE). To address this, you can use a simple PHP-based template that follows the classic WordPress theme structure. Unfortunately, FSE templates are not supported at the moment.
Problem:
The REST API is one way that WordPress and other applications communicate with the server. For example, the block editor screen relies on the REST API to display and save your posts and pages.
Solution:
I checked that the customer's site has Cloudfare CDN on.
I found a similar case where the culprit of this issue was Cloudfare firewall blocking wp-json/wp/v2 requests.
