Martijn Geerts

ProcessWire doesn't generate output, so SEO is as good as your own SEO skills. And ProcessWire is blazing fast, that SEO part you get for free.

The oranje already dancing:

I agree it was to painfull. ( I was really afraid of riots on the streets ) @totoff, Manuel Neuer playing forward making the formation very compact, Müller maybe the best player of this WK. The Mannschaft is a very well organized team. Gonna be very hard for any team. Tonight we first have to play against Argentina. We will see.

Gratulation an alle deutschen ProcessWire Mitglieder. Was für ein Spiel ! Brazilian football died yesterday...

Hi Mike, The link: "the amazing Ryan Cramer" doesn't link to a page. Thanks for the beautiful article !

@Christian: Building a theme is 1 but maintaining it is a whole other story. ProcessWire is evolving quick, very quick. So if the company has the time the money and the knowledge to update custom themes after every bigger PW update, it is doable. Just a scenario: Say you build a tiny website for a customer, estimated 20 hours of work. But you can't deliver the site within 2 or 3 weeks because the custom theme misbehaves after that awesome ProcessWire update. My personal opinion: I wouldn't go for that route.

The last years Javascript has become necessary in a lot of big websites. Without Javascript, YouTube & Facebook etc. won't function. We as developer can benefit from this trend. It's rare that the average guest turns Javascript off and if they did they know. With forms I hide the forms with CSS, and show it again with Javascript. If javascript is disabled, you can show it with the <noscript> tag. Captcha brings IMOH inaccessibility to the blind or people with low vision. Even for me, with perfect eye sight I have trouble to decipher them. The reason I see is that the purpose of those websites is not to serve out information. But the main reason is marketing. Eye catching is for those companies more valuable. Do those companies even know what accessible web is or do the care enough to pay for it? Then you have those sites where developers think in front-end templates and not in structure. If you see the tabs in Bootstrap, they won't function without javascript. I think that's a sad thing. With good and structured HTML you could make tabs work with some simple :hover functionality in CSS.

@LostKobrakai, I do use the @apeisa methode in combination with Inputfield Select File some times, it's very flexible.

Have you seen my post on setting up a web environment on Mavericks?

First of all i'm not sure of this, I haven't test it, but maybe you can give it a try. Not shooting will never hit the target I do think those messages are coming from InputfieldRepeater. Maybe you can hook before InputfieldRepeater::render, and suppress the errors with the getErrors(true) methode. $this->addHookBefore('InputfieldRepeater::render', $this, 'suppressFieldError'); public function suppressFieldError(HookEvent $event) { $repeater = $event->object; $repeater->getErrors(true); // clear errors }

Don't suspend Suarez:

@Dave, I use Incognito Window for that. I love it because I don't have to start 2 browsers and the Incognito window looks different then the default. Chrome on the mac: [ shift ] + [ command ] + [ n ]

Did you moved over the .htaccess ?

Just found a video where Louis CK is telling about people in the context of Cell Phones and Flying. Instantly I thought about Open source. vid on vimeo

@bwaked: take a look at this // here get() will get the page, while count, does not count it. parent page | +- page (status=hidden) (still I could be wrong socorrect me when wrong, no computer to test it right now)

There's a difference between the get and the count. Count uses the find methode internally, thus it won't count the page if it is in a hidden state. But the get will regardless of the state. Correct me here if i'm wrong.

The most common typo is any white-space character before the closing label or after the semicolon. // This fails, note the space before EOS; echo <<<EOS Hello world. EOS;

It could be a CSS z-index issue on the .navigation div. nav .navigation { position: relative; z-index: 10; } Could try to set the position & the z-index ?

I'm impressed by this theme nikola. I love the simplicity of the look. The module configuration makes so much sense. Sorry to be a nitpicker: 1. I would love to see that child elements in the tree are more indented. 2. The contrast of status hidden compared to default is to less. 3. The color of the fontawesome icons in the pagetree is to light. Take a look at the screen shot ( css glitch ) Overall very good work here nikola !

Big thanks David...

Hi Ralf, I love to see you succeeded with the site. Jahj ! Congrats with the outcome! The site is easy navigate-able and looks fine. It was a pleasure to help you out with the profile and big thanks naming me in the "impressum".

That should not a problem I guess. What about the time to live? If you didn't set it, it is an hour. ( 60 minutes)

@Manol, Regarding the Feed Module: 1. Could you validate your feed. It should say: "Congratulations!" 2. It can be that the ttl (time to live) is to high.

@MadHatter, love the flexibility of the FilenameArray, so I would love it would work with $config->styles & $config->scripts

I have a fusion drive in the mac, the rotating one failed. Just bad luck.