apeisa

Where is that code? Template or module?

I get shivers when I hear Monkey Island tune. That is epic 😊

Looks and works great, thanks @Pete!

Great to see pull requests merged. This will help community and pw greatly!

Not exactly what you are looking for, but similar solution (to a certain level) can be achieved by using a repeater field which then has title ("folder name") and files -fields.

Same here. This is probably windows specific problem - at least in our company it is.

Just my 2 cents: it should throw an exception here - this current logic is not good in my opinion.

Great additions - many of these are things that we have setup our own solutions when hitting performance issues on large scale (10 000+ pages with lots of fields) so it is great to see core supporting this kind of things. Thank you Ryan! Quick note on findRaw - it looks like it doesn't support parent? It would be very powerful to be using parent just like any normal field based page relation.

Yes, thumbs up from here also to focus on bard/editorjs level of "content blocks" instead of full layout editor.

I actually do like the functions api, although using it in one project only. But it doesn't help with selectors, which is where I type most of my tempaltes...

I think this is probably because in Finnish it is pretty rare to see L after P - I think probably only in words that come directly from foreign languages, like application => applikaatio etc. Very frustrating, maybe we should have a module that adds tempalte as an alias for template... 😉

After 9 years using ProcessWire I still do multiple times a day a typo writing template as tempalte (probably write it wrong more often than right). I know few of my co-workers does the same. Is this curse for us Finnish people, or is tempalte thing in other parts of the world also?

It was Kongondo doing maintenance release to old one. But I know Kongondo is working hard to get v2 released.

Yes, I think you are probably right with both of your reasons. I did try to make pagelist work with pagination (it does, but couldn't get limit to be set dynamically, so it follows whatever is set on pagelist module which defaults to 50). It seems that I wont need pagination at all on dashboard (more proof for your point 1), but if the need arises I will definitely take a closer look into it.

Unfortunately I believe there is no best practice and very little tools and helpers regarding testing. I have some experience with Laravel and there testing is first class citizen and is very easy to get started. I think @teppo has done some testing with few of his modules if I remember correctly?