Hello. Thank you for contacting the Toolset support.
Can you please share problem URL where I can see the issue as well as admin access details.
*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.
I have set the next reply to private which means only you and I have access to it.
UPDATE:
Hi I noticed also some custom fields previously created disappeared too and the cred form reports some errors, but I can't add them because it said they already exsist. 🙁
I'm not sure why you do not able to see the private fields.
*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.
I have set the next reply to private which means only you and I have access to it.
Before login as admin, you have to use the credentials I sent you in line Before to access...
I'm working on the website and it's working fine, but the folder is protected by a password.
Let me know if you can log in.
Thanks.
As Minesh was having some difficulty in accessing your website's admin area, he has passed on this ticket to me.
I noticed that the "Gruppo di campi per politico" custom field group not only consists of a lot of custom fields, but some of those fields also have very long field names and slugs.
This means that whenever any change is made to this custom field group, a lot of information needs to be processed by the server in one go. We've seen some similar reports about this issue where increasing the server's "PHP max input variables" and "PHP post max size" values fixed this.
If you'll go to WP Admin -> Tools -> Site Health -> Info -> Server, you'll see that the current "PHP max input variables" value is 1000 and "PHP post max size" value is 8M. You can increase both these to higher values, for example, 4000 and 32M respectively.
But this is only a temporary fix and a more efficient and long term solution would be:
1. Making sure to keep short names and slugs in the fields in custom fields groups, and
2. And even if you need to store many custom fields with an individual post type, it is a good idea to distribute them in multiple custom field groups, instead of registering them all through a single custom field group.
I hope this helps and please let me know if you need any further assistance around this.
