Leaderboard

<div id="content"> <?php // get all children as $child foreach($page->children() as $child) { // get all images and output the single images foreach($child->get('images') as $image) { $thumb = $image->width(250); ?> <div class='favs'> <a href='<?=$image->url?>' data-uk-lightbox="image"> <img src='<?=$thumb->url?>' alt='<?=$child->title?>'> </a> <div class='text-favs'> <span><?=$child->title?></span> </div> </div> <?php } } ?> </div> Something like this ? I think you should have another look at the php foreach function how it works ?

Hi @DrQuincy Add check_access=0 to your selector string. Gideon

Note: This feature has been moved to RockSettings --------- Every site that I create needs some kind of links in the footer. It's not much work to create a page reference field for that, but it's not much fun as well ? That's why RockFrontend creates a "footerlinks" field and adds it to the home template for you: With the latest commit you can easily access those pages in your template file: <ul> <li n:foreach="$rockfrontend->footerlinks() as $link"> <a href="{$link->url}">{$link->title}</a> </li> </ul>

No, the idea is that RockFrontend is unobtrusive. That means you should be able to install it without any unwanted side effects happening. If you find anything that violates this concept let me know ? But if you update and check that box for "footerlinks" you'll be able to call $rockfrontend->footerlinks() in your template files ?

In version 2.9.1 I have to manually enable this feature and others. Will this be enabled by default now?

If you are using custom page classes since v206 there is the "getPageListLabel()" method: https://processwire.com/blog/posts/user-activity-v6/#core-updates

The place is Modules > Core > ProcessPageList Thanks.

I took a look at the WireMail class and what I miss is SMTP support (although I might be wrong here, I simply didn't see anything in the docs that implies SMTP is supported out of the box). I could also use the module named WireMailSMTP for example, but no matter how you cut it that would involve installing the module manually for each website. It's preferable to me to manage dependencies with Composer and reuse our existing mail scripts, then installing PW modules manually for each project.

Works like a charm. Thank you very much.

Perfect, thanks!

No, conditional hooks are great. I just tried to show that this: Pages(template=foo)::saved is wrong and this is the correct version: Pages::saved(template=foo) See https://processwire.com/talk/topic/18037-2-date-fields-how-to-ensure-the-second-date-is-higher/#comment-158164 and

Hello @torf, I pushed an update a minute ago. Please have a look, if the issue is resolved. Happy new year.

Here's one of my latest projects: https://petibol.pt/ Petibol develops and produces of all types of EPP (Expanded Polypropylene) and EPS components and packaging for various industries. This website is a collaboration between Supertiny and GOdesign. Super simple approach: The frontend is just SCSS and vanilla js "components" (no libraries), and pages are built with a blocks system based on a repeater field. Having tried a bunch of stuff between building this site almost a year ago and publishing it (Tailwind, AlpineJS, VUE...) it's pleasing to return to this site's code and compare the approach. Here I've basically set up Laravel Mix to compile SCSS, join and minify a bunch of <1kb js files. A BEM style approach to the styles so that I have a bunch of preset variables for typography, spacing and whatnot, and the JS files follow the same logic of identifying components like the hamburger or the parallax effect by looking for specific data-attributes and going from there. Super clean, performant, and couldn't be easier to pick up and maintain.

https://processwire.dev/integrate-composer-with-processwire/ maybe this helps you

@bernhardI just haven't gotten to it yet, as it requires a PageFrontEdit module update rather than a TinyMCE one. I also have to update ProFields Table, Multiplier, Textareas and Combo to support TinyMCE. Once all of these are done we'll merge the TinyMCE module into the core.

I don't use SEO Maestro, but I installed it on a local mirror of a simple site, added a field using it to the basic-page template and put it into the body of the relevant Latte view. Out of memory error! A bit more investigation led to the module's BreadcrumbStructuredData.php, which creates a template named structured_data_breadcrumb.php. That causes a fatal error, as there is no associated Latte view file. The solution is to add "structured_data_breadcrumb" to Ignored Templates in the Template Latte Replace module settings. Having done that, no problem outputting the SEO data in the page, or adding {$page->SEO|noescape} to the head of the @layout file.

Hi @ryan, this module is very big time saver for me. I'm also a fan of ProFields Combo and i use both of these regularly. My question is that is there any plans to add support for Combo field type? Now i have to do multiple conversions and helper fields for imports if i want to use Combo fields. I have got the impression that it shouldn't be too hard for this field type?

Just in case someone else wants to do something like this, I just wanted to note that hooking before ProcessPageEdit::execute and foreaching through wire('breadcrumbs') works well. But for my particular needs I had problems with this approach and the Reno theme and so had to take another approach which worked: hooking after Process::breadcrumb Anyway, thought it might be useful info for others.