renobird

Would be awesome to have the ability to group fields and have them display nested like pages. Maybe an optional configuration that can be set via the fields module?

Hi Ryan, Does this currently allow for multiple feeds? I have a "master" calendar that has a lot of individual calendars.

Hi Ryan, Quick question about licensing. Would I need separate licenses for subdomains if they are current on different servers? (i.e. dev.domain.com and test.domain.com are on one vhost, and domian.com is on another.) Either way is fine, just want to know what I need when I talk to the controller of the purse strings.

Alan, YES!

Neeeeevaaaaah!

Hi Ryan, I hadn't ever really looked at the field visibility options, didn't realize there was "not shown in editor". Showing a message is a great idea — Thanks!

That's great news - really looking forward to this.

MadeMyDay, Glad to see this is still alive — really looking forward to checking it out.

MarcC, I used both MachForm and aMember, both have their strengths. I also like FormTools.

WillyC, This value is something that will get set when the user is logged in via a 3rd party authentication provider. I need superusers and admins to see the checkbox, but not be able to change it.

Hey Marc, Seems like you could build this with PW for sure, although building from scratch may be cost prohibitive. Please report back if you find a decent 3rd party solution.

That makes sense, the attributes for fields aren't stored in the DB, so you have to modify them before render.

I'm trying to set an checkbox in the user template to disabled via the API. Tried this: $user->of(false); $user->checkbox_name->attr("disabled","disabled"); $user->save(); Results in: Fatal error: Call to a member function attr() on a non-object

Thanks Ryan, Not sure what I was thinking this morning — thinking too much about the iPhone 5 I guess.

Hello all, A bit dense today, so hopefully someone can help me. I'm trying to show a list of all the roles a user has using the API. $users = $pages->find("parent=/processwire/access/users/"); foreach ($users as $user) { echo $user->name . " - " . $user->roles . "<br />"; } $user->roles returns a page array, so I get something like 1015|2263|2273 What I need is the name of the role instead of the page ID. Duh! $user-roles is an array, need to use foreach to return the name. Sorry, told you I was being dense today. As you were.

Your IRC will get used to it.

indeed it is.

Would it be possible to add this topic as a "sticky" at the top of the General Support forum? Might help promote the channel a bit, and give users another place to look for support.

Very nice indeed.

Multi-page forms and publish to pages — those 2 features would let me rebuild this beast of an ASP application I inherited sooner rather than later.

Ryan, This is incredible! Looks amazingly well thought out and super intuitive. I can't even begin to tell you how much I will use this — we have dozens and dozens of forms, and get requests for new ones all the time. I'd press the *like* button 100 times if I could.

Thanks teppo.

Good catch Pete. I'll get on them about that.

The /our-experience/ page shows the first project from each child page. foreach($pages->get("/our-experience/")->children as $project) { $image = $project->child->images->first()->size(286,190);; echo "<a href='{$project->url}'><div class='thumb'>"; if ($image) { echo "<img src='{$image->url}' width='286' height='190' alt='{$image->get('description|name')}'/>"; } echo "<h5>{$project->title}</h5>"; echo "</div></a>"; } Here's how I grabbed the prev/next images and titles in Processwire: if ($page->prev->id) { $prev = $page->prev()->child()->images->first()->size(250,175); echo "<a href='{$page->prev->url}' class='sub-nav-left'><div class='arrow'>←</div><img src='{$prev->url}' /><br />{$page->prev->title}</a>"; } if ($page->next->id) { $next = $page->next()->child()->images->first()->size(250,175); echo "<a href='{$page->next->url}' class='sub-nav-right'><div class='arrow'>→</div><img src='{$next->url}' /><br />{$page->next->title}</a>"; } A little bit of jQuery handles the animation: $('.sub-nav-right').hover(function() { $(this).stop().animate({ right: '0' }, 300) }, function() { $(this).stop().animate({ right: '-280' }, 400) }); $('.sub-nav-left').hover(function() { $(this).stop().animate({ left: '0' }, 300) }, function() { $(this).stop().animate({ left: '-280' }, 400) }); Edit: GAH! The code editor is a nightmare. Hopefully you get the idea.

Hi Ryan, Yes! *slaps forehead* that's perfect! Thank you! Using the page field would let me create a handful of unique mini-site layouts could easily be reused, instead of having to make a new one for each site. Something like: /templates/mini-layout-a.php /templates/mini-layout-b.php /templates/mini-layout-c.php /templates/mini-layout-d.php I need to use more descriptive names of course, but all of those templates could have unique layouts. Thanks again.