apeisa

Selector was this: $page->find("template=gallery, gallery_images>0 limit=4, sort=-created"); And it was run on page which had two children (neither of those were galleries, but gallery-categories). Something like this: $page --> category1 ------> imagegallery (found) ------> imagegallery2 (found) --> category2 ------> imagegallery3 (not found) And if I remember correctly imagegallery3 was the one which was moved from category1 to category2.

This happened to me again. There were some template changes and moving pages around and after that lot's of confusion why my selector didn't work as expected. Running this fixed it. Running on almost latest version of P21.

I noticed nice little touch that Ryan had added to the latest build: lock icon on pagelist. I first thought that it means pages that have different access management than it's parent's, but it is indicating locked pages. So, it would be great to have on top of that also Key-icon for pages that have different access management than their parent. Any thoughts? Here is screenshot how it works now, so there could be new key icon with same style, if there is different access settings.

I think you are doing great job and keeping amazing development speed with Processwire: I don't remember even single forum post / email that you would have ignored - and you are doing this on top of client work & family. And I think the speed how fast processwire evolves is a very good one. Thinking how much have happened since January: upcoming 2.1 feels & works very well (and there is some pretty major changes compared to 2.0). Not to mention all the small fixes and improvements... Yes, I agree with this. I think there are many silent followers also, since many people how joins this forum seem to have developed quite a lot with processwire. And that makes totally sense - it usually takes months to find time to try new software, and even more time to find good real projects for them. And we are fighting on a crowded space: there are quite a many php based content management systems out there And thanks for the compliments. I am also (and the company where I am working) very committed and will definitively do our best for processwire. I like that idea, maybe not yet - but next autumn maybe? Also - creating even an association to support the development could be good idea from the early on (not yet, but maybe starting 2012?). It doesn't hurt to make things look little bit bigger than they actually are. I think one thing that is needed is some kind of news/blog section. Now the site feels static - it doesn't feel vibrant. Only thing that is moving is forum - the site should be also active and at least few people creating news. I would be very interested to take part in bringing this site to next level, as a collaboration project. We just need right time for that - and I think that would be right after 2.1 and lang support (2.2?). Here are some great designers on forums (almonk, adamkiss, probably many others too). I think this is one of the most important things right after we get little more popular. We can do a lot to support this kind of progress: Maybe donation buttons for developers, right from processwire.com module download page? Possibilities to co-sponsor module development ("I need this kind of module and I am willing to pay")? Partner network (these freelancer & agencies work with Processwire)? Also - installation profiles will be important. "How to create a blog?" - well, install "blog profile" and see how it is done. "How to create product catalog / portfolio?" - well, install "portfolio profile" and see how it is done. I think we already have here great product and lot's of talented people on board. Also, many things are in better shape than most os-projects ever get: things like good and pretty comprehensive documentation, common place to share ideas (this forum), newsletter (although not yet active) etc... This is also good topic to tell that our company (www.avoine.fi) is co-sponsoring the language support development this summer (for 3000$), so that Ryan can give it little bit more time from client work. We are also looking for other opportunities whenever we can to help processwire grow. We are currently hosting about 200 sites on our old platform, and looking to create many many sites on top of pw. Also - we are committed to open source all the stuff that we can.

I'm little old school here, but I believe that good content brings followers. This means - of course - that pw will continue evolving and being the best cms there is. But also more quality articles and tutorials need to be written. Also more open source examples (full sites) would be great. Like the often required easy to follow "how to turn this design to pw site" -tutorial. Also other articles would be great - if they are well written and touch other popular topics. I mean posts like "Processwire and Drupal compared", "Building blogs better than wordpress", and all the stuff that Ryan has written here on the forums (like using pw with ajax etc). Also trying to get these topics to popular sites. Well written introduction tutorial on nettuts would bring tons of people to processwire. Processwire.com is great site (clean looks, lot's of quality content, great documents etc), but it could be more attractive for first comers. I remember that it was second time when I stumbled to processwire.com when I decided to download it and try. First impression from the site was that it was something too small (on scale with pulse cms, perch etc) for our needs. I think that front page should be more "proud" about all the strengths that pw has. It needs superlatives "Super easy user interface - your client can manage complex data in easy manner." "Flexible data modeling - you can build anything" "Relations - easy cake!" "Does it scale - yes, there are huge sites build on top of pw!" "100% Control over your markup." "It's actually a great framework, even for command line use" "More flexible than drupal, more simpler than CMS made simple." Something like that. I'm not native english speaker or copywriter, so these examples are probably clumsy and naive, but you got the idea. Ok, these are pretty much all covered here, but these should be mentioned clearly and in marketing spirit at the front page. I think that these guys do pretty good job with their site: http://symphony-cms.com/ (although many probably disagrees about how great it is to use xslt, but that is what makes it different and they want it to be clear)

Ryan: thanks for your detailed (read: complete) example again! I ended up for even simpler solution here. In this case it will be always "yes" or "no" answer, so this went with super simple page where title = question and also two hidden integer fields (yes & no). I created simple ajax voting (works without js also - though I might change this, if it seems that bots and spiders are too eager to vote) here. Almonk: yes, in many scenarios (like images, files & comments currently) repeatable elements are very much needed. Often we can get good solution with different pages, but it really shows it's limits when things get more complicated than simple poll. If you would need new page for every image, it would be messy to have anything else under that page. But matrix is not very simple scenario, as we know. Currently focus is to get 2.1 out as stable version and after that hit language support. But I would love to use something like matrix in EE is in PW.

This is something that I thought also. And I do have "publish date" in news/blog post type, that is used. But this is actually more complicated issue. We do need some basic workflow baked in (nothing more complicated than published/unpublished), since this is how it actually works now (but is unclear). If there isn't any clear default (or the default is "always published unless developer does some special stuff in api") then you have to think this published/unpublished on every time you do your selectors. It would be clumsy on most sites. And this is so common need (I think that 80% sites needs some kind of draft/unpublished solution), so doing this in core is reasonable. I agree. I don't think it has worst interfaces, but it is complicated for average joe, and "blog roots" shows in many places (as a positive & negative). Processwire's strength is in totally different area than wordpress has. I think most important thing is that person who creates page can be sure if his new creation is going live right away or can he test and play with content safely. I added one more screenshot (vanilla Drupal 7.0). This is actually pretty good solution (if you strip down all the other stuff than published setting )

Yep, it should be unrelated, but since there is now way to keep page as unpublished, but still add content & save, then this is currently only way to prevent the page being 100% published. And the fact that you need to save page once before you can embed images to rte-fields makes this painful. Good to hear this. I think that "two buttons" is very much needed here. Of course there should be clear default & alternative action, so that this won't be too hard decision. I wanted to take a look how Wordpress handles this, and it is actually pretty messy (although it shows lot's of possibilities to user): I also quickly sketched something how this could work in PW: As we can see this is minor change in the UI, but will be super helpful in some cases. We also have to think carefully about what to say in notifications. I think one reason this happens is, that first notification is: "Created page /new-page/ with template page". I think we shouldn't show that at all, only something like this: "This page is not published. You will have to publish this page before it is visible on the site." I also think that there should be possibility to preview the unpublished page if you have an edit access. It is otherwise very difficult to know how the page will look, if there is lot's of "freeform" content, like rte-fields with images etc. And about terms used: I think we need to settle for "unpublished" or "draft", not to use both if we mean same thing. I vote for unpublished.

Thanks for this Ryan, very helpful. I actually have used this function to define if page was loaded from ajax: function isAjax() { return (isset($_SERVER['HTTP_X_REQUESTED_WITH']) && ($_SERVER['HTTP_X_REQUESTED_WITH'] == 'XMLHttpRequest')); } But I assume $config->ajax does about the same (checks the headers for XMLHttpRequest)? Also: it would make great module to return all fields as JSON (also Page references). It would make super simple to create read API:s with PW (not that it is difficult now).

Nice little site! I think this shows really the strengths of processwire: it scales for super large sites, but also works very well in small sites like this - gives benefits that most simple content management software couldn't give! I would actually use processwire even for single page websites!

Oh there is! Haven't noticed those before, they are well hidden

Great stuff Actually, we should start discussing soon (maybe after 2.1 release) how we get PW more popular! I would love to see more module developers and people contributing.

This is the post that helps you create this outside the admin: http://processwire.com/talk/index.php/topic,75.msg1438.html#msg1438 But I think that Ryan's solution is more elegant (less code, only one admin etc), and in this custom admin scenario you should code that access stuff by yourself (although it should be relatively simple).

There is some off topic discussion using pw inputfiels & templates outside admin. Would be perfect in your case, I think. At least my need was pretty similar.

There is. See the "form generator" topic. I would link but using from phone...

Easy fix coming, not available yet.

Well, there is a notification, but little bit small one. Also other parts of admin doesn't indicate these unpublished pages at all (like pagelist). I do agree that this is clumsy and unclear, but there is easy fix for this... See the other topic in this area.

Nope, it is not a horrible idea You actually understood it little wrong. If you save as draft, then it will stay "unpublished" so there will be two buttons also next time you edit a page. UI is something that need to be crafted carefully. Probably something like green button for default action (save & publish), but only light text link for save as draft function.

There are some weak points on how processwire currently handles page status (I'm talking about 2.1, not sure how things work in 2.0). After you give page name, you are taken to edit view, but page is not published yet (means it is not visible to site visitors). But after you click "save" first time then page gets published. There are couple of weak points here: 1) You cannot add images before publishing, because image uploads require page saving 2) If you want keep page as a draft, you have to set status: hidden, which is (if I'm right?) little bit different from unpublished. It is also clumsy and hidden behind settings tab. 3) This is really unclear and actually difficult to explain why it works this way (other than "you don't want to publish empty page") How it should work (this came from our client, but I liked this flow): 1) First step just like it is now, just name and continue 2) Now you have same notice "page is not published yet", but now there is two buttons: => "save as draft" (this keeps page unpublished) => "save and publish" (works similar to old save) 3) After page is published, there is only one save button like there is now. And there should also be setting to unpublish page. Difference between unpublished & hidden is that hidden is just hidden from search & navigation etc, but unpublished is actually only available for users who have edit access to that page. What to you guys think? Also, I'm not sure if I got all points right or I have misunderstood reasoning for current flow, but this would make more sense I think.

This is great news! I had training session for our client how to use processwire and there were 14 people listening. This was one of the first questions there, so great that there is a solution ready. I have some other good points from client, but I put those on other topic.

Thanks Ryan. New template.php didn't fix it, but moving that template change to init fixed it. I will commit this sooner than later to Github (will test on 2.0 first).

Client needs to create simple polls (or questionnaires) like this: Choose what describes you best: 1) Awesome 2) Smart 3) Polite And then on the site people can click on one options and see results. I started to think that this should be done with pages, where poll is just template. But what is difficult now is to create those options (this goes back to "matrix" again, I think). So we need 2-n options, which should have title, but also value inside. I'm in little bit hurry with this one, so I am ok with not-so-perfect solution. My plan is to create new FieldtypeValueKey, which holds just text title + value. These should also work like images, files etc, that you can put more than one in one field. This FieldtypeValueKey should be usable on other cases than only polls, so I think it is better solution than custom poll module. It is nowhere near "matrix" vision, but could prove useful. If there is simpler solution or something else I haven't figured, please tell me now I'll probably code this during weekend / tomorrow.

In case that someone wants to use this in 2.1: it works nicely, but only for superusers. This is how you get it working for your client (if you don't want to give superuser permission): Create new permission: redirects-admin Edit ProcessRedirects.module, add to line 14: 'permission' => 'redirects-admin', Then add that permission to roles you want to be able manage redirects. If setup page is not showing, then you need to edit admin-template and give access there also (too lazy to test this one).

One more reason to like this setting: if you have some pages along the path that user doesn't have edit access (but has view access), then clicking on those pages will give him/her a empty page with warning: "You don't have access to edit this page".

Yep, that fixed it! (well, needed to put $home->setOutputFormatting(false) also to get that snippet working- just mentioned here for reference). I have created many templates, fields, pages etc.. so difficult to say when this has occured...