
categories Page Reference field to supply select options on front
By
jds43, in General Support
-
Recently Browsing 0 members
No registered users viewing this page.
-
Similar Content
-
By Rossie
Hi Everyone,
I wish to display a gallery of images from multiple pages on the site. These images have custom fields created through page reference called 'furniture_list_type'. Each image now has a radio button which has been selected.
In the example code below all images appear from the "gallery20", however the selector "gallery20.furniture_list_type=3390" does not have any effect. "3390" is the id of the page reference "chair" selected through the page reference. I wish only images selected as chair to show.
Hope someone can help with this.
Thanks,
Calum
$imagePages = $pages->find("template=makers-child, gallery20.furniture_list_type=3390") ; foreach($imagePages as $p) { echo "<ul>"; foreach($p->gallery20 as $image) { echo "<li><img src='{$image->url}'>{$image->furniture_list_type}</li>"; } echo "</ul>"; } -
By dfile
Hello, i must count products per category like so:
category 1 (4 products)
--category 1.1 (2 products)
----category 1.1.1 (1 product)
and so on.
category 1 --category 1.1 ----category 1.1.1 ----category 1.1.2 ----category 1.1.3 --category 1.2 ----category 1.2.1 ----category 1.2.2 ----category 1.2.3 produkts have page references for the categories:
product 1 -- page reference->category 1.1.1 -- page reference->category 1.1.3 -- page reference->category 1.2.2 -- page reference->category 1.2.3 what is the best way to do this, i have many categories and many many products.
Thank you.
-
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
-