Sorry for any inconveniences these bugs may have caused.

To select more than one value all you need to do is for the value specify an array of all keys which will be marked as selected if found.

I also want to mention that I believe the version of the database class included with MiniMVC currently is a bit out of date.  I had completed some updates making it work properly and not give notices when running on E_STRICT.  So you will want to update the version by downloading the database class from the link on the right named “Database Class” and then placing it into the system/libraries folder of MiniMVC.

Any bugs you find please let me by either posting it as a comment or by emailing me it through my contact page.

Apparently the next video will be coming up within the next week or so, so I don’t know about you, but I can’t wait to see it .

• Fixed the multiselect drop down lists so that you are now able to select multiple items
• Changed the handling of the INPUT_CHECKBOX and INPUT_RADIO, prior to this release it was one value per button however from now on, these are now able to accept an array of items (like the drop down lists) in order to build the actual list of items

• Checkbox – the value will which is set will now enable and disable the checked value rather than set the ‘value’ attribute of the input element.  The value which should be passed in should be a boolean (TRUE/FALSE).  The posted value will also be returned as TRUE if the checkbox was posted checked.
• File – the element in the value array will now contain information about the actual uploaded file rather than not be present

Thanks Xylogeist for pointing it out!

Within the next few weeks I’m going to go into a complete recode for my database class. Because of this, I want to know if you guys can think of anything else which would make it even more powerful / that you would like to see implemented with it.

A few of the changes that I am thinking of are as follows:

i) Adding the ability to specify a location for a parameter to bind to – i.e. if I have a query where I am binding the same variable several times, i.e.

SELECT `username` FROM `trades` WHERE `ownerId` = %u OR `offerOwnerId` = %u

Where we are looking for everything from a single user (i.e. ownerId or offerOwnerId is one user’s user id). Currently you would have to bind it as:

$db -> query ( 'SELECT `username` FROM `trades` WHERE `ownerId` = %u OR `offerOwnerId` = %u', $userId, $userId );

I’m thinking of changing it so that you only need to provide the query function with $userId once. So now the structure of the query would be as follows:

SELECT `username` FROM `trades` WHERE `ownerId` = {0:u} OR `offerOwnerId` = {0:u}

Where the 0 is the element it will bind to the query (i.e. 0 is the first parameter, 1 would be the second and so on) then you could bind to the query like:

$db -> query ( 'SELECT `username` FROM `trades` WHERE `ownerId` =  {0:u} OR `offerOwnerId` = {0:u}', $userId );

ii) Change the parameter binding away from the use of the percent signs (i.e. %u) to using the curly braces (i.e. {u}). I could deprecate the use of the percent sign so anyone with the code written in the original format would receive deprecated warnings throughout their code when their queries are still running using the old syntax.

iii) Change all error messages to provide E_NOTICE when you have invalid parameters.

That is all I can think of for now. Anyone else have any suggestions on improvements?  If you do, please post them within the comments.

Thanks,
Andrew