David Noble

Yup, in awe, just like everyone else! A great addition to a great CMS.

It took me a little while to work out exactly what this meant. Given that this is talking about moving the default homepage from the top of the tree it wasn't immediately clear to me which homepage template diogo and Ryan were talking about above. So just to be clear, my understanding is that what you would do is create a template for the page at the top of the tree - which need contain nothing more than Ryan's code above. You would then create a new "home page" template for the page you actually want to be the home page. Perfectly logical when you think about it - but I'm a bit slow

Thanks for all the suggestions. ProcessWire certainly has an active and helpful community behind it! Cheers

Hi, Thanks for the excellent tutorial. There's one question I'd like to ask, as I haven't been able to find the answer in the forums or API documentation. I have included a hidden field on my form (using InputfieldHidden). This works fine, but displays a label for the hidden field (which I don't want). It uses the name/id for the label. I have tried setting the label using $field->label = '';, but it still displays the label. Is there anyway to prevent this? (I could make it disappear using CSS, but would rather it wasn't there at all.) Just by way of explanation. The form has three fields for providing a phone number, email address and street address. The person submitting the form has to supply at least one of these. I have a test to make sure that is the case in the field processing and set an error if this is not the case. The three fields are in a fieldset, and I tried adding the error to the fieldset (for which I set an id and name), but that doesn't display the error message on screen when the form is submitted. It also doesn't make sense to add the error to one of the three existing fields. So that is why I'm adding a hidden field. If there is an error I attach the error to the hidden field, and on submission the error is displayed in the location of the hidden field - which is great. It's just that the hidden field label is displayed too, which I don't want. (The label displays when the form first displays too - not just when there is an error.) Any suggestions appreciated - including any better way to achieve this outcome. Thanks!

Hi all, I just wanted to let you know that I've implemented the solution you helped me out with above, and it works wonderfully. I now have a site ready to move from development to production. I can't believe how easy it has been with Processwire. I've been able to implement things that were just way too hard to bother trying to do in some other CMSs. Again. Thanks for all your help!

Thanks everyone for you help! I'll have a go at implementing it

Hi Marty, Thanks for the quick reply. I'm not sure I've explained what I'm trying to do well enough. I can see how what you've suggested would help me if I wanted to show blogs with a publish date that was less than today. What I'm trying to do is set the "publish_date" when the status of the page changes to published (or from unpublished I guess). That way I can retrieve the publish_date and display it on the page eg: "This page was published on: 30 December 2012". Cheers

Hi, I'm a totally new user of ProcessWire and I'm just starting to migrate an existing site. One of the requirements is to to show the "date published" on pages on the site. This is the actual date published - not the date it was created or modified. As there does not appear to be a field that holds this date I imagine that I will have to create a field and include it on my templates (which is very easy to do with this system). My question is - how would I go about populating this date? Is there anyway to hook into the publish event? (I've looked through the API, and I can see that I can hook into the save event. I've also found the code in the ProcessPageEdit module that works out the page is unpublished, and gives the option to save and publish, but I'm really not sure where to go from there.) Any help greatly appreciated.