Martijn Geerts

Congrats to all Germans, you guys played good!

Hi pine3ree, I had not the time and the computer to check out your module. ( Hardisk crash this week , today I will bring my 'new' iMac to a Apple reseller in the hope it would not take long for them to fix. ) Fontawesome page label is developed a few weeks before Ryan introduced Fontawesome in the core so it's a little bit redundant now. I'm not sure where to go with this module. I will definitely check out your module as soon i've time. You'll never know where this leads us. Thanks for checking out Font awesome Page label.

Welcome Kae !

First half Spain was better and the second half the dutch did great.. The system played is not old Dutch, but I don't think the dutch have the players to play the old system. 5-1 is to much for the game played. The Dutch have to watch out for arrogance. They need to keep prepared and stay focused. @dazzyweb, tnx

Thanks for the info Soma, Better documentation would be handy, but it's an awful lot of work to do & maybe even more to maintain it all. We all know Ryan works his but off. The amount of work he does isn't possible but he's doing even more than that What I think is possible is a set of really well written boilerplates for modules like the ProcessHello.module (Wonderful starting point). I would love to see a boilerplate for fieldtype & inputfield. The exchange of data information those two needs is still a little vague for me. Often the data you need is not net there. All in all I do think we are in a very luxury position, as documentation in general ( API level ) is very comprehensive.

The point is, what country would pwired choose !

Font-awesome icons are build for 14px or a multiple of it, if you make them 18px or 20px they will be less sharp. Love the changes in 2.4.4 ! Thanks, Ryan.

$pages->find("template=x, pagearrayfield=1234"); // where 1234 is the page ID // this will also work $wanted_page = $pages->get(1234); $pages->find("template=x, pagearrayfield=$wanted_page");

+1 like

Hanna code is if you talk in MODX language, a combined snippet & chunk on steroids

Passed back, coming from ProcessWire, values are stored clean, (else it should be blanked) and those values are given back in a clean state. If it's coming directly from an input methode, cookie, post, get etc... you should sanitise. If you need to build logic from user input, sanitise everything and test if you get what you want. If the testing fails, stop your script. Please correct me here on anything...

ps, please don't use my hat.

It's never wrong to test for a suspected outcome of the input. If you know the outcome should be a page id, and you know what template that page should have you can test and stop the script if it failt. // we want a page with the basic-page template $id = (int) $input->post->id; // typecast to integer, so we have an integer. $valid = false; if ($id) { // only if it's not 0, read zero $p = $pages->get($id); if ($p->template == 'basic-page') { $valid = true; } } // if valid is true, it's valid if ($valid) { echo 'Jeuhj jeuhj jippie jeej'; } I always test for a suspected outcome. Others will tell you more about security i think.

Stolen text: The $input variable is your connection to get, post and cookie variables, url segments, and page numbers. So that has nothing to do with HTML tags if you look at it strict. You don't have to if you use the sanitizers when using those fields, as that is already done with those fields. // no need to sanitize. Sanitizing is already done in the Fieldtype/Inputfield foreach ($page->fields as $field) { echo $page->$field; } But you're free to join Kongondo ! Please correct me here on anything...

@Joss: Just discovered my cauliflower showing her white curd... ( didn't thought that would happen )

$pages->find I guess ?

It's in the page tree. Selects and Checkboxes are infact pages (Fieldtype Page). For the page references, select the options page as parent. Look at the page tree below. options ( options template ) | +-- option one ( option template ) | +-- option two ( option template ) | +-- option three ( option template )

// Pre-populate ? $inputfield->value = 'Oei oei, tralalala'; echo $inputfield->render()

https://github.com/ryancramerdesign/ProcessWire/blob/master/wire/modules/Inputfield/InputfieldSelect.module#L267

Checkboxes like that a Page reference fields. Checkout this:

One suggested ProcessWire above MODX. Pitty I don't know which forum and which post.

@kongondo: I Love to see that that ! Kokondo the magic hat eater !

So, what about a dropdown <select> ? It might be text, but it's not free input... do I need to sanitize? You should never trust form input. You can change values in a dropdown in the dom inspecter and submit those changes.

It could be that the template 'formbuilder' doesn't have guest access. 1. Could you check at templates, check show system templates. 2. Select formbuilder template 3. check the access tab, be sure view pages is checked

Just overwrite the wire folder, installed modules are installed in your site folder, thus not overwritten. I got a nice message from cstevensjr, correcting me on the line above. He was kind enough to write the proper steps. Quoted from cstevensjr: Thanks cstevensjr, we are lucky to have you here !