apeisa

Ryan writes documentation based on demand. Currently basics that most people need are covered very well, but some more advanced topics are missing "official" documentation. Lot's of information is here on forums (it is a bit searching - or what we try to encourage - asking), but the official stuff is coming. But after the basics - as you mentioned too - I think the great thing is that source code is very easy to follow and mostly very well commented. Good example is the addHook() method which has nice example here: /site/modules/Helloworld.module (which is referenced from here: http://processwire.com/api/modules/).

This is great, very welcome addition!

Actually I think there is very little overhead of doing that, since PW doesn't load the data until it is used (or if you have autojoin set on your fields). And if you don't have to loop all those pages it will be breeze. You can also do this: $pages->find(selector, limit=2)->getTotal() But I guess it does pretty much the same under the hood (not sure though) - removes the limit and counts it.

Yes sir!

Does anyone know how jQuery UI datepicker can be configured to use other languages than English? There ain't no language code selection like there is in TinyMCE field yet, so not sure if that is possible yet. BTW: That solution that TinyMCE has is perfect for us, since we only need to support Finnish in backend. But people who need multiple Admin languages do have a need to match Inputfield language with the language preference the current user has. Not sure what would be best way to approach that. Just ignore that, I don't make any sense. Since that setting is set on lang editing interface, it is always lang specific setting, not global.

Yep, the API supports sorting with multiple values, but the admin UI doesn't (at least yet).

Hmm.. looking at the API I guess both should work. Other possible failures: You are on last sibling, so next will return a nullpage => therefore no images Your images are configured to have only 1 image, so first() is already assumed

On mobile, but shouldn't there be next() with those parenthesis?

Rob, very interesting. I found one of the best parts of PW is that it has strong relation to websites, ie. each page has an unique url (wheter you need it or not), nice caching, good ua control etc. So I find almost everything pw gives granted very useful and like to keep those features. But I also love the bootstrapping and using API just as a data storage, it is very flexible. I found your approach pretty radical (building whole site as bootstrapping), but very interesting and want to try it too (please do share more information, if possible). PW definitely doesn't get into your way in that method, but you get great API and admin site for free. Nice! PS: Have to say that Twig actually looks pretty interesting.

maxWidth & maxHeight would be great!

Not sure if that is easily possible.

Yep, definitely nice one to build with PW. As slkwrm said the most work will be on user profiles. It would be breeze to just extend the user template and allow "employee" -users to edit their profiles. There is ready functionality for that also - but since you especially don't want to use PW admin looks for that you are left to two options: a) Use admin and profile editing there and create new admin theme to fit your design b) Create "front-end" editing capabilities for user profiles. I guess b is much more work, since admin themes are pretty easy and fast to do.

Nice work Marty! You are on the roll - I guess you have soon more PW sites under the belt than Ryan has

I haven't used Silverstripe, but heard some good things. I have always found it little bit "overhelming", though the new UI seems to make it much cleaner experience. About Kirby: there is admin panel available: http://getkirby.com/docs/panel Using files only has some advantages too (mainly very easy versioning with git/snv etc). I wouldn't consider Kirby with anything too huge, but I see that as an interesting and refreshing alternative - taking the "simplicity" to extreme (even compared to PW). I don't think so. Both mimick the jQuery API to CMS field and use PHP, that is where the similarities come. Also both have settled to use $page and $pages variables, which make them seem even more similar (both I think $page is only logical variable name there.. $node..? $entry..? no no). And since Kirby's roots are in year 2009 (http://web.appstorm.net/general/interviews/interview-meet-bastian-allgeier-the-developer-behind-kirby-and-zootool/) and open source PW 2 came out December 2010 (I think?) I don't think they have drawn much (if any) inspiration from others. Cannot say for sure though.

I was thinking this at one point, but the project was cancelled so I didn't get into implementation part. It had the special need, that the recurring event need to be it's own entity (it might be same event, but different time - but also it might be in different place, have different price etc). How I started to approach the problem was to have "events-item" template which could have children with template "events-instance". Events instances would inherit most of the data from their parent event, but could override some parts of it. And how I would have implemented is that when saving the "event-item" you could make some selections "Repeat once a week, until <date>" and that would create the required amount of instances as children. Pretty simple actually that way.

Silverstripe (http://www.silverstripe.com/) might be interesting for you. And on the other end (something much simpler) is Kirby, which is no-db cms: http://getkirby.com/. It should be pretty easy to get started, since it also has jQuery inspired API: http://getkirby.com/...ent/home/03.jpg Haven't really tried either of those, but I have heard good things about both.

Usually simple honeypot is enough (put a inputfield quite a top of your form, hide it with css and if that inputfield has any content, then show error and don't allow the form). PW comments module has something similar, search for requireSecurityField on this page: http://processwire.c...types/comments/

Mats: nice site! Very well designed and works fast and rock solid. I noticed that your midsummer link was little wrong though, here is the right link: http://en.wikipedia.org/wiki/Midsummer#Finland Happy midsummer too

Also I know many solo developers like paid dropbox and it's unlimited versions.

Thanks to stillmovingdesign (http://stillmovingdesign.com.au/) for sponsoring it.

Thanks Guys. Interrobang: tested and worked nicely - thanks for the tip, I just committed it. Great improvement. Teppo: I think there should be cleaner way to see if field is repeater. Probably by getting the actual field an checking it's fieldtype. But this is great news to know the solution for this problem. Will look into this soon (before holidays I hope).

This came up by quick googling: Error code 28: No space left on device

Export and import is enough, no problems there. Only things you need to take care are file permissions and that you have same password hash in your site/config.php file.

I am sure many people find that interesting. Maybe you should share the code in Github so others can see and contribute to it?

See this: https://github.com/ryancramerdesign/ProcessWire/blob/master/htaccess.txt#L71 So it might be as easy fix as editing and uncommenting one line on .htaccess file. Cannot really help you with other questions. Cache problem is probable easily solvable. but I don't know anything about twig so cannot help you there. Great that you got it working!