Leaderboard

The answer to this may help others, I hope. It is not ProcessWire (I didn't think it was but I was hopeful someone else might have had some related knowledge that might have helped hence bothering you guys here). I had already spoken to the hoster in this case to work out which php.ini file was to be edited. The answer is interesting and easy: as I was running a website with FastCGI the php.ini file just above the httpdocs location was the one to edit, not the overall one often found in /etc/php.ini. All good, I edited it. But the problem remained. So a call to (mt), the hosters for this site, and they quickly found and fixed a one-time file that stops FastCGI working with files greater than 128KB. They upped the limit for this file to 1GB and so now this site and any others that use FastCGI will practically be controlled by the settings in their php.ini files. Result: all is working beautifully I hope this is helpful to someone else and thanks again PW people for this superb product. Cheers, -Alan

Inline Editing. What fun that is. Adobe took their standalone inContext editor ( an inline) and added it to their Business Catalyst hosted offering. Developers can add attributes to the code (a div with a proprietary tag) that would be recognized by the inContext editor, to restrict the features of that editors use of it. That can certainly help to control the mayhem. But there is lots of that with inline. Plus I hate to see proprietary elements added to html but you usually do need someway to control the users editing scope. For the most part, my experience with end users has been that they need a simple structured way to submit content types that followed repeatable patterns while having some latitude within the "textarea" to add media elements and such. A focused backend serves that purpose. So I don't pine for it as a feature in a CMS. What I do like is the ability to control the presentation of the data entry process. PW has those features with the exemption of required data entry on fields (or am I missing that?). +1 for the repeatable fields. In summary aside from the "wow factor" I feel inline editing is overrated and when available, underutilized. Besides in a few years 60+% of users will be mobile or tablets anyway. Apps rule that space today and will in the future. That means more structure. We will have to create our interfaces to serve the users on the tools they will be using not the ones we do. I am not planning on giving up my keyboard. In fact you can pry my keyboard from my cold dead hands. Or maybe my keyboard will be the surface of the desk while a kinetic or similar device is reading my finger movements in 3D. Ahh what a wonderful time to be an interface / app developer!

echo "<ul>"; foreach($pages->get("/students/")->children) as $gender) { echo "<li><a href='{$gender->url}'>{$gender->title}</a><ul>"; // Male or Female foreach($gender->children as $student) { echo "<li><a href='{$student->url}'>{$student->title}</a></li>"; // Peter, Anna, etc. } echo "</ul></li>"; } echo "</ul>";

You want all of them? Male and female? You could put another foreach inside the one you have, but would be more practical to give those pages the same template and call them by it: $pages->find("template=people")

I still didn't comment on this site, but I must say, I love the "Philosophie" part

Thanks for the credit Soma! The Omnia is my favorite ProcessWire site. Beautiful hotel too. My Dad apparently knows of this hotel, it must be internationally famous. I stepped through the reservation process the other day, and there is a lot of quality and attention to detail everywhere.