Jump to content


  • Posts

  • Joined

  • Last visited

scutter's Achievements

Jr. Member

Jr. Member (3/6)



  1. We converted the web site for Broomstones Curling Cub (Wayland, Massachusetts, US) at www.broomstones.com to ProcessWire last summer in preparation for the current 2014-2015 curling season. We only had time and resources to focus on the technical implementation details (membership management, league scheduling, sub requests, event management, etc) and not the graphic design. Though we did get some nice responsive features into the site - mostly in the member-specific area that the public can't see. But you'll see that in general we really don't have a graphic design. We'd love to make it look like a proper web site. I've seen many slick sites built on top of ProcessWire. While knowledge of ProcessWire isn't really needed for creating a design for our site, I figured I'd turn here first to find someone with design skills and PW knowledge. The types of pages we're looking to design: Public home page including upcoming events, info on club rentals, public club news Member home page including personalized schedule for upcoming league matches and non-public club news Public event pages for tournaments that we host Committee-specific pages Member profile pages Member profile directory page / profile photo browsing We'll integrate the design into our site. If you are interested, please email webmaster@broomstones.com. We'd prefer a fixed price arrangement. Thanks. --Sharon
  2. I'm hitting this issue as well, running 2.4.0. I'm just a couple of weeks away from publishing my site, so I'm a little concerned about upgrading to 2.4.1 dev (not stable) to fix this. Going into production with a dev version doesn't seem like a good idea. Any comments on how stable or unstable 2.4.1 dev is? Are people running it in production? Alternatively I could go hunting for the fix and patch my version. Thanks, --Sharon
  3. Interesting. When is the dev branch expected to be officially released?
  4. I hit this issue too with a custom selector that's similar to the "templates=user,roles=company" example given above. The custom selector was working in 2.3.1 and started to fail after I upgraded to 2.4.0. Seems like a regression. I worked around it with the custom php code workaround. --Sharon
  5. Using $users->find() also does not apply access control - when logged in as guest this returns all users. Thanks, --Sharon
  6. I've been exploring ProcessWire for the past week and really like the simplicity, power, and flexibility. The site that I plan to build will have a member login, and also a member directory. I want members to be able to view the profiles of other members, but guest should not be allowed to view the member profiles. I have a 'member' role defined and have added additional fields to the user template. I was experimenting with the access control for the user "pages", but wasn't getting the behavior I expected. I modified the user template to allow page view for the member role, expecting all selectors to filter appropriately. When I use selectors with a path for the users like this: $pages->find("parent=/processwire/access/users, limit=50") I get inconsistent results. The guest user usually ends up getting a non-empty page array, meaning it found users, even though the guest user doesn't have the member role, so should never get any users in the results. The results were fickle - some selectors worked as I expected, others didn't. I did a similar experiment with regular pages, not the user "pages", and the results were what I expected. The results of the selector are filtered appropriately based on the role of the user executing the selector - only users with the member role got any user results. The selector below worked consistently - guest never found any user pages since it doesn't have the member role. $pages->find("template=user") and I can add roles=member to remove the admin and guest users from the results. This is mostly a theoretical question on what's the right way to search for members, since I am also adding the member role restriction to any page that would browse or access user pages, so no non-member would ever run these selectors. But what is the "right" way to get the list of members with access control applied? Thanks, --Sharon
  • Create New...