Very very weird behaviour for repeaters

[verdeandrea]

Hi guys,

I'm getting crazy trying to figure out what is the cause behind a weird problem is giving me some bad moments with my client.

I have a repeater field, with some fields as childre. From one day to the other the children fields of the repeater change and i find other fields as children. Also, all the content my client inserted in that repeaters are gone, cause now we have the new empty children fields. I really don't understand what can be the reasons behind this.

This happened more than once.

It' s like there is a repeating action that changes the repeater's children. The only repeating action I can think of is the chronjob for the database. Could this depend on that? Have you any idea or suggestion of what should i check or ho to solve this weird problem?

Thank you very much!

[dragan]

56 minutes ago, verdeandrea said:

The only repeating action I can think of is the chronjob for the database

What exactly is this cron job doing?

[Robin S]

Do you have the AutoExportTemplatesAndFields module installed by any chance? There are reports in the the support topic that it can cause issues with repeater fields.

[verdeandrea]

Thanks for the reply.

@dragan I'm using the CronjobDatabaseBackup module to make daily backups of the database

@Robin S no I'm not using it. 

If I remember correctly i had this problem for the first time when i used export / import fields tool in processwire to copy this new fields from my local pw to the remote one.

 

[verdeandrea]

This are the modules I have installed.

There are two custom modules I made (GlobodoroChildren and GustoChildren). But I don't think they can be responsible for this problem. You can find them attached.

GlobodoroChildren.module

GustoChildren.module

[dragan]

Both your custom modules use the same hook, and the same function-name createSubPagesForEdition(). I find that a bit strange, and potentially dangerous. Do you have control over which module is executed first?

Also, the import/export function is labelled as "experimental" (don't know exactly why).

[adrian]

What version of PW? Repeater import/export was fixed fairly recently https://github.com/processwire/processwire-issues/issues/416 so if you are not on dev, maybe that is the issue.

[verdeandrea]

@adrian sorry i forgot to mention: PW version is 3.0.62, so it should be the last.

@dragan thanks, i'll change my functions names se they are not the same.

But i think i understood where the problem is but i don't know how to fix it.

I have these two repeaters and their children fields where inverted when I imported them via pw import fields. Then i though i fixed but they are now somehow related.

That means that, if i fix one repeater's children also the other repeater get the same children. I suspect it could be some problem with ids in database. Maybe the best thing to do is create new repeater fields from scratch, if you don't have better suggestions on how to fix this problem.

Right know i tried to fix one repeater and when I checked the other one, its children fields were changed and were the same of the first repeater.

[dragan]

Did you try to merge your two custom modules into one? And also (since it seems to be a live site): can you go back to an old state (backup) where you are sure everything worked fine?

[verdeandrea]

@dragan unfortunately i can not go to old state cause a lot of contents are being inserted by my client during these last days.

I'll definitely try to merge the two custom modules into one.

[verdeandrea]

Yes, I'm pretty sure I have some messes on the database. I tried to delete the first repeater. First i removed it from the only template that was using it. But then, when i tried to delete it i got an error message that says it can not be deleted cause it's used in 56 pages (i also emptied the trash before and tried again).

Probably i have to dig in my database.

 

[verdeandrea]

Ok, i think I got where the problem is. The 2 repeaters have the same template id in the database. I have to fix that.

[adrian]

4 hours ago, verdeandrea said:

PW version is 3.0.62, so it should be the last.

That's the last master - as I mentioned, the issue wasn't fixed until recently in the dev version. 

[verdeandrea]

Thanks @adrian

Yes probably the export/import feature messed my repeater fields. In the end I decided to trash all the old fields and to start again with new ones so now it should be fixed.

Thank you guys.