alan

Nice, thanks Soma.

Oo—gonna read both those. Instapaper'd.

Yes John, you'll be AOK with instapaper.com — a great place to keep articles about Skynet achieving sentience.

I <3 http://www.instapaper.com/

Will do do Ryan and thanks for the site, that looks good too.

THANKS for this Ryan, examples like this are so helpful to me. I've been so enthused by the power and flexibility of PW I've bought a book that was recommend here on the forum in the hope I end up needing less and less of these brilliant examples as time goes by Cheers!

@jan thanks for posting the correction! Yes I'm still loving PW too, and I think this will be a permanent thing, because of it's excellent API (instead of having to use lots of plugins like many other CMSs). Thanks for the suggestion, yes, I saw that numPageLinks and I assumed '0' would turn it off, but it doesn't seem to But I'll keep looking for how to do this

Welcome back Ryan

I found PW like this (and NO disrespect to Textpatten which I admire and have used to great effect): started a new project in TXP (Textpattern) went to do a couple of things that needed plugins and was tripped over by plugins not working made an executive decision that I had had enough of relying on plugins that generous people had shared but that inevitably they had sometimes stopped maintaining and decided, with reluctance, to train on EE bought $48 worth of video training and began to learn EE found EE was a little like a clunky version of TextPattern in some regards but inevitably due to it's commercial footing more complete and with an ecosystem of high-grade plugins — I was a little saddened to see I still needed to rely on plugins and even sadder* to see they often cost $30, $60, $+ (on top of the $300 for EE the client pays) but soldiered on and kept learning (*but I recognize that charging for good plugins is right in many cases) was Googling re EE and found Marty Walker's web site http://www.smd.net.au/ and as usual scrolled to the bottom to look at some meta and read "ProcessWire" and not EE, "Hmm" I thought clicked "ProcessWire" and never looked back Thank you Marty and thank you PW community for your help and most of all, thank you Ryan for creating, sharing and driving this superb project.

@jan and all, thanks, this thread finally got me started on Pagination, I've tried for hours and got nowhere until now and I don't really know why, this has been a hard problem to solve for my small brain. Now to loose the numbering and just have Next and Previous being in lumpt of 5 posts at a time (wish me luck )

Thanks, the code is beyond my limited capability, but it's interesting to know that this concept has already been looked at.

Good luck with the latest version, if you still get the problem then post to let me know and I'll try it here again, but with more pages. And happy Easter fellow Ontarian

On the topic of creating templates I have found, so far, that I generally use one/few PHP template(s) but refer to it with different PW Admin templates (using Advanced > Alternate Template Filename), of course using different PW templates allows me to do lots of stuff in PW. But often I actually want the same editor presented to a client, regardless of which PW template a page is using. As noted my solution is I duplicate the template and all is good. This however presents me with a small maintenance challenge, the lack of a DRY definition. E.g. After duplicating I now have two templates that I want to be the same but that can differ if one is changed and not the other, e.g. one has fields added or removed. At the risk of adding complexity, for these cases I would love to be able to 'Template Alias', that is, create a new Template in PW Admin that is locked (useable for an editor to add content but not editable by the Admin to change the Template) and the Template Alias always mimics the settings of the source template, taking on changes that are made to it, such as field removal or addition. This is likely an edge case request and so not worth doing, but it occurred to me more than once so I thought I'd note it both in it seems to have merit and also in case even if it's not directly useful maybe suggesting it will help in some way I've not thought of.

Thanks apeisa, I am not sure I always did in my hacking attempts so I will make sure I do now, I'll post back when if I get it working

I can't work out how to get pagination for showing batches of blog posts. I've tried adding pagination from the main page doc and some post examples but nothing happens, it's as if I had not added the pagination code. The URL I am trying to add pagination for is /category/cooking where /category/ is a real PW page and cooking is a URL segment (the template has Allow Page Numbers and Allow URL Segments ticked.) Without pagination I see all pages that have cooking in their category field, 12 of them. <?php $category = $sanitizer->selectorValue($input->urlSegment1); $blogposts = $pages->get("/blog/")->children; $categorized_posts = $pages->find("category.count>0, sort=title"); foreach($blogposts as $blogpost) { foreach($blogpost->category as $category_to_test) { if($category_to_test->name == $category) { echo "<h1>{$blogpost->get("headline|title")}</h1>"; echo $blogpost->get("body"); } } } I wonder if my problem stems from the examples always having a single object/array holding the pages and in my case I don't, $blogposts is a super-set and I use the inner loops and if(...) to find the ones I want? Any advice would be much appreciated.

Hi digitex, I am on v 2.2.0.1 and I just tried to emulate what you did, I created four pages, two I created and didn't even click publish (just left them as titles) and two I created, added content, saved, edited to untick-published. Then I left them a few minutes to make tea, then I returned and published all four. No problem. I have no idea if it's more likely to be your version not being as late as mine or something and I am sure Ryan/others more knowledgeable will comment more.

@jan Although it's only a tiny piece of evidence I am finding my use of a Repeater in a site I am developing perfectly reliable/stable. I had missed the point about avoiding cloning, thanks for pointing that out — as Ryan notes this will be worked on and I am confident ironed out as part of getting Repeating Fields out of beta.

Thanks Soma, I understand.

@Soma I looked but couldn't find in Google a page that covers 'permissions' and 'page-edit' http://goo.gl/Pw6ZB — if you think this is a page of documentation that should be added and if there is a place to note that I would be happy to go and note it — anything I can do to help. And just in case it helps anyone else, I also found (presumably by design as part of 2.1/2.2) that is indeed not true for 2.2, that is, I wanted to add permission for the module ManageFiles and I was able to add a Permission called randomname and the line "'permission' => 'randomname'" in the module file worked fine.

Thanks Nico for this module. Please may I ask, how I can allow a non superuser to see the 'Files' link in the admin? I've looked at hidden templates (etc) but can't see a way to do this.

Wishing you a totally r-e-l-a-x-i-n-g time — away from computers!

Thanks for this excellent walk-through Ryan. I am using a /tools/ pages (not visible to a client) to hide pages such as /search/ and /tagged/the-tags etc. This works fine, the only slight compromise is that any page I want to use for display below tools has /tools/ in it's url such as /tools/search/. Am I missing something simple that would allow me to 'collapse-up', hide the /tools/ part of the URLs for such pages?

Thanks Soma, I found both the tables I thought I didn't need or want were indeed not listed by name etc in table fields and so I went ahead and deleted both tables. All still working AOK. Thanks very much for your help. I don't know if a database administrator would worry about old tables getting left behind or not, if they would then perhaps this ought to be added somehow as a 'todo' on github passed to Ryan to decide on priority etc? If there's anything I can do to help (I doubt it as I have too few synapses then I'd be happy to, I could at least test new builds to see if I can break them

I don't see any references to "flags"? I'm using Navicat.app GUI which shows me this, and if I understand it correctly if I can't work out if they appear in fieldgroup_fields then I can't safely delete them do you think? Yes, I think so.

Excessive trying, that sounds like me One day I hope to upgrade to excessive succeeding... Btw, those things called: field_tagged field_tagging field_tags_alan are, I believe, MySQL tables not fields (PW naming convention).