Home › Toolset Professional Support › [Resolved] After page creation, Page Edit extremely 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.
Our next available supporter will start replying to tickets in about 1.88 hours from now. Thank you for your understanding.
Sun | Mon | Tue | Wed | Thu | Fri | Sat |
---|---|---|---|---|---|---|
- | 10:00 – 13:00 | 10:00 – 13:00 | 10:00 – 13:00 | 10:00 – 13:00 | 10:00 – 13:00 | - |
- | 14:00 – 18:00 | 14:00 – 18:00 | 14:00 – 18:00 | 14:00 – 18:00 | 14:00 – 18:00 | - |
Supporter timezone: Asia/Kolkata (GMT+05:30)
This topic contains 30 replies, has 3 voices.
Last updated by Minesh 1 month ago.
Assisted by: Minesh.
Well - if I have duplicator and I try to install duplicator pro plugin and try to take your site copy, is that ok?
That will be fantastic, thank you.
On 503 errors: our hosting service is busy with scheduled maintenance, which might be why this happens today.
There must be issue with your server or site as even when I try to access the plugins page on your site: hidden link
I can see the white page with error:
503
Service Unavailable
As I'm not able to access your site they way I wanted.
I'm happy to share the sandbox site and here is the auto-login link for the sandbox site:
- hidden link
Are you able to reproduce the same issue with the above sandbox site by copying the page?
Minesh
There was some server maintenance earlier and no site on the server was visible.
I wonder if your 503 Service Unavailable was not perhaps due to that.
The plugin page shows at my side -- but I see Toolset's key disappeared. It request to input the key.
I am not sure what you mean with Sandbox. I followed the link.
Which page must be copied?
I opened the latest page on the Sandbox with the Page Editor: View: test-legacy-view1 - its shows, I saved it without trouble.
But on the Sandbox WP, it says Toolset is "unregistered version"
If you could let me know urgently what you mean, please.
Out site development has been standing still since the previous Monday. We've put in too much dependence on Toolset to start over, so we really need to know what the problem is.
Did you manage to get into the site at all?
I tested just now.
It now suddenly says there is no support of Toolset container block -= never had that message before.
Also, before I replied to your previous message, I also tested, and then there was a message that the Toolset is not registered (screenshot). But on plugin page it says it is registered (2nd screenshot)
Well - the sandbox site I shared I did not register the site key that is why you see the message and there is no issue with that.
The plugin page shows at my side -- but I see Toolset's key disappeared. It request to input the key.
===>
I did not removed the key.
Here is the Doc that shows information how you can register Toolset on multisite:
- https://toolset.com/faq/how-to-install-and-register-toolset/#registering-toolset-on-a-multisite
Where on what page you see the information that container block - can you please share link of that?
No worries about Toolset registration on multisite. It has worked months.
Possibly all pages.
Earlier today I tested with another page, and just now with Page with ID 1646. The screenshot I sent earlier was for another page.
hidden link
The problem we have is that since last Monday, the whole Page Edit function is problematic, and the problem goes away when we deactivate Toolset Types.
Well - I'm not sure but I checked the page you shared:
- hidden link
And again I get 503 error.
Then I asked one of my collogue to check this and he also get the 503 error and your site is extremally slow at this end.
I do not have a window to help you further in the current server environment as I can not access the site.
That is strange.
I checked now and access here (South Africa) to the server in Amsterdam (Netherlands) is fine.
As last effort, could I perhaps then make available a set that you could import? On Google Drive.
I'll open it for an email address of yours.
What you mean, I need site copy.
It will be great if you able to provide your site copy.
My email address is: minesh.s@onthegosystems.com
I have set the next reply to private which means only you and I have access to it.
Hi Minesh
We're just going through an intense cycle of troubleshoot once again and the copy of the site should be available to you by this coming Tuesday.
Have a good weekend
Jacques
Ok fine - please let me know when you have a site copy.
I have set the next reply to private which means only you and I have access to it.
We're still busy analysing each and every bit.
The Toolset-Woocommerce Blocks definitely has a conflict. In a previous ticket the advice we got from Toolset is that the "deprecated" notice should not be a problem - but I wonder if that does not perhaps cause a loop.
When Toolset-Woocommerce Blocks is deactivated, the Toolset Types problem goes away.
Although woocommerce is installed, we haven't implemented it yet - except for custom product categories.
Yes - Deprecated notice should not break or not have any possible performance issues.
Ok please do your desired checks and feel free to share information once you done with that.
Hi Minesh
Thanks for your patient assistance.
We have gone through an intense process of resetting each and every setting, clean DB, tables, double-checking every setting, etc. etc..
Pages in Edit mode now load quicker than he looong time. Its sill not what it used to be.
And with Toolset Woocommerce Block deactivated, we do not get all the error messages. In a separate ticket it was replied that Toolset is looking at the matter and will be fixed in next update.
The problem is not fixed yet, but we will have to live with that now to catch up for the next phase.
We might be able to copy the content to a more stable installation.
I still suspect some table content problem, as we occasionally get weird error messages, that go away by themselves.
So for now I'll close this - but might need to reopen if the problem gets worse again.
Warm regards
Jacques