Skip Navigation

[Resolved] CPT too slow

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
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Sao_Paulo (GMT-03:00)

This topic contains 10 replies, has 2 voices.

Last updated by Mateus Getulio 2 years ago.

Assisted by: Mateus Getulio.

Author
Posts
#2625015

CPT are too slow, we already updated all the website and all works fine except CPT

This video explains the issue
hidden link

#2625017

[removed]

#2625149

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hey there,

Thanks for your contact and welcome to our support forum!

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.

Regards,
Mateus.

#2625375

Here is the error logs
[19-Jul-2023 11:16:18 UTC] PHP Deprecated: ctype_digit(): Argument of type WP_Post will be interpreted as string in the future in /home/statging_terroirs/www/wp-content/plugins/types/vendor/toolset/toolset-common/inc/autoloaded/field/group/factory.php on line 134
[19-Jul-2023 11:16:19 UTC] PHP Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /home/statging_terroirs/www/wp-content/plugins/types/vendor/toolset/types/embedded/admin.php on line 168

Why are these are repeated a lot of times

#2625385

Also here is a quick video with our concern regarding the number of CPT created which we are not sure if that is supposed to be there or not hidden link

#2625487

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hello,

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.

#2625817

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hey there,

Thank you for providing the credentials, but it seems that the login page is different from than the default ones 'wp-admin' and 'wp-login.php'. If we try to access it, we receive this: hidden link

Could you please review what is the correct login URL and update the credentials? Thank you.

#2625827

this is the login url hidden link

#2625867

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hello Rodriguez,

Unfortunately it is not working for us, please check the following video: hidden link

Do you need to whitelist my IP, by chance? If it is the case, here it goes: 190.52.73.251.

Or, if you prefer, you can even share a website copy with us. Your next response will be private again, in case you want to attach a package.

Waiting for your feedback. Thank you.

#2625919

Can you please try with this url hidden link

#2626235

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hi there,

Thank you, now it works.

In the past we had a few reports of multiple "Toolset WooCommerce" field groups getting registered, and it occurred due to some custom code/plugin. Are you using any custom plugins or code on your website too, by chance? Please let us know this info.

Further, in order to remove those several dupe field groups, you can follow the steps suggested in this forum reply:
https://toolset.com/forums/topic/toolset-woocommerce-starts-multiplying-custom-fields-in-back-end/#post-2092581

We tested the custom code mentioned above and it seems to successfully delete some entries. Could you please give it a try and let us know if it helps? Thank you.

Regards,
Mateus,