ottogal

Aren't there missing the opening <li> tags? It should be foreach ($items as $item) { $content .= '<li>'; if ($item->front_position == $item->index() { $content .= '<a href="' . $item->url . '">' . $item->title . '</a>'; } $content .= '</li>'; }

No problem here...

Extremely helpful hint - thank you!

Hi all, did I miss anything that might have happened in a few years in this context?

That was the way they did it in other CMSs I used in former times - before I luckily found ProcessWire! It was like a breeze of fresh air after a long stuffy time... The dilemma you are in is to incline to habits you are familiar with. Try to understand the way PW works, and you will soon be convinced. (And as a next step: Try to convince the client...) All the best!

Thank you for the insight - I wasn't aware of this.

Isn't it a rather common security consideration to not allow passwords to be pasted?

The gain of "nicer looking" IDs is way smaller than the possible loss of consistency or risk of side effects not being aware of...

Sorry, but i have to pour some water into the wine: It works well only on my local installation (xampp), but not on the live site. With toggle_field=1 in the selector, the output is correct; with toggle_field=0 the output is empty, $posts->count() is 0. Considering a remark in https://processwire.com/blog/posts/pw-3.0.139/ I thought it could be necessary to make it a required field. But that changed nothing. Finally I got it to run correctly by editing the value in each single post (changing it to 1, save, changing back to 0 and save again) - at least there are not so many posts at the moment... Obviously setting the default value to 0 (directly at the creation of the field) has no effect at all. Just an hour ago I realized that the very same issue was adressed by @Nils Wiere in this post (and that I already asked back in June...): So further help is much appreciated!

Indeed, that was the reason for the strange behaviour. Thank you, Ivan, for your help.

Hello all, using PW 3.0.148 with the regular site profile for a blog, I got an an empty pagination output when I had a Toggle field in the selector. The Toggle Fieldtype was introduced with https://processwire.com/blog/posts/pw-3.0.139/ . The selector resulting in empty pagination: $posts = $pages->find("parent=blog, sort=-date, limit=10, toggle_field=0"); It worked well, when I replaced the Toggle field with a Checkbox field: $posts = $pages->find("parent=blog, sort=-date, limit=10, checkbox_field=0"); So the prerequisites for the pagination to work are given. The settings for the Toggle field were: Formatted value: Integer Label Type: Yes/No Input Type: Toggle buttons Default selected option: No Thanks for any hints!

I didn't say that would solve your problem. But it was necessary anyway. I'm not sure that how you're calling the function recursively is correct.

$page is the API variable for the current page you are on, so you can not redefine it here. Better take foreach ($children as $child) {

Welcome @bookie! This tutorial by @kongondo could be a good starting point for your intention: Don't worry if it looks difficult - it is not!

Hi all, something new in that context?

Good points - I did it. Danke @MoritzLost !

Ok, it worked ... till the moment when I (as Superuser) wanted to add a new User. I got the "Fatal Error: Call to a member function attr() on null" in this line of the hook: $title->attr('autocomplete', 'off'); As a workaround I replaced it with if ($title) { $title->attr('autocomplete', 'off'); }; That helped - but I feel unsecure if there's something bad still left. Obviously it's just because the user template doesn't have a title field...

Thank you so much, @MoritzLost, that worked - and I've learned again something...

Hi all,when an editor in the admin adds a new page and clicks the title input field, a drop down list would open to offer the formerly used titles. How can I prevent this? (It seems to confuse my editors somehow.) Thank you.

If you opt for using @Macrura's InputfieldSelectize https://modules.processwire.com/modules/inputfield-selectize/ then just follow the steps under "Usage":

You don't want to edit anything in the core - you would loose the modifications with the upgrade to a newer PW version...

You could try $parent_title = $page->parent->title; $items = $pages->find('template=items-ordered,supplier=$parent_title');

Stupid me - just didn't have that idea... Thank you, Zeka!

Hi all, I'm using the Custom fields for files/images introduced in PW 3.0.142. In the Editor, the only way to see that the image has custom fields is to hover on the thumbnail to reveal the Edit link. I have a special "editor" role for some user. When he opens the page for editing, I would like the custom fields of that image already be open and ready for being edited. Most likely I'm missing somethimg obvious - but how can I make this happen? Thank you ottogal

Hi Aleksey, one way to add a new article page would be: Open any existing article for editing and save it with the option "Save + Add New". The new page will automatically get the same template like the sibling one getting saved. But if there's no need for more than a few different categories, why not use an own template for each category? (And make benefit of the family settings). Good luck ottogal