evan

Another question -- Is there a way to make a page editable but not deletable, on a page-by-page basis? I would like my client to be able to add children, edit the parent, but not delete the parent. Thanks!

That's basically what I was thinking, yes. Thanks!

Hi all, Is any kind of formatting possible in the field description? Linebreaks would make it more readable for lengthier descriptions about how information should be entered. Thanks! -evan

Great, glad to know I'm on the right track! I see some nice organizational possibilities using associative arrays or classes/objects to store markup. Thanks for the responses, I'm stoked to implement a site with PW now.

I should probably clarify that I'm interested in methods to abstract these elements outside of the templates, so I can reuse them. Perhaps I'm overthinking it...do people just do something like this? blog_entry.inc: function blog_entry_markup ($x) { echo "<strong>$x->title</strong><br />$x->body"; } blog_template.php: include('blog_entry.inc'); foreach ($page->children as $child) { blog_entry_markup ($child); }

Hi all, I just discovered Processwire and am very intrigued as a current Textpattern user, and seeing the similarities and new possibilities. Quick question -- how do you all manage your repeatable page elements that contain Processwire variables (called forms in TXP)? By "repeatable page elements" I mean formatted content like blog entries, calendar events, etc. within a greater page layout. I realize this is outside the scope of Processwire itself, and more on the personal workflow side, but I'm curious to see what methods people use before I start building. Do you store them in a PHP include as variables? Functions? A combination of both? I'd like to hear how people typically approach this, and why. Thanks! -evan