Martijn Geerts

Don't think so. Name should be english... please :_)

It's old thing those gremlins. Old versions of Safari indicates an alert sign in the right bottom of the window when safari discovered sucha weird character.

All strings can be translated in PW. It is as easy as. $this->_("provide your english here") or __("provide your english here") instead of "provide your english here" Then If someone needs to translate your module the translatable strings are in there. The translator should go to /Setup/Languages/ Then to the language, say Dutch. There fill in the path of your module ProcessWire will detect all __('translatable strings') & $this->_('translatable strings') and present the translator with inputs. Then The translator can type in "vertaalbare tekst" go to the next, etc. translate them all. Save... Done $field->description = __("Fringilla Sollicitudin Consectetur"); or $field->description = _$this->_("Fringilla Sollicitudin Consectetur"); To make it more fancy, use the sprintf or printf printf(__("Created %d pages."), $count); example protected function buildForm1() { $f = $this->modules->get("InputfieldText"); $f->name = 'fieldTitle'; $f->label = __('Field Title'); $f->required = true; $f->description = __("The title of the page field to be created."); $f->notes = __("Use capitals, spaces etc."); $form->add($f); ..... }

Hai Adrian, sorry bugging you again. What about making it __("multi language") ?

Maybe you forget the . before .main. Try to remove the - sign and add it. Safari outputs ÔÇô instead of the - If you own BBEdit. Trow your Document in, go to text, and click Zap Gremlins.

Sorry to say, but that's stupid Markup. ( just looked at the Zurb Foundation Website ) In between a list, list nothing "<li class="divider"></li>". If you have the navigation in a variable, say $nav, maybe you could do something like: $nav = str_replace("</li>", "<li class="divider"></li>", $nav);

Scaling should happen on later time, on template level I think. (Don't mess up the originals) code for your template: $images = $page->images; // assumed that the field called images if(count($images)) { foreach($images as $image) { $width = $image === $images->first ? 600 : 200; $thumb = $image->width($width); echo "<img src='{$thumb->url}' alt='{$thumb->description}' />"; } } This should work, didn't test it.

it's the third one in the picture.

@RIVO I love to hear this: For the moment I'll stick to PW for my personal projects and learning. You won't regret learning a little PHP. Even if you leave PW, the knowledge is there, ready to use everywhere.

I would say: ProcessWire has more basic features then any other CMS out there that I know. ( but it's not a one two three, click, click: I have a new website ) In other CMSses you have to learn a lot of things to (maybe it doesn't look like code, but it is). But when you switch to an other CMS your Knowledge is gone. I don't want to invest in a unsure future. Who can say that the big 3 will be the big three within 3 years. If you don't want to code at all. I think it's better to not a CMS at all. There are plenty of website builders for Mac or PC.

That number is the ID of the Page where the image lives. It's the key to the image. I consider the images in there as content, so they belong to the content of the page. So there's no easy way to change this behavior. Next to that It's very powerful. Other images like GUI don't have that direct relationship so they can be in a folder where you want. And just link it in your templates, css or js.

Wil test tomorrow, thanks for all your effort! Did the testings this morning... simply love it. Thanks for bringing in my ideas !

The lack of this was the reason why I ended up making the nav my self. Things changed, Huge addition !

<adrian>Do you mean all existing text fields from the entire site? I am not sure what would make them compatible or not</adrian> Yep that is what I meant. Reuse of existing fields makes sense, so it would be nice to see a list of all fields that extends from FieldtypeText. ( all compatible I think )

I thought I had a split personality lately !

Works ! $field->notes at Select Options contain a lot of text. Maybe move the to $field->desc. And use the $field->notes to echo out all compatible text based fields. ps, your implementation of my suggestion is way better then how I thought about it.

Adrian I think you broke something in your latest commit. In the option with multiple fields The pagefield, doesn't store the Parent Page. ps, I'm smiling while using this Module (aside: People have to take care they're not creating a Hani amount of fields )

<adrian>how about I allow the Select Options field to also handle multiple fields if entered? I might take a stab at that and see how it goes - stay tuned!</adrian> I didn't thought about that, but thats even better, thumbs up !

Sorry Kongondo, I guess it is safer to assume that Ryan has been quite busy as long as I know ProcessWire.

This is great Adrian, extremely handy! As this is a more advantaged tool I was thinking of: Select a template to use as child page ( with more fields in a template ) Say you select a child template with the fields: title, type & year. Then at Select Options: BMW, m3, 1987 Mazda, 323, 1986 VW, Golf, 2012 --- Even without this it's a real time saver !!!

If you enable URL segments on the home page you could get what you want. Or you could create the rootParent catering and do your search there.

Can you tell more, I don't understand what you're after.

Thank you Soma !

Tnx ryan. Had a hard fight building this module with scoping as i'm not very comfortable with OOP. I needed some functions to be static ( for getModuleConfigInputfields ). It was a bit of trial and error. All points you mentioned are fixed in the latest update. What is still unclear to me is why this module still needs a empty init() to function.

Just added the module to the modules directory. It's in a pending state.