Yet another blog about PHP, HTML and CSS

Nette forms documentation lacks information about enhancing your forms while still using the default renderer. I offer here a list of solutions for the most common needs, using getControlPrototype(), getLabelPrototype(), getSeparatorPrototype() and setOption().
(more…)

Sooner or later, you’ll find yourself in a need of filtering out NULL values along with some other criterion. You’ve tried ->where(array('something' => $value, 'other_thing IS NOT NULL')) and got an error. I’m sure you’ve spent considerable time looking for some kind of negation that would work with NULL and I bet you’ve even tried to stick NSqlLiteral somewhere in there. I’m here to rescue you.

(more…)

You probably know that you can define your form as a component in a class of its own and handle its submission in the same class. This is handy if the submission handling logic can be isolated and is independent of any presenter. But what if it needs to be a part of some particular presenter lifecycle? Then you need to force the form to submit to this particular presenter.
(more…)

If you ever tried changing your form from POST to GET with $form->setMethod(‘get’) and then render it with macro {form} … {/form} I’m sure you discovered that your submission callback doesn’t trigger. Apparently it’s difficult to resolve this in a clean way so until the Nette team finds a solution you’ll have use some sort of a hacky workaround.

(more…)

Say you have a search form on a page that lists customers but you also want the same form on the main dashboard page. You have two options: either define your form in a third place and use that definition in both createComponent… methods, or you can create it with createComponent… in BasePresenter and inherit it by both the CustomerPresenter and the DashboardPresenter. Or you can use a hack.

(more…)