Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Change Form Input Type in CakePHP3

DZone's Guide to

Change Form Input Type in CakePHP3

Generated code platforms like CakePHP can be a real time-saver. But, what happens when the platform infers form input types from database column types and gets them wrong? Author Lorna Mitchell describes what to do in this situation.

· Web Dev Zone
Free Resource

Learn how to build modern digital experience apps with Crafter CMS. Download this eBook now. Brought to you in partnership with Crafter Software

I've been having my first experiences with generated code, generating a new admin backend using CakePHP3 (yes CakePHP is still around, it's alive and doing rather well in fact!). So far it's going great and producing a much more complete solution than I'd have managed for myself on this timescale.

One thing is bothering me though: it guesses form input types from the database column types, which mostly works well but sometimes it picks something that doesn't reflect the way that the user will store information in this field. It's actually pretty easy to change the forms that get generated though, so here's an example.

I have a field in my database called "enabled" which is declared as int(1)—it holds a boolean value.

The view code simply says which form field to output:

echo $this->Form->input('enabled');

For most fields this is all I need, but this one gives me a number field like this:

Screenshot from 2016-03-13 13-17-57




In this case, I would prefer a tick box for the user to just indicate yes/no on the value. I can tell CakePHP that by passing an additional argument to the input() method containing the options I want to use, and setting the type option like this:

echo $this->Form->input('enabled', ['type' => 'checkbox']);

This gives the result I wanted:

Screenshot from 2016-03-13 13-18-32



You can change all kinds of things really easily—try adding a label option (I'm sure I'm not the only person with not-useful-to-humans column names in an old database!) to add better labels. There is also really excellent documentation in the Cake Cookbook—see this page for details of creating and modifying form fields.

One thing I was worried about with generated code was maintenance—what if I generated a form, customized it, and had to regenerate because we added a field? In fact, since we use git this works brilliantly, I just generate the new version of a file and then pick out the bits I want and throw away all the other changes!

Crafter is a modern CMS platform for building modern websites and content-rich digital experiences. Download this eBook now. Brought to you in partnership with Crafter Software.

Topics:
php ,cakephp ,forms ,input ,database

Published at DZone with permission of Lorna Mitchell, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}