diogo

I was trying the user access on 2.1. I really like it, and think it can do everything I wanted. There is one thing that is puzzling my mind, however. I created a hypothetical situation to explain this: I have a page named "projects" with a template with the same name that i don't want the user to edit, or move, but i want him to be able to create children for it (using the template "project") and to be able to edit and sort them. The problem is that the user is able to move the pages to another parent, but not move them among siblings (because i'm not allowing him to edit "projects" itself). I don't know how this could be solved... maybe by being able to choose, not only wich roles, but also wich permissions for each role on any template... i don't know, maybe it would add to much complexity... There's also a weird thing happening. Although i don't allow creating new children for the template "project", it's possible to create them by dragging the pages there (like on the screenshot). This is not the intended behavior, is it? I'm also working on the debugging tool, and i think it can be very useful. Maybe I will be able to make an extension for it

Thanks for the kind answer Ryan! I will try your suggestions.

I guess i didn't explain very well my point i think because of my inexperience with designing websites and using cms's in particular. Apeisa, for what i've seen we really can't compare drupal and Symphony in terms of simplicity and control. In Symphony you never have to think how you can remove something, you always have to think how to had it instead. It's core it's also very small and only few extensions are active by default. This is why I think we can compare it with Processwire although they are so different in other things. I won't try to explain how Symphony works because I will be unsuccessful again for sure. But maybe I can tease you both to study it a bit, and discover how it has some really nice things that could give ideas to make Processwire even better. Ryan, maybe you got it right about the forms, although I was not talking only about them. One of my concerns is how the editor will interact with the back end... and, while the tree view is perfect for building the website, I think it would be nice to be able to organize the the content for the editor. I mean, some people could see everything, others only some pages, while others would land directly on the new blog post page (like in textpattern, for instance). Since I also referenced the debug tool in Symphony, I was also thinking how Processwire could have something similar (an idea for a module maybe). In symphony, if you add '?debug' at the end of any URL it shows you all the XML data that you can access from that page, and it let's you try XPATH expressions highlighting the nodes that you reach with them. I can imagine that in Processwire we could have all the results of each field shown, and an imput field where we could write some variables and have the generated results. Hm... this discussion went quite far away from the Breadcrumbs subject. Sorry for that.

It's not the first time i read about symphony on processwire forums, and thought i could tell something about it. I was trying symphony before i discovered processwire, and besides the obvious differences (starting by xslt/php templating systems), both have one important thing in common, they give you complete responsibility for the markup and great flexibility on constructing your website. For me, the problems with symphony is that the xslt can get quite complex (although i love how the xml data is thrown at the pages, and how you can check and easily get any node with their debugging tool http://symphony-cms.com/learn/concepts/view/devkits/), and i wonder if it make sense to output in pure xml when using html5 (there are big discussions on symphony forums only on how to output the doctype). Where i think symphony beats processwire is on the flexibility it gives the developer/designer, not only on building the markup and the front end structure, but also on building the backend structure, allowing him to build the forms independently from the pages, and presenting them to, or hiding from, the client/writer with the structure and organization he wishes. This flexibility is achieved basically like this: sections(fields) >> datasources(xml) >> pages(xslt) (http://symphony-cms.com/workspace/assets/learn/visual-overview-1258682736.png). I think this is very powerful, and maybe i'm wrong when i assume processwire doesn't achieve this kind of flexibility on the back end. It will be perfect when it does

I will be glad

I was playing with tumblr API inside processwire and I think it integrates quite well. Using simplexml you can have complete control of the markup (ok, not complete...) and, for what i've seen, even a complete separation of kind of posts, tags, etc. You can also make your tumblr blog private, so it will only be visible inside the site (hm... i have to confirm if this is really true). I think it wouldn't even be difficult to pull the data to your databaseif you want to keep it. So, If you don't mind putting your data on a server you don't control, i think it can be a neat solution http://www.tumblr.com/docs/en/api http://finlay.tumblr.com/post/529010691/embed-tumblr-into-your-website (if you copy the code from here you should replace the quotation marks) I'm only a graphic designer adventuring on learning webdesign and programming. Please correct me if i'm saying everything wrong here

HI all! I found Processwire very recently, and I really like the concept behind it. I'm from Portugal and would like to help with the Portuguese translation. I agree that it would be much easier and friendly if we have complete sentences. The Portuguese language also raises some issues, but taking the example from Marcin I can see it might be less complicated than Polish A página foi criada -> Page was created A página não pôde ser salva -> Page cannot be saved Foram salvas duas páginas -> Two pages were saved Foram salvas cinco páginas -> Five pages were saved One major issue (but of a different kind) that comes to my mind is if there should be separated translations to European Portuguese and Brazilian Portuguese.