diogo

hm... it's not needed

In arabic, shouldn't the sentences be on the right?

You also can put those setting on another tab. But I agree that it's good to have these kind of options when designing the edit page.

Thanks for the reference Ryan! I hope soon I will be able to contribute with modules, instead of ideas only...

Hi 97s! Welcome to PW Fields and such are on the database, while the other things you mentioned are files. You can install PW locally, and then export your database and copy all the files to server without forgetting the .htaccess. All you have to do is check your permissions again, and change the database info on the config.php file. At least this is what I did until now. You can also use the ProfileExporter module. But I never used it for this.

says the floating head

Yep, that simple

If you don't want to wait for the repeatable fields, here is a completely different idea. create 10 different fields (or whatever number you think will be the maximum you will use) and create a template with all of them. Put the letters A, B, C, or D on the first line of each texarea and the content from the 2nd line on. Now, with PHP, explode each field string on the first /n and assign the letter to the div class. With repeatable fields you don't have to create 10 fields and clutter your edit page edit: or even using explode()

there's a lesson to be taken from this

Great apeisa! I wouldn't know how to do it

For using the admin template you would have to create a process module, and then choose it from the select process field. Maybe it would easier to build the settings form as you where planning. But it would be very nice to have a module that simply places an admin link to a specific page edit, wouldn't it?

I tend not to like the idea of having too many profiles or templates as a product becomes more and more popular (and I think PW will), it makes people not able to distinguish between what well done and very badly done. Same thing goes for plugins. That's why a very well done community driven profile would be a good start. Something that could be proudly presented in the homepage as an example of what can be achieved with PW, and at the same time, something that would call the attention of a different kind of users. I also think we shouldn't be in the middle with this. If PW is directed at Designers/Developers, than this profile could be directed at those that wouldn't even touch the template files.

This is great Ryan! I'm dying to test it

You're right. What you are describing is a profile. I was also thinking that it would be nice if there was some profiles to share in PW website. But even better would be to create a PW community driven profile, maybe a blog, or a tumbleblog with everything that could make it very simple to use and really great (posting by email or bookmarklet, user being able to change background color, image header, logo, text typeface, simple widgets, etc etc etc). Would be great publicity for PW, and encourage non developers to also try it.

Andrew, I also thought of that. But since you would have to program your template to deal with them anyway, I don't think it would be any easier to use a system of that kind instead of this one.

Great work Ryan! This will make it so much more intuitive for editors in some situations! And I also think it will bring more people to PW, as it was obviously one of the most requested features.

If not, it can be called like this: $gp = $pages->get(5766); $gc = $pages->find("parent=$gp->children"); foreach($gc as $a) { echo $a->title; etc... }

Can't this temporary P21 be a copy of P22 with the README explaining?

Oh, sorry for the typo and errors... next time I will be sure I'm awaken when I post edit: ok, now I understand why children->children could never work. But I think in some situations it can be useful to target pages like @wmushtaq asked. Maybe a parameter like this "deep=2" passed to children(), or even a method descendants() with this same parameter...

this didn't work for me $grandchildren = $page->children->children; neither did this, or any other variations of this kind: $grandchildren = $page->children()->children(); what worked for me was this: $gp = $pages->get(5766); $children = $gp->children; foreach($children as $child){ // there was a ")" missing $gchildren=$child->children; // corrected from $children to $child foreach($gchildren as $gchild) echo $gchild->title; } you can also give all of the videos the same template and call them simply like this: $pages->find("template=video") // corrected from get() to find() after soma's reply or if you need the videos to have different templates: $pages->find("template=video1|video2|video3") // also corrected from get() to find() edit: Ryan, I also assumed parent->parent children->children would work. Why doesn't it? I'm sure there is a very interesting explanation involving methods and classes and lots of oop stuff

Or, when giving permission on page, PW could check the permission on template and tell that for doing this you also have to give permission on template and ask if you want to do it now... then you can have the usual check (...if you do this the pages: blabla, blabla and blabla will also inherit this permission... are you sure you want to?)

This is also where I have more problems with processwire. I think I gave permission to editors to edit or view a page, but I didn't...

Ha!! Didn't know that one The module is not active by default. And there is also a Newlines to Unordered List handy! edit: why aren't they active by default?

you can use Markdown or Textile: http://processwire.c...text-formatter/ or, if the only thing you want is the <br> where there is a new line; you can use "nl2br" on a regular text area: http://php.net/manua...ction.nl2br.php <?php echo nl2br($page->field); ?>

Sorry, i did some mistake copying the link above. here is the correct: http://processwire.c...page-fieldtype/ And I was talking about this topic: http://processwire.c...__fromsearch__1