martinluff

All we need to do now is clone you a few times Ryan so you don't keel over adding all these cool features...

Thanks for the info Ryan. Agree with you points for the roadmap - good to hear where you see it going. Also agree with your comments on using JS for pulling in Disqus or IntenseDebate... My understanding is there's a REST API for Disqus - but not had a time to explore it or see what features this includes - but I'm thinking it could possibly overcome the issues of a JS include? I guess the other alternative is to integrate something like commentics http://www.commentics.org/ (not that I've tried it - just did a quick trawl for PHP comment scripts)... Seems like comments could be handled more easily by a third-party SaaS or script than something like workflow or versioning for example (just thinking out loud here )

No problem Adam, all your time here is much appreciated and I know what it's like to be fitting in personal projects around a busy business (I know Ryan is in the same situation) I'm sure things like this will start to take shape as time goes on...

Rebecca - sounds great. Look forward to seeing the results and thanks for the kind offer.

jbroussia - I think Disqus is as good as any... has pretty much any commenting feature you'd need (plus a load of extras like 'reputation points' easy integration with main social networks and so on) and nice admin. Another plus is that it's very widely used so your users are likely to be familiar with the UI. Right now PW commenting system much more basic (not necessarily a bad thing depending on your needs). IntenseDebate being the other leading contender (especially since it's effectively part of the WordPress family now)... Adam, on the one hand I think it makes a lot of sense not to reinvent wheels and integrate something like Disqus (and I'd be interested in what your definition of integration covers - if it goes beyond the standard JS include and used the REST API to pull in the system then I'd be very interested...) I'm sure this will come up again when the subject of ecommerce gets raised On the other hand with Disqus you're calling an external system so can be a pause for comment system to to load after a page's content is visible and I've also encountered bugs in Disqus in the past...

Hi ritch0s - great you took the time to try the PW I think you're making good points... The great strength of ProcessWire is that you can mold it to pretty much any method of working you prefer - but that also makes it a little more challenging to grasp than systems where there's a more prescribed way of doing things. I think more tutorials will follow in time - remember this is a very new system If you've digested the stuff from Adam and Ryan and it's still a bit of a mystery - do come back and ask some more questions - I'll do my best to help out (I'm pretty new around here too - and nothing like trying to explain a new system to someone else for learning it yourself

Congratulations indeed! Great work guys...

I'd add a vote for this too, it's such a common request and seems a pity if client always has to hire a dev to build a few simple forms. As you say Ryan you've essentially a form builder in there in any case for the admin... Look forward to seeing your sample code for a contact form too.

Hi Ryan, would like to take a look at the basic comments system - any chance of a quick few notes on how to set up in templates plus any useful tips?

Ryan, Adam thanks for the info/ideas! Ryan, that's the sort of approach I'd started to think about... Will have a think about both approaches and see what I come up with. Thanks again

Any advice on the template setup if you want to create a mobile version of your site - e.g. at m.domain.com and assuming here I'd probably tailor a cut-down version of content in pages on the mobile site - as well as custom layout and certain tailored UI elements. Mostly here I'm thinking in terms of how to deal with the templates for the different versions of pages... Be interested in ideas (Ryan, Adam?)

@adamkiss - yes makes sense. I can also just add a little JS to alert users or do validation if leaving a field empty is likely to cause issues... @ryan, likewise, makes a lot of sense. Looking forward to seeing how the system blossoms as you decide how to implement (or for that matter leave out) features from PW1...

@adamkiss - gives me some ideas and helps me get my head round the system - thanks @ryan, OK makes sense and these are details rather than key issues + of course very early days

I'd be interested in the approach you suggest in PW if I want to make some fields in a template required so a page can't be created if they're empty?

Suppose I want to set a default value for a field - let's say I've a template for 'cars' and I have a text field for colour and 85% of the cars I sell are black; so each time I create a new car page it would make sense to have black as the default value in this field to speed up page creation. Wonder if it would make sense to have a config for some field types to set default value? Or perhaps there's just another easy way to do this?

Adam; just re-read the question - yes I think you're right, sorry for adding any confusion there.

Yes, you're probably right, must be getting a bit pedantic in my old age

Hey Apeisa, just wanted to say 'nice work'! This is a really nice feature to be adding - thanks

Couldn't you also use the code in the basic PW installation site where the sub nav gets generated by: <?php // Output subnavigation // // Below we check to see that we're not on the homepage, and that // there are at least one or more pages in this section. // // Note $page->rootParent is always the top level section the page is in, // or to word differently: the first parent page that isn't the homepage. if($page->path != '/' && $page->rootParent->numChildren > 0) { // We have determined that we're not on the homepage // and that this section has child pages, so make navigation: echo "<ul id='subnav' class='nav'>"; foreach($page->rootParent->children as $child) { $class = $page === $child ? " class='on'" : ''; echo "<li><a$class href='{$child->url}'>{$child->title}</a></li>"; } echo "</ul>"; } ?> So in this case it's checking if the section has sub-children rather than the page itself (plus there's an extra check in there for homepage that you don't really need I think. Anyway, hope that makes sense...

Thanks for the instructions Ryan - I guess these could be appended to the http://processwire.com/about/requirements/ page? Plus, I just wonder about including a warning that you might want to edit .htaccess with any new settings for ProcessWire rather than overwrite with an updated htaccess.txt since it might include other settings required on the server?

Music to my ears... so many other systems seem to put up unnecessary barriers by fencing off the user-related data objects from the ones used to manage all the other data in a system #makesnosensetome. Go for it Ryan! ProcessWire = more flexible than a yoga Guru... ;D

Looks like a great addition to the caching/performance side of things - thanks...

You might be onto something there. Or perhaps you've just been looking at too many skyscraper demo sites ;D

Great! Yes, I was kind of thinking that it's one of those things that sounds simple but has a number of implications. I think the matrix display is less of an issue - even if the fields were full-width one above the other then you'd still get most of the benefits...

Wouldn't it be possible to make available the user template the general content admin so attached fields could be modified in same way as any other template? (I guess you'd want an extra lock so you didn't accidentally change fields which would immediately disable the user admin by accident - but other than that adding/re-ordering like any other piece of content would seem in the spirit of the system esp. given the admin is pretty much built on top of the API in same way as any other content. Agree with adamkiss that we don't want to cripple the ultra-flexible model in PW