I did a manual install of toolset types3.4.15, blocks 1.6.1, and forms 2.6.12 on my staging site and played around for 2-3 weeks, did a lot of trial and error, and learnt a lot. Decided on naming conventions for fields, forms, views and templates etc. I set up 3 x post types, custom fields, forms, views, templates, and new pages to house content. All good.
Now I have done automatic install of the 3 same components on my Prod site, and started to manually configure everything using my agreed naming conventions. (rather than do an export/import).
I configured 3 x post types, custom fields, and forms.
I started to create a template for Job Vacancies, and as soon as I added a view, and some search fields, the template could not autosave and after some unresponsive time (~3 mins) the site crashed. I persisted, and retried - crashed again adding fields to the template.
I added a new template for Events, and again, the site crashed as soon as I added fields. I got email/s from the site saying toolset crashed the site.
I cannot save these templates. In one case they did not create the new view.
Can you take a look? You have my sign on details for the site (as before)
Templates I cant save which will crash the site:
- Job Vacancy Template — Draft, Block Editor
- Job Seeker Template — Draft, Block Editor
- Events Template — Draft, Block Editor
Views created:
- Events View — Block Editor
- Job Seeker - View — Block Editor
View NOT created (it should have been when I added the view block to the template)
- Job Vacancy - View — Block Editor
Thank you for contacting us and I'd be happy to assist.
An error message like this can appear if one or more files in Toolset plugins are either not available or corrupt.
To fix this, I'll suggest the following steps:
1. On your production website, deactivate and then delete the Toolset plugins.
2. Download the new copy of the Toolset Types plugin from the Toolset downloads page ( https://toolset.com/account/downloads/ ) and install and activate it.
3. After registering Toolset with the site key, you'll be able to install and activate other Toolset plugins, from WP Admin -> Plugins -> Add new -> Commercial.
After the plugins have been reinstalled and reactivated, try creating a new content template and editing the existing ones.
Hi Waqar, questions. you said:
1. On your production website, deactivate and then delete the Toolset plugins. ==>(plugins = plural, I assume all plugins - types, blocks, and forms)???? this is a question
2. download install and activate toolset types
3. install and activate other plugins (blocks and forms)
4. try creating a new content template and editing the existing ones. (existing ones? = will there be existing one?)
Will I be starting from scratch - ie I have to start to define custom post types, custom fields, forms, templates, views etc.
I have done A LOT OF WORK doing all this. A LOT!!! Will the deactivate & delete remove all the work I have done?
You said:
In case the issue still persists, (after deactivate & delete & reinstall & reconfigure) please see if any other errors or warnings are logged in the server's error logs, after turning on WordPress debugging. Can you check this before I go ahead and deactivate & delete?
I hope you can answer my questions before I go ahead and remove everything.
Hello, still waiting for your advice - is there anything you can check/test before I go ahead ad deactivate, delete & reinstall and reconfig. Pls advise.
> On your production website, deactivate and then delete the Toolset plugins. ==>(plugins = plural, I assume all plugins - types, blocks, and forms)???? this is a question
- Yes, I meant all Toolset plugins.
> try creating a new content template and editing the existing ones. (existing ones? = will there be existing one?)
- The Toolset settings and data like custom post types, custom fields, custom taxonomies, views, content templates, WordPress archives, forms, etc won't be lost if you'll delete and re-install the Toolset plugins. This means that your changes and work involving Toolset plugins won't be lost, when you'll reinstall the plugins.
I recommended checking the server's error logs after the plugins have been re-installed because that way we'll be sure that all plugin files are up-to-date and complete.
