• ktib1

• in reply to: Many custom fields in a post : optimize performance
• November 2, 2021 at 8:21 am

Hi @hube2,

Thank you very much for the information, especially the one in point 2).
I hadn’t noticed this behavior, and knowing this solves my performance issue, because as I said most of the fields in my repeater will be hidden by conditional logic.

However, this created another issue, because I had planned to hide many fields with a true/false button. Only when the user needs it would he click on the button, check/edit the fields that are needed then click again to hide the fields. If he does that, the changes won’t be saved.

Possible solution :
When the button is clicked to FALSE, first update the post then update the button value to false. I suppose it’s possible, but if you already faced this problem, if you have a better idea, don’t hesitate to tell me.

@raygulick thank you, but in my case the repeater won’t have many entries (2 to 6 in most cases). The problem it that each row of the repeater has a lot of fields.

• ktib1

• in reply to: Many fields in a repeater : long saving times
• October 26, 2021 at 7:18 pm

I trust you 🙂
I had read enough threads on the subject to guess that it was almost impossible to fix, but I wanted to make sure.

Ok, then I have some questions on how to optimize my fields (to try and reduce the number of them), but I will create a separate thread for that.

Thank you very much John

• ktib1

• in reply to: Many fields in a repeater : long saving times
• October 26, 2021 at 5:13 pm

Hi John,

Thank you for your quick reply.
You mention Gutenberg in your 4th reply of the thread on January 29, 2018.
But it doesn’t matter, I don’t use Gutenberg either, I just mentioned this in case there had been some changes to WordPress since then that makes my problem now irrelevant. Obviously not the case.

With that number of fields I would defiantly look at a different way to build it.
I fear this is what I’ll end up doing. Using a repeater is very justified considering what I’m building, but I’ll probably have to separate some functions in different posts types. Not ideal at all, but better than the alternative.

Before resorting to that solution, I’d like to ask if the solution I thought of could potentially work :

– Create an additional field in the row (lets call it rowmodified)

– When there is any change in any field of the row, have a value (for example “1”) added dynamically in the field rowmodified.

– Add a function that does the following when the post is updated:
* Start by checking/saving the value of rowmodified in the first row of the repeater.
* if rowmodified has a value of 1, insert/update the other fields of the row. THEN delete the value of rowmodified.
* if rowmodified has no value, don’t check/update the other fields of the row (i suppose this is the tricky / impossible part)
* On to the next row
* Update the remaining fields out of the repeater.

As I said I’m not really a developer so i have no idea if it is technically possible, I suppose not, but who knows.