Martijn Geerts

Textile is not something I can give, same for markdown... (pitty)

Somehow content editors love the <br> tag. On a 'random' base, the're putting in a line break. The cases of double <br> is easy to solve, but the single ones are just a pain in the *ss, as they could be intended. Think 80% of the <br /> makes me <grrrr />. For other elements I can use some pseudo elements to foo-doo visualize when they are used. For br thats not possible without some javascript I think. I even think: Disallow br tags at all.<br> How do you guys solve this.? Putting this in the the CSS, will visualize the BR. p br { content: "*"; display: block; margin-bottom: 0; line-height: 1; } p br:after { content: "<br>"; display: inline; background: red; color: #FFF; font-size: 12px; border-radius: 2px; margin-right: 2px; padding: 0 4px; float: left; }

lol

Don't know.... maybe

Seeing interesting things in that module ! It's the first one I see with the conditional autoload. ( Thought I red it before somewhere )

*pong*

Last days I'll see that for some inline text, the elements are faulty rendered to a default serif font. When hovering the element, the intended font-family is shown. After a page scroll the text gets back to normal most of the time. It effects lots/all webpages here with chrome 32 ones in a while. ( MacOSX 10.8.5. ) Do more people experience this ?

ModuleManager updated with ModuleManager , great work Soma.

Oké, Headers of all files send is every time 200. Would be nice if they were 304. Take a look at HTML5 boilerplate and then in specific for the htaccess settings. Or take a look at the wonderfull world of Willy . Edit: About the 200, my bad ! I enabled: Disable cache (while DevTools is open)

There are more stats and stuff queried then only the link to the server. Sometimes visiting a page will result in a "browser page" that says "this page looks suspicious". The URL has to be translated to an IP. And maybe Google wants to know if the lady has dinner ready. It'll do all these things before serving you. (some things you like other things you don't want) If there's one thing hanging, the waiting is for you. [ nice gift ]

Oh now you're lookin super-clean Pete

Well said Jeroen !

Big thanks !

2 more

I love Fanfare Ciocarlia when playing live )

That's from Dutch TV . Listening now, thank Diogo (Reminds me of Al Di Meola)

Cool, combined with Repeater Table you can setup a nice ordered table within 5 minutes

I also did not know that Source code of ProcessWire is Joyful to read.

Good solution, you can use the ->setName() when using the example of ryan to rename it ( remove the {sort_order} )

Short answer, no. But there are alphanumeric sort possibilities on run time. As $images is a Wirearray you could do: $images = $page->images->sort('name'); foreach ($images as $key => $image) { echo "$key => " . $image->url . '<br>'; // hyatt2.jpg => /site/assets/files/1/hyatt2.jpg } This will, sort the images on filename. -- And you can re-save the page with the new sort order. // Page is previously saved, but now we reset the order $page->images->sort('name'); $page->of(false); $page->save();

Little site note on the unique methode after the Wirearray of files: $config->jsFiles->unique() Appending unique isn't needed anymore, as the ->add('script-here') insures it's uniqueness. This works for 2.2, 2.3 and dev.

This is huge !

An other way could be using the module Date Archiver from u-nikos. It will do the archiving, list /year/month/day/ automagically.

Regardless of a CMS/CMF for sites like these you need to have decent knowledge of scripting. Next, the preparation before you even can start building sites like these takes awful lot of time. As Kongondo stated, those sites require significant amounts of custom code. 1) When you're new to ProcessWire and want to build this you need to have a good understanding of PHP/ OOP. 2) Accept the extra time it takes finding out `best practices` for PW. 3) Very, very good preparation. If you want to do it with PW, it's all in there. ps, I don't want to build anything not build on top of PW.

Unless you're doing pagination and want it to be acurate for example. And the other way around doesn't work eighter. You can't exclude if you want. A thing mentioned by Soma ( overhead ) second post, is a reason a good reason for not being available to exclude those in a selector. ( ps I do love these discussions, these discussion make us think. I really appreciate the response from Soma & you here )