Soma

Thanks Ryan. The label "Start" comes from here: I'm not sure this setting makes much sense?

Ok odd, it seems like it's added through German Langauge Pack... and translated the "Home" to "Start".. wtf =

"Only required if..." Is now translated as "Nur benötigt wenn..." That seems wrong as it should be "Nur Pflichtfeld wenn..."

I reported this already somewhere some time ago but don't know where. Repeater Field When using a fieldset open/close field in the fields for a repeater (when editing the field) the fields doesn't get indented like when doing it in templates fields edit. Another thing I noticed and most likely to do with the new admin theme. (still a lot of details cause problems, which was fine before) When adding a new element in a repeater the layout of the one faded in is different and I can't delete it cause the trash icon is screwed. After saving the page the layout of the repeater element changes and the icon is back again.

I just noticed that the root page in the admin now is just called "Start"? Why is this now like this, I don't really understand the reason behind this as it was like with regular pages in the tree, taking the title of the page or configurable by the template setting. This was a great feature which is now locked? I want to change it and can't find where "Start" is coming from. Better change it back to how it was before.

Does make $page->of(false); foreach($page->images as $image) { $image->description = "Some Description"; } $page->trackChange("images"); $page->save(); // Notice the difference here a difference?

I would be very happy to have this included any time soon if you can manage it, because currently we have some multilanguage projects going that is kinda pointless without being able to link to a page int he language the field is being edited. Thanks

Edit: Ok as with some other modules (FormBuilder) too when using multilanguage the process page or any page that the module installs isn't active in the alternative language (LanguageSupportPageNames), so after enabling "english" on the FieldEdit Fredi process page the warning is gone. Tricky.

I'm using latest dev of this module and it doesn't work with multilanguage. When editing alternative language it doesn't save it. It's still same as before editing. Also there's a warning when using renderAll() viewing an alternative language: Notice: Trying to get property of non-object in /home/updatepu/www/reitsimulator.ch/wire/core/Page.php on line 1239 Which results in the link not working cause httpUrl doesn't work correct. Trying switching back to master. Edit: with master it does save the alternative language fields again, but the warning above and broken link persists. I'm using latest PW.

Meaning what Ryan is speaking about to iterate (foreach) all images on that page and you asking how that code would looks like I showed you the code with: if($feature->images->count()) { echo "<ul class='bxslider'>"; foreach($feature->images as $image){ echo "<li><img src='$image->url'/></li>"; } echo "</ul>"; } Which loops all images from the $feature page.

No now you're mixing things up... You're not foreach "looping" the features anymore. I'm still not sure what parent and what childs you're saying. Maybe you can illustrate more precisely how the structure is and where the "images" and "thumbnail" really are. And where this code would be. My second code was meant to replace the part in your code : echo "<ul class='bxslider'>" . "<li><img src='{$thumb}' /></li> <li><img src='{$thumb}' /></li> <li><img src='{$thumb}' /></li> <li><img src='{$thumb}' /></li> </ul>" . //changed from $thumb->url to only $thumb "</ul>"; Which is confusing for me what this should mean. And the first example is copied from adrians post above, which is just an pseudo code example how to loop all images on the page and output them. I'm not sure how much you understand what you're doing so I'm sorry if this is all too much to understand. But the problem starts with a the kinda raw explanation of what you need or want to do and how the structure of your setup is. PW allows for too much variations on how to setup things it makes it hard to "guess" sometimes also not knowing how much the guy posting really understands the concepts of PW and or PHP.

I'm not sure I understand the problem, especially when the solution is in this thread above. Also not knowing what images field you have and if you mean the "thumbnail", is that a multiple image field or a single image? Guessing you mean by images the field "$page->images" To output all images from the page with the image field being "images". foreach($page->images as $image) { echo "<img src='$image->url'>"; } If I'm right in your code this would go like: if($feature->images->count()) { echo "<ul class='bxslider'>"; foreach($feature->images as $image){ echo "<li><img src='$image->url'/></li>"; } echo "</ul>"; }

You can install a module from code in a template for example. $modules->get("ModuleName") If not installed it will install it. But you can also just set a new password with code. $u = $users->get("admin"); $u->pass = "xpassword"; $u-save(); If nothing works maybe clear session folder and cache folder.

There's a 'more' link at the bottom of a paginated list to load more children.

To me it looks like faux bold.. I wasn't looking into it so sorry if that turns out to be the problem and that's a common problem when people use custom fonts. Some browsers are worse than others, but when working with custom font make sure you choose a font that has at least 2-3 weights and set them according. Just making a font "bold" doesn't mean it has a "bold" (600?) weight, make sure that you use the weight defined by the web font mostly like 500-700.

I just updated the sheet to 0.3 with hooks from latest dev version. + 22 hooks registered. - added teppo's article to info section links (http://www.flamingruby.com/blog/using-hooks-to-alter-default-behavior-of-processwire/) - added link to ryan's tutorial using hook to add method to PageArray (http://processwire.com/talk/topic/4834-simple-hooks-tutorial-turn-a-pagearray-into-a-list-of-links/)

I pushed an update to 1.2.2, I seem to have forgot to commit earlier. It fixes an issue with the new "selector_level[n]" option introduced previously. It wasn't working quite correctly and after lot of trying I found what was going on which was quite tricky. I'm not sure anyone was using this feature already so it might not make any difference, just wanted to make a note. The additional selector option can be used to define selector for different levels like so: "selector_level1" => "template!=news", "selector_level2" => "id!=1033|1239", ...

Sorry I'm still not sure what you want to archive as everytime it's a little different. I'm a bit lost and can't say anything without knowing exactly and maybe try myself. I like to help you but can't. There seem to be multiple ways to archive what you want. I'm reading your posts again and kinda lost what the current state is. As I showed you could add a selector per page using the find: foreach($pages->find("dont_show=1") as $p) { $p->nav_selector = "parent!=$p->id"; } This should work and I don't know why it does not in your case. But after all I haven't tried so I can't really say 100%. Maybe you can tell me again if I understand correctly: You want to exclude children of a certain parent? Right? What I can say for sure is: "!parent=1034|1015" just isn't a valid selector it would have to be "parent!=1034|1015". But if you do this you can't overwrite it for a certain children to still show, as it will never get to it. Does that make sense? Maybe you can draw me a picture? Edit: corrected typo... oh dear.

Then you haven't studied the HelloWorld.module that comes as example? Hmm... it was the first thing I checked out when starting looking into modules and there's all examples also adding properties and methods. It's what definately blew my mind and made me stay with PW after all Edit: I don't mean to put you down or something was just wondering and I'm glad you found out now!

The answer is relatively simple and there would be different ways but best would be to: In a autoload module (HelloWorld.module) add the hook to ready() where the page being rendered is already set in $this->page So this would only add property to basic-page templates: public function ready(){ if($this->page->template == "basic-page"){ $this->page->addHookProperty('hello', $this, 'helloHook'); } } public function helloHook(HookEvent $event){ $event->return = "Hello World"; } After all I'm not sure this would make a lot of difference to just add it pages globally. But I could see this being useful for certain situations.

In InputfieldWrapper.php around #302 and looks like this if(strlen($showIf)) { if(strpos($inputfield->name, "_repeater") !== false){ $rep = explode("repeater",$inputfield->name); $showif_part = explode("=",$showIf); $showIf = $showif_part[0] . "_repeater{$rep[1]}" . "=" . $showif_part[1]; } $ffAttrs['data-show-if'] = $showIf; $ffAttrs['class'] .= ' ' . $classes['item_show_if']; } I thought maybe Ryan would read this and implement support for repeaters too, but you know how it goes...

@owzim see my post above where I explain this.... http://processwire.com/talk/topic/4189-flexibility-in-page-design/?p=45581 But repeaters don't support field dependencies (yet) I just hacked it into to recognize dependencies and it would work. and here I meant http://processwire.com/talk/topic/4189-flexibility-in-page-design/?p=45565

You didn't knew this?! Where have you been?

Go to the /wire/modules/Process/ProcessTemplate/ProcessTemplate.module #299 and replace the line with $row["{$numPages} "] = "$numPagesLink"; // space is required to make it work and you'll have the number pages count in the template table the search link. The $numPagesLink is already there but not output, maybe Ryan wanted it to add there but forgot.

Ryan has pushed the limit to 350 for now. So you can now again use the master ModulesManager version and set the limit to 350 in the module setting. He also removed the readme text from the feed so this will make the data loaded a lot smaller. Regarding save_mode, this is something that is deprecated in php 5.3 and removed in php 5.4, so not positive to add additional check for it. Thanks