Leaderboard

Looking nice! But I don't know about you guys, it seems like Bootstrap feels a bit old and somehow weird to use, especially with all the cool stuff out there now (the structure is so restrictive IMO). Personally, I've completely switched to Sass recently and been using these as starting points incredibly efficiently: - A customized reset - Susy — Grid/Layout framework (you HAVE to try this!) — http://susy.oddbird.net - Bourbon — Awesome mixin library — http://bourbon.io - Bitters — Unobtrusive, minimalistic and easily editable boilerplate starter styles — http://bitters.bourbon.io Hopefully the new Bootstrap components aren't too tied together.

New processwire - responsive - site live on www.rugpijnweg.nl Thanks to this forum I found vxda who did all the coding while the design was done with his colleague Piotr from 7thavenue. Rugpijnweg.nl uses procache, and gets high scores on gtmetrix.com. It still needs some better way to optimize images and serve scaled images. Any feedback much appreciated, this site is meant to be fully responsive. Used Modules: - Procache (thanks Ryan) - ModulesManager (thanks soma) - ProcessJumplinks (thanks mike-rockett) - Thumbnails (thanks apeisa) - Get Video Thumbs (thanks adrian) Still some minor stuff needs done, happy to incorporate any feedback to make it better!

I would probably organize it this way: - /categories/ - category - /categories/questions/ - question1 - question template with repeater for answers - answer is just a text and checkbox 'correct' - question2 - ... - /categories/tests/ - test1 - test template - just a page reference field to ../questions/* - test2 - ... I am not 100% sure, but I think you can add children to users, since it's basically just a page? If you can't, it shouldn't be hard create a page for each user automatically, somewhere else in the tree. - /users/userId/ - ./attempts/ - /md5(pageId)/ - 'test-attempt' template. has a page field for a test, has a text input for a serialized form data. The workflow would be: 1. load test (build it from the questions) 2. take it 3. on submit, create new page under /attempts/, add answers, calculate results 4. show results. Bam. Done.

Try this $anzeige->save(array("quiet" => true, "uncacheAll" => false)); Any page save clears some cache. I don't know but it was always like this that when you have page saves on front-end templates happening. That might interferer with some methods that are cached previously. Not sure why prev and next are affected here, could be a bug or a side effect of an optimization for these methods that have some overhead. You can also call a $pages->uncacheAll(); before your $page->next and it won't work.

yep, i would also NOT trust this special field value because if the marker is moved it could also completely change the address generated by the google maps api! seperate fields would be the safe way but of course it depends how sensitive your data is... @limits: https://developers.google.com/maps/licensing

Foundation 6 for sites will have a release candidate out next month.

I'd really suggest storing this data separate to the map-marker data. In such a situation you don't want to depend on a tool you cannot surely control what data it spits out (changes to the module or the api).

Quickly toggle your checkboxes with extra action buttons via AJAX. The module adds functionality to InputfieldCheckbox so you can toggle the checkbox fields in the extra action buttons intruduced in ProcessWire 2.6.5 via AJAX. Github Page Download Link Requirements This module works only for ProcessWire versions later than 2.6.5. How to Install 1. Copy the files to /site/modules/ProcessQuickToggle/ 2. In your admin, go to Modules > Refresh for new modules. 3. Click the "Install" button next to "Process Quick Toggle". Usage Go to any checkbox field you want to enable quick toggle feature for. Setup > Fields > my_checkbox_field. There in the Input tab you should see an Enable Quick Toggle field. After you check it you will see some fields that you can fill based on your needs. Then save the field. Now there should be an extra button for every page that has this field in the Pages tree. Features Supports template contexts. Supports core FontAwesome icons. Any kind of feedback is appreciated.

Well, show_in_slide= will miss the ones that have value 0 while show_in_slide=0 will miss the ones that have no value but show_in_slide!=1 will fetch all that are empty and those with value 0 (or anything that has not value 1 for that matter) @rooofl i like your avatar, you realy wrapped your head around it