apeisa

This looks even better. Import doesn't seem to work on my test site though, seems to some incompatibility with multilang features. This comes after using paste import: Catchable fatal error: Object of class stdClass could not be converted to string in /srv/www/pw/frontendedit/wire/modules/LanguageSupport/FieldtypeTextLanguage.module on line 38 I am running PW 2.3.0 on that site.

Horst, no worries. Just merged the new pull request and now it remembers the cropping. Superb! Thanks fellas!

Well... those aren't actually too helpful. This page still tells about old "page based ua" instead of current template based.

Tree is where you put your pages. But it is very simple to create ProcessModule (custom admin page), that lists your news in table/grid and allows adding new ones.

Unfortunately there ain't API for that. Should be possible with PHP though. Anyone done cleaning script for that?

I have just tested and merged pull request from horst and owzim that adds support for PageImageManipulator in thumbnails cropping view. This is great addition! If you don't have PIM installed, it will work just as usual, so updating should be safe. If you do use PIM, make sure you are running latest version, since earlier throws error when using cropping tool. Thanks for your work on this horst and owzim! PS: It maintains the settings and also coordinates, but coordinates aren't active when re-cropping. It shows preview of different part of image, but when proceeding still (rightly) crops the old part. Probably the cropping tool JS needs some refresh...?

Totally missed those dependent selects on first watch. Amazing stuff, thanks Ryan!

owzim: one thing you might want to mention. We (www.avoine.fi) are company with around 2.5 - 3 million euros revenue for this year. Good part of that (all client websites and -services) comes from ProcessWire. We have also build lots of new software using ProcessWire. Fully dedicated to this platform in many ways: 5 developers working with ProcessWire, sponsoring the core development and also contributing to the core and releasing open source modules. And I see "strong leader" model as a strength for ProcessWire development. Software development is not road building: you don't do it faster nor better by throwing more people to the mix. It of course requires that we have great leader, and that we certainly do have!

http://communities-dominate.blogs.com/brands/2013/09/the-full-story-of-nokia-and-microsoft-how-we-got-here-and-why-microsoft-will-fail-with-nokia-handset.html (it's long, but few first chapters are good review of what happened). Elop probably has a record as most unsuccessful CEO all time. Of course it is all "what if" discussions now. But CEO saying "symbian is dead" when Symbian is most popular smartphone OS in world by far and NOT even offering alternative OS in 9 months is pretty much suicide. And that is exactly what Elop did. I wasn't fan of Symbian, but it had very strong position in companies (kind of BlackBerry for rest of the world). I remember talking to our CIO on the "burning platform" day, he said that he just cancelled few phone orders and starts really looking for android and iPhone for business... And next Open Source OS (maemo / meego whatever) was just around the corner (Nokia released Meego phone before Windows Phone phones...). Meego phone (N9) got nice reception, but Elop finished it by saying: No matter how well it sells, it is just "test bed for new technology" and we will not release more Meego phones. Well, now Nokia should just buy Jolla (it's a startup where many ex-nokians are building phones / os) and should release their first phone this Christmas.

Very interesting! Does it create the fields also when importing (those are defined in JSON, so that made me assume)? I would also think about JSON schema - should metadata and content data be in their own containers? Something like "meta" and "data"?

If you access the page directly, then it will give 200 OK as a header: http://processwire.com/http404/ When accessing url that actually doesn't exist, like http://processwire.com/fasdfkw/ you get 404.

I like it much better without boxes. Thin borders look great! That boxes inside boxes inside boxes effects is very heavy when you have repeater that has an image field for example. I really like this. Still not a fan of red/pink labels. Setup view looks wonderful!

Philipp, looks great. Can you show how fields looks without that thin border/shadow and maybe with black/grey labels? I think we should aim for "less borders / boxes" feel. I really like your iteration, very clean looking!

Always visible page tree has it's merits. But I also find it little overwhelming. When I evaluated different CMS products few years back I did found Silverstripe interesting, but remember that "always visible pagetree" was little messy. PW way is much more "zen" This is how it looks now:

Kongondo, I don't think that is wise optimization to make. Although trash page id is not likely to change (at least on site on production, but might be different between site profiles etc), there is no real speed gains and doing that way you should at least comment what id=7 is.

Now that I think of it, it's clear why the first approach didn't worked: pw is already in outputting content when we changed the template protocol - it is too late for PW to do the redirect. With right hook and autoload module that approach might work. .htaccess is probably very simple in this case and little bit faster than this approach.

Well, if that template protocol/https setting doesn't work when changed runtime, you can always do the redirect too. Something like this: <?php if ( ! $config->https) { $httpsUrl = str_replace("http", "https", $page->httpUrl); $session->redirect($httpsUrl); }

This? $page->template->protocol = 1

Easiest way: uncomment this line: https://github.com/ryancramerdesign/ProcessWire/blob/master/site-default/config.php#L58 and add _init.php file to your templates folder. Add the code snippet there.

How about this approach (not 100% sure if it works, but worth trying): <?php if ($page->rootParent->url == "/members/") { $page->template->https = 1; } Add that into prependTemplateFile (if you use that) or into autoload module.

That is exactly the thing I am doing with Trashman: https://github.com/apeisa/Trashman/blob/master/ProcessTrashman.module#L124 I understand both "sides" of the discussion - both opinions are valid so it is matter of having one way and stick with it

Just checked: 119 870 is the magic number today

Nice work Adrian. I would definitely add formatted option too. Btw: is that how you you format phone numbers in US? Here phone numbers look like this +358 4143 8399 1 (not sure about spaces). Maybe allow few runtime options for different localizations?

This is amazing stuff Ryan! Working very well, definitely even more robust than I even imagined! I love the implementation with data attributes too.

My fieldset behave perfect, hiding with selectfieldvalue=something. I really like that you can just say "required" for all the fields inside fieldset, and if the fieldset is hidden, then those fields inside that aren't required. Logical and powerful.