Jump to content
jds43

Page Reference field to supply select options on front

Recommended Posts

Hello, I'm trying to list the categories, on the front through select options, that have been selected by page reference field (multiple pages PageArray) on the child pages.

Things to Do (would only display three, six, seven, nine in select)
-thing one (-category three, -category nine)
-thing two (-category six, -category seven)


Lodging (would only display one, two, three, four in select)
-lodging one (-category one, -category two)
-lodging two (-category three, -category four)


Dining (would only display five, six, seven, eight in select)
-dining one (-category five, -category six)
-dining two (-category seven, -category eight)

Categories(hidden page)
-category one
-category two
-category there
-category four
-category five
-category six
-category seven
-category eight
-category nine
-category ten

$categories = $pages->find(1129)->children('include=hidden');
foreach($categories->references('category') as $ref) {
    echo $ref->title;
}

This selector isn't working, but it seems 'references' would be helpful. I've never used it before, so I'm not sure how to employ for this.

https://processwire.com/blog/posts/processwire-3.0.107-core-updates/#page-gt-references

Share this post


Link to post
Share on other sites

The below assumes that your Page Reference field on the child pages is named "categories".

If you want duplicates or don't care about duplicates:

foreach($page->children() as $child) {
	foreach($child->categories as $category) {
		echo $category->title;
	}
}

If you don't want duplicates:

// Create empty PageArray that will hold the categories
// By default each page can only exist once in a PageArray (hence no duplicates)
$categories = new PageArray();
foreach($page->children() as $child) {
	$categories->add($page->categories);
}
foreach($categories as $category) {
	echo $category->title;
}

 

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

Thank you Robin S! You've saved me many times over the years.

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      Page Reference Default Value
      Most ProcessWire core inputfield types that can be used with a Page Reference field support a "Default value" setting. This module extends support for default values to the following core inputfield types:
      Page List Select Page List Select Multiple Page Autocomplete (single and multiple) Seeing as these inputfield types only support the selection of pages a Page List Select / Page List Select Multiple is used for defining the default value instead of the Text / Textarea field used by the core for other inputfield types. This makes defining a default value a bit more user-friendly.
      Note that as per the core "Default value" setting, the Page Reference field must be set to "required" in order for the default value to be used.
      Screenshot

       
      https://github.com/Toutouwai/PageReferenceDefaultValue
      https://modules.processwire.com/modules/page-reference-default-value/
    • By Pip
      Hi, Everyone! 
      I'm currently working on a page reference field and set it for multiple pages (AsmSelect) for the input. Is there a way for me to add an image field (aka Avatar) and the title of page in the radio button? 
      I used the field name enclosed in the { }. Didn't work. It appeared a text instead. 
      Thanks in advance and hope to hear from you soon!
    • By jonatan
      Hi! 😄
      SITE SETUP / DESCRIPTION:
      What? Online art magazine with an "All featured works" and also an "All featured artists" index page, and also individual "Work" and "Artists" pages, and data relations between the different artists and their artworks.
      So, I have two different page reference fields, connected by @Robin S's awesome Connect Page Fields module (though that has nothing to do with the issue in fact, Robin's plugin works great! and the issue is the same with or without it).
      The two Page Reference type fields are called "works" and "artists". They are meant to simply connect different artists to different artworks.
      Fx:
      Work 1  (page)  –> artists (Page Reference field) : Artist A (page)           --->>> (automatically connected)         Artist A (page)  –> works (Page Reference field) : Work 1 (page)
      Work 2  (page) –> artists (Page Reference field) : Artist B  (page)           --->>> (automatically connected)         Artist B (page)  –> works (Page Reference field) : Work 2 (page)
      ISSUE:
      On both Page Reference fields, both on "artists" and on "works" this option "Allow unpublished pages" is activated:

      As it says in the option description, supposedly, unpublished pages should be selectable in the page reference field, but they should not be visible, they shouldn't appear, on the front-end...
      Frontend:
      To show all works related to the artist on the artist individual page I'm doing this:
      <?php foreach($page->works as $item) { echo "<img src='{$item->image->first->width(200)->url}' class='pr-2'><a class='pr-4' href='$item->url'>$item->title</a>"; } The problem is now, unexpectedly, if some work is set to "Unpublished", it shows up anyways!
      WORKAROUND:
      So to get around this I figured out that I can do this:
      <?php foreach($page->works as $item) { if($item->is(Page::statusUnpublished)) { return; }; echo "<img src='{$item->image->first->width(200)->url}' class='pr-2'><a class='pr-4' href='$item->url'>$item->title</a>"; } But ofc this is a rather inelegant "solution" which shouldn't really be necessary, right? 
      I might be missing something basic here, but really can't figure out what it is... I hope one of you awesome guys can help me out 😊
      Thanks a lot in advance!
      All the best,
      Jonatan
    • By Flashmaster82
      Hi, can you guys help a beginner with a problem..
      On my template (profile_page) i have a dropdown (page reference) where i can choose a sports team (team_page) that is related to that profile which is also its parent. Then on my Competition1 page (competition_page) I have page reference field (profiles) a dropdown that i want to display only profiles that has choose a specific sports team (template=team_page) the page parent to be specific.
      Structure/Template
      Sports_team1 (team_page)
           Profile1 (profile_page)
           Profile2 (profile_page)
           Profile3 (profile_page)
           Competition1 (competition_page)
       
      ready.php
      <?php $wire->addHookAfter('InputfieldPage::getSelectablePages', function($event) { if($event->object->hasField == 'profiles') { $relative = $page->parent->name; $event->return = $event->pages->find("template=profile_page, sports_team=$relative"); } }); ?> This returns with no results in the dropdown. If i remove sports_team=$relative then it displays all profiles that have profile_page as template, so it works almost. But i will have more sports teams so this is just an example. I only want to display the profiles that has choosen the parent team on there profile page in admin not front end.
      I hope i was able to explain it so you guys can understand a little bit. Need some help please! /Thanks
       
       
    • By MaierGrem
      Question to professionals)
      I use the "Page Reference" field (name = categories, types = multiple, asm-select) and checkbox field (name = notify_user).
      When editing the page, I need to check if:
      - (categories) values has changed (deselected one or more current pages), make (notify_user) required.
      - (categories) values has changed (selected one or more new pages), make (notify_user) required.
      - (categories) values don't change, then the (notify_user) is not required.
      I tried to make a condition, required if:
      1. "categories!=1020|1490" - does not work.
      2. "categories!=1020|1490, categories.count != 2" - does not work.
      3. "categories%=1020|1490 - js error.
      Please advise how best to solve this problem.
×
×
  • Create New...