elabx

This works?? $data = $event->arguments(0);

I think I just have never used it before haha, but from what I know of it it does look like it could do the work.

I don't think there is a "best practice" written down somewhere for this sort of scenario. I agree it can be confusing to figure out the "right solution" when there would seem to be so manyw ays to achieve the same. If all the values from the identifier are okay with being a text type value, I would go with a Table field with two columns, a Page Reference that fills its options with the "catalogue" of "possible IDs" and a text field that acts as the field for the actual value, this way you can have whatever fields you want on each organization, and you can do stuff like: $pages_with_

@benbyf I'm still using it without issues! And even use it with @bernhard's RockMigrations . I think there is an issue with the composer install related to composer 2, but you should be able to install it like a normal module. EDIT: @benbyf dude I completely tripped and was thinking I was in the old Migrations module thread lol Nonetheless, I have also used this project a lot and noticed it breaks with most recent php version, I think 8+

Could you do a search through your codebase to find if somewhere you might be assigning that property to the page (a typo)?? At east it happens to me sometimes that I swap a variable's words like that lol Came for the title, stayed for the issue 🤣 Like, wow what's FieldtypePhantom

That was one of the first games I had on PC!! I was like 10 or something, I couldn't believe there was such a funny game haha, it really opened my eyes to what could exist as a videogame. Now I'm thirsty for some table melting quality grog.

Is the repeater set in the projects template? Maybe a screenshot of your template/repeater field config could help!

They are, you need to configure that inside the repeater field, on the Details tab where you add the actual fields for the repeater, click on the field's label/name and it will popup a configuration screen that will be set the configuration in the context of the repeater field. (in case you use the fields in other places, for example)

Wouldn't this be the concept of a template, that has the 15+ fields you need. So on your page tree you could end up with something looking like this: - Cards (a page with a template called cards-display-page, without any other field aside from title) -- Card 1 ( a page with a template called card, with the 10+,15+ fields you need) -- Card 2 (another page of type card, ready to be filled) Since you seem to be new to ProcessWire (at least from what I perceive on your posts!), maybe you are not familiar with the idea that a Page can also be just a sort of "data bucket", it doesn't r

Hi @spercy16! Are you super sure tall_card is the name of your repeater field? It seems to be a non existent object.

That's a very good question haha, it just happened to me just today when moving a live site to local development for some upgrades and found the recommendation around the forum, I didn't dig much deeper into the exact issue with the fingerprint and the change of environment. Though I can tell you I noticed that had to be related to the fingerprint because the session log shows a message about it. You should still be able to something under /site/assets/log/session.txt. I can also tell you that those lines are not originally on the file because the site/config.php file is sort of an

Can you try on site/config.php: $config->sessionFingerprint = false; $config->sessionChallenge = false;

I remember this topic being one of those moments of "enlightenment" when learning processwire haha.

Move the page in the tree to be sibling of Pages, like you would with a regular page.

Related: https://github.com/processwire/processwire-issues/issues/550