DaveP

A little tip for anyone wanting a drop-down arrow on submenu parents, like after 'About' below - just add something like this to your CSS. li.has_children > a:after { content: "▼"; font-size: 70%; padding-left: .5em; vertical-align: middle; }

That sounds like your PHP install doesn't include the GD library (which is unusual). How much control do you have over the server? Can you look at your phpinfo (http://php.net/manual/en/function.phpinfo.php) and check that GD or GD2 is installed?

PW puts no limits on your front-end design. Your resulting web site could be completely unstyled html, all laid out in tables or the latest cutting edge CSS3. That part is up to you. PW just organises your content and page hierarchy, if that is all you need from it.

One of the things to add to the excellent answers above is that a lot of what you will learn with PW is standard PHP, so it is a transferrable skill - not like a bespoke templating language that only works with one CMS, but a skill you could use in other circumstances.

I think you could use your code (with an addition) to create a selector value to use with $pages->find. Then replace doSomething(); with $selector .= $page->id . "|"; and after the end of the foreach rtrim($selector, "|"); to knock off the last (redundant) pipe, should leave $selector containing something like 123|456|789 which you can then plug into $pages->find for renderPager(). (Completely untested, but should work, I think. (I hope.))

Some purists might argue against echoing so much plain html, but as long as it works... There's a heck of a lot of my code looks just like that.

Take a look at yoursite/site/assets/logs/errors.txt. It should give you more information. Then, if you still need help, post the error(s) here.

I was speculating that the OP might have done the same as myself - not recognised the field inserted by the PagePermissions module as being relevant (I had assumed it was something that had been my experiment and I had forgotten about it) and had deleted it from the template. Then, because the module is still installed it errored in a very similar way to the OP. (Which appears to be the case from the OP and Ryan's comment.)

I have come across something similar, when I installed the PagePermissions module, then sometime later just deleted the page_editable field because I couldn't remember it being used for anything. Uninstalling the module fixed everything (of course). Just as an afterthought, is there a way for module-created fields to be locked against deletion to help oafs like me?

Just looking at the home page, is there some duplication of .js files? (and all those custom fonts and cufon?)

And worth mentioning <?php foreach($pages as $page): ?> // do something here in mixed html & php // probably a few lines of it <?php endforeach; ?> It makes code much more readable, but you would expect to use this most in output templates, where there is a lot of html going on.

Just clicking 'Like' doesn't seem enough. Ryan, you make it all sound so easy.

One of the many things I love about PW is that whenever new features are added they always make sense. Not just Ryan's excellent descriptions, but the additions themselves. In this case I especially like the $pages->add method.

Would http://processwire.com/talk/topic/3745-hanna-code/ help?

@nik is (of course) right. The 'start=0' in your selector will force it to always show the first (in this case) 2 records, regardless of what the pagination module would normally produce. By removing 'start=0', the module can take control of which subset of records are produced.

@cmscritic & @Ryan bit of a problem with the link rel='author' content.

You can always make a copy of a particular module, rename it and install it as a different module so you can change its functionality without losing the original or losing your changes if/when the original is updated. There is at least one thread in the forum on the subject but I can't find it just now, even thru Google.

One way I like to get around this problem is to have a 'list' template which just displays an unordered list of the page's children, like a menu, and use it for the parent pages (Employee, Department & Year). Then you can use breadcrumbs (good for usability) and it will allow an experienced visitor to navigate by editing the url if they so wish. I suspect it would also be helpful from an SEO and spidering perspective, but that's just a hunch. Depending on your navigation and menu structure, those pages might never or rarely be seen, but, for the work involved, it can't hurt.

Nothing earth shattering, but easy to implement. <ul class='breadcrumb'> <?php foreach($page->parents as $parent): ?> <li itemscope itemtype='http://data-vocabulary.org/Breadcrumb'> <a href='<?php echo $parent->url; ?>' itemprop='url'> <span itemprop='title'><?php echo $parent->title; ?></span></a> <span class='divider'>›</span> </li> <?php endforeach ?> <li><?php echo $page->title; ?></li> </ul> It's based on the breadcrumbs in the default PW profile, but the presentational markup is Bootstrap flavoured. Try it and copy the resulting html snippet into Google's rich snippets testing tool - http://www.google.com/webmasters/tools/richsnippets.

I know nothing about MODX, but I can really appreciate your hard work in putting this post together.

Flashdata thread http://processwire.com/talk/topic/970-flashdata/

Looks very interesting - http://alphapixels.com/prepros/ (Windows only)

http://security.stackexchange.com/ is well worth a browse in a free moment.

Me too. (At last, a semi-legitimate 'Me too' post!)

I love this translation