Jump to content

ottogal

Members
  • Posts

    311
  • Joined

  • Last visited

Everything posted by ottogal

  1. As far as I know in PHP a quotient of integers with a non-integer value is treated as float. So I'd try to cast the $percent value: $percent = (int) $percent; or $percent = intval($goalNum / $raisedNum);
  2. Hi John W., hoping not to misunderstand your data structure: I'm sure that the Drs. are not in the Gifts businesss, and Mary's Flower shop ist not involved in physicians' tasks. So the hierarchy of your categories should be just like your wanted output (see the attached image). Then the individuals (Dr. Adams, Dr. Smith, Mary's Flower Shop) need only to have a reference field to the Secondary Categories - not to the Primary Categories. (Since Mental Health is a subcategory of Physicians, Dr. Smith automatically is categorized as Physician...)
  3. Saying "consider" and "should not", I tried to give advice - of course there is no "must not"... I'm aware that many and big players don't care, or see some benefits in their way to handle this. They ignore the arguments against it, and that is bad.
  4. Please consider that flags should not be used to distinguish languages! See the notes here, visit the links:
  5. Maybe this would do it: https://www.zeitverschiebung.net/en/city/2192362
  6. 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>'; }
  7. No problem here...
  8. Hi all, did I miss anything that might have happened in a few years in this context?
  9. 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!
  10. Thank you for the insight - I wasn't aware of this.
  11. Isn't it a rather common security consideration to not allow passwords to be pasted?
  12. The gain of "nicer looking" IDs is way smaller than the possible loss of consistency or risk of side effects not being aware of...
  13. 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!
  14. Indeed, that was the reason for the strange behaviour. Thank you, Ivan, for your help.
  15. 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!
  16. 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.
  17. $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) {
  18. 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!
  19. Hi all, something new in that context?
  20. 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...
×
×
  • Create New...