[Waiting for user confirmation] CRED intensely slows down the backend!

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.

Our next available supporter will answer your ticket in about 2.69 hours from now. Thank you for your understanding.

You are not logged in. You can view support threads, but not post.
If you are already logged in, please refresh your browser.

Tagged: 

This topic contains 20 replies, has 2 voices, and was last updated by  Shane 7 hours, 44 minutes ago. The support staff assigned to this topic is Shane.

Viewing 6 posts - 16 through 21 (of 21 total)
Author
Posts
#576967

Shane
Forum moderator

Supporter languages: English (English )

Supporter Timezone: America/Jamaica (GMT-05:00)

Hi Herre,

I want to change the server environment of the site. Would it be possible to install the duplicator plugin for me so that I can get a clone of the site.

Thanks,
Shane

#576979

Hi Shane,
Done... by the way... your account is a super admin account... so feel free to add or remove items. Its a test site pure for this issue.. so it's no issue at all if things change or get lost.

Best regards,
Herre

#577417

Shane
Forum moderator

Supporter languages: English (English )

Supporter Timezone: America/Jamaica (GMT-05:00)

Hi Herre,

I've provided our 2nd tier supporters with the duplicator package to test this and debug further.

Thanks,
Shane

#580264

Shane
Forum moderator

Supporter languages: English (English )

Supporter Timezone: America/Jamaica (GMT-05:00)

Hi Herre,

I've got some good news and bad news.

The good news is that the issue is not related to CRED at all. The bad news is that it is with our Types WYSIWYG field.

It seems that when you have quite a number of these fields on the same page it dramatically slows down the page loading so we are suggesting that our developers find some way to improve this.

Nothing else we can do here except to reduce the amount of WYSIWYG editors on the page .

Thanks,
Shane

#580556

Hi Shane,
thank you for your update so far...

I am aware that the more WYSIWYG editors, it slows down the backend....

BUT....

could you please inform at the developers and give an explanation why the page gets slowed down even more when CRED is active?

I don't have a satisfied feeling that they say it isn't CRED at all... I for sure know that the WYSIWYG editors slow down the page on the backend. Has been the fact for all four years i've been using Toolset now.
BUT what I don't get is... the slowdown increases at least 2 times when CRED is active! There somehow needs to be a connection... or try to explain to me why there shouldn't be a connection.

I already communicated the conclusion it had to do with the custom fields on the 27th of September:
==== quote ====
Next I disabled the post fields group linked to pates, therefore pages didn't have a toolset post type taxonomy or anything linked to it.
--> loading time with CRED enabled: +/-9sec
--> loading time without CRED: +/-9sec

So no noticeable difference with CRED enabled or disabled and a tripled increase in loading speed!!!

So somehow the custom post fields to have a huge impact on loading speed of the backend of the page. And when CRED has been enabled this increases with approx 30 seconds.

==== end quote ====

Best regards,
Herre

#580707

Shane
Forum moderator

Supporter languages: English (English )

Supporter Timezone: America/Jamaica (GMT-05:00)

Hi Herre,

Based on the analysis done, it could be that the button from CRED loading onto the editors. Removing CRED removes the CRED form button from all the WYSIWYG editors and this could be why you are seeing some improvements in page load times.

However the root issue is the WYSIWYG fields and not CRED itself.

Thanks,
Shane

Viewing 6 posts - 16 through 21 (of 21 total)

You are not logged in. You can view support threads, but not post.
If you are already logged in, please refresh your browser.