Search the Community
Showing results for tags 'repeaters problem'.
Found 1 result
-
Hi to everyone, please try to consider this post as a possible thread to every PW installation. We have used PW to backend a website and app for a big big company, so stability must be granted. Recently we was into a big trouble, filesystem was blocked because no Inodes left. The assets/files/ folder was full with more than 7 million directories. After some research we found a possible origin to this: If we have a template user, which have assigned a repeater field. And then we set as parent of that repeater a "User" page, this could lead into an infinite loop of pages creation; because the template_id for the repeater pages was set to "User Template" and since "User Template" includes that repeater it will need to create another page and you go on until your disk crash. Usually repeaters should stay under Admin->Repeaters. And here is the main questions: Can a repeater page be created with the same template_id as his "container" page? At database(Mysql) level does the template_id field will be filled with his parent template_id in the pages table when you import the repeater field? (Sorry for that but filed means something for db schema too) Could someone tell me if this actually happen. If so, could this be checked in a future release to prevent this problems? You should say, "How could this happen?" This happen when you have different environments and you migrate fields from one to another environment; a Page ID that is an Admin->Repeaters child page in one environment is not necessarily the same in another. Thank you for your time reading.