apeisa

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

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.c...ges-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/.

OK, thanks for the clarification. So it is correct to say that Title is a custom field type and Name is a system field type?

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.

$allArticles = $pages->find("template=article|image|video|audio|quote, sort-=created, limit=20");

foreach($allArticles as $article) {
  echo $article->render();
}

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...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).

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.

I have new version coming that introduces ability to create new pages. I would be extremely happy to get some feedback about the methods and arguments I am planning. Currently it works like this:

$fredi->newPage("templatename", "title|summary|body");

or

$fredi->newPage("templatename", "title|summary|body", $parentPage);

That would open new modal with title, summary and body fields. By default it creates new pages under the current page, but you can define alternative parent page there also.

I have also created ability to set fieldWidths, just add =XX to fieldname and it gives the width. Those can be used both in edit and new page modals. Like this:

$fredi->render("title|author=50|summary=50")

I want to take this further: defining required fields and also for new pages prevalues and possible hidden fields. This means that simple string based fields definition doesn't fly that far, or it needs some super nice syntax. Ideas?

This gives all you need: http://mqtest.io/ (also build be real superhero - Viljami)

Ah, I finally found it. This is why custom selector stuff fails on FrediProcess: https://github.com/r...age.module#L141

I think cleanest option would be if getSelectablePages() method would be hookable. Any hopes to get three underscores there Ryan?

You might have to change the root on your config file. But that's it.

Nope. There isn't any setting like that. PW doesn't "know" where it is run or not. It can even run at both domains at the same time (granted they are on same server like horst mentioned).

There is also handy Process modules, that admin uses. See this as a starting point when building your own: https://github.com/r...gn/ProcessHello