apeisa

Clever solution Nico!

Oh boy! That is so somantic.

Ah, sorry. I was a bit unclear. We have translated the "name" in Finnish: "Sivun nimi selaimen osoitepalkissa", which means "page name in browser's address bar". Our client's found "name" a bit unclear (what does it mean? Where it is used?). That translation then of course doesn't make any sense in user context. Our first option was to fallback to "name", but that didn't make full sense in user context either, since first two fields in user template (in our default setup) are "Firstname", and "Lastname". So it has been little unclear for clients "Name, Firstname and Lastname", it would be more clear to have "Username, Firstname and Lastname". PW uses "username" on login form (http://processwire.com/skyscrapers/admin/), but "name" on when editing/adding users. Convention with API usage doesn't matter, since it doesn't match with Finnish in any case. This is definitely detail and will think about hooking (I need to support multiple languages, so it little bit more difficult).

This is the latest incarnation of CustomPageRoles (view & edit access per page): https://github.com/apeisa/CustomPageRoles/blob/master/CustomPageRoles.module Not totally happy with it yet, so that is the reason it's not in modules dir.

Arjen, happy to know if you find anything.

Since users are also pages, they use name field as their username. I would really like to have something like "Username" instead of just "Name" there. Also when editing page settings I would like to have "Page name in address bar" instead of just "Name". There seems to already be some kind of tweaks with name field (it doesn't show the path when editing user), so this might already be possible. I just couldn't find anything.

Why does it need another layout, if you want to personalize the download? While I would prefer having same layout used across all the regional sites, I don't have anything against custom designs (I think in this point it is great to have more any kind of localized content about PW). I just don't understand the reasoning

Yes, there has been very strong growth recently. Monthly visits in April: 2011: 5 112 2012: 12 448 2013: 48 455 Most popular countries this year: 1. United States 2. Germany 3. United Kingdom 4. Netherlands 5. India 6. Finland 7. Switzerland 8. Canada 9. France 10. Italy

If you have datefield called date, then yes, looks good to me. Why not try and see how it works? (never used wireRelativeTimeStr myself)

No, it means this is already supported on global scope in PW: wireRelativeTimeStr($timestamp); So try this in your template file to get started: echo "This page was created " . wireRelativeTimeStr($page->created);

I guess the pain point for most is that while they are editing text and need for image occur, they click "Image" button on editor (tiny or ckeditor). Then there is no way to upload images in that view. Also that view could have nice little image grid instead of full size photos (this: http://processwire.com/talk/topic/635-thumbnails-of-images-in-tinymce/). Overall I think PW has nailed images & text pretty nicely and in a flexible way. The more you mix the two (images and text), the more mess you have in any scenario (harder to reuse the content on different contexts etc). I try to make nice default image placements (with few variants if needed) and really having to use RTE image placement should be the last resort. For some sites, of course that is impossible or inconvenient.

Well, managed VPS is one option. There you can ask hosting company to configure the server for you. Servint (their vps: http://www.servint.net/vps.php) seems to be great choice and also what Ryan & ProcessWire recommends: http://processwire.com/servint/.

Why not $albums and $album->songs?

Ah, sorry I read your message in hurry. I guess it's a bug with earlier webkit then. I'll take a look at it.

Try updating the chrome. It was a bug with chrome version 25 and below I believe.

That is how I would say it. Title is kind of "special" custom field, since it enabled by default for all templates. I have never removed it, even if it has been unnecessary few times. I love the fact that I always have $page->title which would give me something readable in every case.

To avoid any duplication kongondo is talking: In latest versions (not sure if in stable yet), you can do this: $allArticles = $pages->find("template=article|image|video|audio|quote, sort-=created, limit=20"); foreach($allArticles as $article) { $templateFile = $article->template . "-teaser.php"; echo $article->render($templateFile); // It renders the content with article-teaser.php, image-teaser.php etc... } There is of course multiple ways of doing that (I rarely output any markup in templates directly), but I think that would be nice way of doing simple tubmlr-style blog.

Sinmok, this looks very cool, gotta test this soon! Nice comparison with Fredi too

$allArticles = $pages->find("template=article|image|video|audio|quote, sort-=created, limit=20"); foreach($allArticles as $article) { echo $article->render(); }

Full featured forum software is a lot of work. Maybe full integration with http://fluxbb.org/ ? And to answer Pete's question: not very interested in IP.Board integration (full featured forums like IPB have proven to be too much for our clients), but with some simpler forum software I would definitely be interested.

I am using it on one site, but would love to polish it a little bit. Try and give some feedback, I am happy to hear how it goes.

Ok, changing the code to this makes it work in 5.3 also: $this->addHookBefore('InputfieldPage::findPagesCode', function($event) { $page = wire('pages')->get(wire('input')->get("id")); $event->arguments(0, $page); }); It seems $this was removed from closures at some point (https://wiki.php.net/rfc/closures/removal-of-this) but introduced again (since it works in 5.4).

Thanks for the update Rasmus. Eagerly waiting and definitely paying (if you think about making it commercial).

I am testing these Anonymous functions and it seems to work on my php 5.4.6 installation, but giving error on 5.3.10. This is what I receive when trying simple hook init with anonymous function: Error: Using $this when not in object context This is the code that is generating the error: $this->addHookBefore('InputfieldPage::findPagesCode', function($event) { $page = $this->pages->get($this->input->get("id")); $event->arguments(0, $page); }); // Yes, findPageCode is not hookable yet, but I have made local modification to it These two installations are on two different servers, so it might be something else than PHP version.

Not sure about next few days, but in week or two at least. Want to test it more here. But so far - it seems to provide super nice editing interface.