[SOLVED] Repeaters odd behaviour

[lele_ballack]

I'm getting crazy after this issue that appeared in the last two websites with PW. I'm using respectively the versions 3.0.210 and 3.0.223. 

Repeaters are showing a very odd behaviour. When I create or import a repeater, sometimes it is saved in the wrong place. I do expect repeaters to be saved under Admin/Repeaters, and while most do, for some odd unknown reasons, some of them are saved in some other places of the Admin tree. 

For instance in this case (see attached pictures), the 'Card_FT' repeater was saved under Admin/Permissions, overwriting the permission title 'Page Clone' and having each repeater as children of this (wrong) page.

Can anyone provide an explanation why this is happening? Anything I can do to fix this issue?  

I'm literally clutching at straws trying to fix this issue and deliver these websites to clients asap. 

Thank you in advance!

 

[bernhard]

My first bet would be that any other modules/hooks are messing things up. I think it's very unlikely that there is an issue in the core or in the Inputfield itself. Never seen such a behaviour 😮 

[netcarver]

I'm seeing something similar on a site where I imported a repeater and now it's being saved in a part of the page tree I would not have expected. Also, pages using the template into which I added the repeater are being saved in the same part of the page tree. I'm running on v3.0.204 dev.

[Robin S]

@lele_ballack, I believe it's a bug with the field export/import for repeaters. I opened a GitHub issue here: https://github.com/processwire/processwire-issues/issues/1792

[lele_ballack]

Thank you @Robin S for opening the issue on GitHub, I feel a bit less crazy knowing I'm not the only one with this issue as I was nearly losing my mind! 

[lele_ballack]

As a workaround for now, we could exclude the parent_id when importing a repeater, but it's important that this behaviour is at least well documented and pointed out during the import. 

[Robin S]

@lele_ballack, Ryan has fixed the issue in a recent commit on the dev branch.

[Robin S]

12 hours ago, NaomiBecker said:

Can you share the link where it is fixed?

Not sure I understand the question.

You can install or upgrade using the dev version to get the fix.
https://processwire.com/download/core/
https://processwire.com/docs/start/install/upgrade/

Or if you want to look at the specific commit it is here: https://github.com/processwire/processwire/commit/a2d5d62131cb94d5a5955f2ace4ba4d37947616b