Tell us what you are trying to do?
trying to fix the error I saw on the post type page - Toolset needs to connect to its server to check for new releases and security updates. Something in the network or security settings is preventing this. Please allow outgoing communication to toolset.com to remove this notice.
Is there any documentation that you are following?
I just updated the plugins, unregister and re register the toolset plugin. I have installed the plugins manually but they are connected and registered properly
Is there a similar example that we can see?
I dont have any other example to show you
What is the link to your site?
hidden link
I have found this if that helps after activating the debugging
Deprecated: Creation of dynamic property Toolset_Theme_Integration_Settings_Front_End_Controller_avada::$is_blocks_active is deprecated in wp-content/plugins/wp-views/vendor/toolset/toolset-theme-settings/compatibility-modules/controllers/toolset-theme-integration-settings-abstract-controller.php on line 56
I have created a sample post type with dummy fields to test. I can create the post but its not showing the post list properly and its same for the other custom post types I have. The posts are showing up fine on the frontend but the pending posts and published posts list in the backend is not showing up properly. Please help me fix the problem Id be grateful if you can help me fix it
Hi,
Welcome to Toolset support. Please follow the steps below to provide the debug information for initial check:
https://toolset.com/faq/provide-debug-information-faster-support/
To be able to see ethe debug log please do as follows:
Would you please access your website files and edit the "wp-config.php" file on the root folder of your WordPress installation and add the code below into the file:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', true );
Please add the code above the line below:
/* That's all, stop editing! Happy blogging. */
For more information:
https://wpml.org/documentation/support/debugging-wpml/
And finally, contact your hosting provider and ask them to whitelist the following domains:
api.toolset.com
cloudfront.net
Thanks.
I have also activated the debug in wordpress you should be able to see it. Thank you for the quick response.
Here is what I see after activating he wordpress debug
Deprecated: Creation of dynamic property Toolset_Theme_Integration_Settings_Front_End_Controller_avada::$is_blocks_active is deprecated in public_html/wp-content/plugins/wp-views/vendor/toolset/toolset-theme-settings/compatibility-modules/controllers/toolset-theme-integration-settings-abstract-controller.php on line 56
I have also found this fatal error on the custom posts dashboard
Fatal error: Uncaught TypeError: count(): Argument #1 ($value) must be of type Countable|array, null given in public_html/wp-admin/includes/class-wp-list-table.php:661 Stack trace: #0 public_html/wp-admin/includes/class-wp-posts-list-table.php(1603): WP_List_Table->row_actions() #1 public_html/wp-admin/includes/class-wp-posts-list-table.php(1078): WP_Posts_List_Table->handle_row_actions() #2 public_html/wp-admin/includes/class-wp-list-table.php(1793): WP_Posts_List_Table->_column_title() #3 public_html/wp-admin/includes/class-wp-posts-list-table.php(1437): WP_List_Table->single_row_columns() #4 public_html/wp-admin/includes/class-wp-posts-list-table.php(839): WP_Posts_List_Table->single_row() #5 public_html/wp-admin/includes/class-wp-posts-list-table.php(815): WP_Posts_List_Table->_display_rows() #6 public_html/wp-admin/includes/class-wp-list-table.php(1712): WP_Posts_List_Table->display_rows() #7 public_html/wp-admin/includes/class-wp-list-table.php(1639): WP_List_Table->display_rows_or_placeholder() #8 public_html/wp-admin/edit.php(503): WP_List_Table->display() #9 {main} thrown in public_html/wp-admin/includes/class-wp-list-table.php on line 661
Hi, I have figured put the problem. I had to downgrade the PHP version to 7.4 and was able to see the posts in the backend with the error I am attaching the screenshot as well. Can you please help me find a way to fix it so I am able to use toolset with the latest version of php I had to downgrade from 8.3 to 7.4 which is not good as the support is not available for php version 7.4. I am goign to run some more tests and see if tools set is really compatible with latest version of php or not. attaching the error I see with each post.
Hi,
Thank you for the details. PHP 8.3 is not officially compatible yet with Toolset or WordPress.
I suggest that you take your time using PHP version 8.2 till we have a stable version for PHP 8.3.
The last screenshot you shared is not an error and it is a warning which is not generated from any Toolset plugins checking the URL.
Thanks.
I have tested toolset on php 8.3 and it worked like a charm no errors but I think there is something off with the post types and custom fields its showing 2 custom fields group in 1 which I think is creating a problem and i cant reassign them at all. I have setup a staging to test everything disabled all plugins, setup a new site installed toolset types and views plugins and they worked fine its just the main website has it all messed up
Just to clarify the custom fields group issue I mentioned earlier is happening on the site not on the testing site I am able to reassign the custom field groups but not on the live website. Is it possible to have a zoom call so I can show you maybe we can find a solution. Is it possible to create a new custom field group without loosing previous data and reassign the same new custom field group to the custom post type?
Hi,
You are welcome to use loom.com to show the issue in a video format and paste the link here.
I suggest that you copy the live website to an environment where you can downgrade the PHP version so that instead of having the error you have a warning and then try to make changes on the field that has the issue and then upgrade PHP.
See if it works for you.
There is an option in Toolset > Custom fields > Scroll down and click the POst Field Control
Where you have more information about the custom fields but I strongly suggest do not touch it if you do not have a backup of the website.
Maybe from there you can change the type of the custom field and it fixes the issue? Not sure just trying to give ideas.
Thanks.
