t0b1
-
Posts
4 -
Joined
-
Last visited
Posts posted by t0b1
-
-
Thank you so much!
I was quite confused by the behavior of LazyCron and the content of LazyCron.cache, this helped me a lot :) -
2 minutes ago, t0b1 said:
$wire->addHookAfter('InputfieldPage::getSelectablePages', function($event) { if($event->object->hasField == 'top_menu_entries') { $page = $event->arguments('page'); if($page instanceof RepeaterPage) $page = $page->getForPage(); $event->return = $page->; } });
The last line was supposed to be $event->return = $page->fullpage_sections;
fullpage_sections is my Repeater Field- 1
-
Hello there, and thanks for ProcessWire!
I'm getting to know ProcessWire while doing my first project using it and I really like it so far.
The challenge I'm facing right now is the following:I have a One-Pager using fullpage.js, realized as a single PW-Page containing a Repeater Field where each Repeater Item is one Section.
Some Sections are supposed to have a little menu at the Top which references/links to different Sections of the Website, so I wanted to use a Checkbox Field "Top Menu" to decide if a Section gets a Menu and a Page Reference Field to choose the different Sections (Repeater Items) it should contain.
I've already accomplished this by pasting the following code into /site/ready.php:$wire->addHookAfter('InputfieldPage::getSelectablePages', function($event) { if($event->object->hasField == 'top_menu_entries') { $page = $event->arguments('page'); if($page instanceof RepeaterPage) $page = $page->getForPage(); $event->return = $page->; } });
The only problem that still remains is that when I select the Entry of the Repeater Item itself it doesnt save the selection, meaning after I saved it's unselected again.
On some Sections I do want a Menu-Entry for the Section itself though (which would be styled differently and not link anywhere) for Continuity-Reasons, any ideas on how to achieve that?
PageimageSource
in Modules/Plugins
Posted
Firstly, thank you for this Module, I installed it yesterday and it works well so far ?
Looking at the code I noticed that it's possible to pass a custom picture-opening-tag as the `picture`-options-argument, which I'm gladly using now to insert custom classes into the picture-element.
I was just wondering why that functionality isn't mentioned in your documentation ^^