PagefieldPairs - Synchronize Pagefields between two different Pages

[bernhard]

This module comes in handy when you need related pagefields that are dependant on each other.

Example: you have a sports team and team members belonging to that team. you need 2 fields: one on the team-page, one on the member-profile. this module keeps both fields in synch. Other examples would be hierarchical company structure or any other kind of membership relation.

Demo:

settings in this example:

 

Gitlab: https://gitlab.com/baumrock/PagefieldPairs

Modules Directory: asap

only tested on PW3 and reno theme. Please test it faithfully before using it. please report any issues

[POWERFULHORSE]

Great to see these types of modules appearing. Similar functionality to ConnectPageFields? I was working on my own implementation but seems that's no longer necessary!

[bernhard]

oh man... exactly the same... i knew this would happen. not enough time to follow the forum and it seems it was not on pw weekly

also in this thread it was not mentioned  

thanks for your hint...

[adrian]

52 minutes ago, bernhard said:

it seems it was not on pw weekly

But it was in PW weekly

https://weekly.pw/issue/131/

[bernhard]

oh noooooo  

then it seems i was working too much on the todo-module

it's the first pw weekly i missed since a while... anywhay. it was not too much effort...

[adrian]

From the video demo it looks great, so good job regardless!

[bernhard]

yeah... it would have been one of my first really helpful modules. but @Robin S was faster ^^

maybe the todo-module, if not anybody beats me again  

[tpr]

Never mind! Practice makes perfect

[Robin S]

Hi @bernhard,

Nothing wrong with having two similar modules out there. I'm always looking at other people's module code because it helps me learn, and I expect others are the same. The more modules, the more to learn from!

I noticed your module has the same oversight that I just fixed in mine: a Page field doesn't necessarily return a PageArray (i.e. 'single' Page fields) so methods like has(), add() and remove() won't work in all cases.

 

[LostKobrakai]

5 hours ago, Robin S said:

Nothing wrong with having two similar modules out there. I'm always looking at other people's module code because it helps me learn, and I expect others are the same. The more modules, the more to learn from!

While that's true it's always a bit harder for the user as he has to decide which one to take. 

[szabesz]

3 hours ago, LostKobrakai said:

he has to decide which one to take

Not to mention that if you unite forces everyone wins, especially with such a much needed module. So I suggest Robin S leading the development with Bernhard posting lot's of pull requests  

[bernhard]

as there is really no difference between those two modules it's definitely better to stay with robin's version.

thank you @Robin S for your hint to ->add()