Jump to content

Recommended Posts

Posted
I had about 300 fields on a template and i was adding on more when after saving they all disappeared i have to re add all again. There was no error message. Has anyone had to deal with this and how was solved? Thanks
 
Posted

Have a look at the log file of your web server to see if an error message appears.

There are also log files from Processwire in this directory: \site\assets\logs

It may be a problem with the PHP setting max_input_vars (that the maximum number has been exceeded)

Posted

There are no errors in this directory: \site\assets\logs and my max_input_vars is currently 3000. I will increase and see if that helps. Thanks

Posted

unfortunately the increase of my max_input_vars  did not help the fields have disappeared again

Posted (edited)

Ok i have successfully saved the template with about 420 fields. Now when i try to populate the fields in the individual pages. I get the error " InputfieldForm: Max number of iterations reached for processing field dependencies - ProcessPageEdit." Any suggestions on how to fix this?

Additional information is 390 fields of the 420 fields  in the  template use field dependecies could that be a problem?

 

 

Edited by Aby
  • 2 weeks later...
Posted

The problem has occurred again after 2 weeks. I tried to save some changes and almost all my fields on the template have disappeared again. I need help please.

Posted

Is there a chance you are using RockMigrations and somehow triggered an older migration that removed fields from that template?

Happened to me yesterday and took me a while to find. And to make it clear: it's intended behaviour - see screenshot.

2025-03-19_21-16.thumb.png.975dcc86c875dbf88a76531b6cfeb254.png

The minus tells RockMigrations to only have listed fields in that template.
Without the minus I could add fields via backend and run migrations without removing manually added fields.

Posted

No i do not use RockMigrations. I do not know whether the number of pages using the template and the number of fields on the template can cause this. 

  • Like 1
Posted

I don't have the expertise in PW that some here have, so I would just ask in a general sense, isn't 480 fields pushing it a bit?

At that point, aren't you better using the most excellent ProFields module or your own database tables? Just curious...

  • Like 3
Posted

Ok i have to discuss ProFields since it involves some cost but about the database tables can you give me some more information? I have no idea what that is

 

  • 1 month later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...