wurst-hans
wurst-hans
Using Phalcon 4.1.2 on PHP 7.4.18. Took me a while to figure it out. Having a simple form: ``` $form = new Form(); $form->add( (new Text('name'))->addValidators([ new Validation\Validator\Alnum([ 'message' =>...
I expect that `Form::isValid()` (see [here](https://github.com/phalcon/cphalcon/blob/master/phalcon/Forms/Form.zep#L649)) should pass whole `$data`, `$entity` and `$messages` to `beforeValidation()` and `afterValidation()` methods, similar to `Validation::validate()` (see [here](https://github.com/phalcon/cphalcon/blob/master/phalcon/Validation.zep#L539) and [here](https://github.com/phalcon/cphalcon/blob/master/phalcon/Validation.zep#L463)).
IMHO there is no solution currently, to handle unexpected array data in `$_GET` or `$_POST`. When validating forms or using query parameters of request, there is no buit-in way (i.e....
I'm running your watch face on three watches now. I'm using the `THEME_BLUE_DARK` but I loooove the blue color of `THEME_BLUE_LIGHT` which is different from the dark mode (even the...
IMHO there is no solution currently, to handle unexpected array data in `$_GET` or `$_POST`. When validating forms or using query parameters of request, there is no buit-in way (i.e....
I expect that `Form::isValid()` (see [here](https://github.com/phalcon/cphalcon/blob/master/phalcon/Forms/Form.zep#L649)) should pass whole `$data`, `$entity` and `$messages` to `beforeValidation()` and `afterValidation()` methods, similar to `Validation::validate()` (see [here](https://github.com/phalcon/cphalcon/blob/master/phalcon/Validation.zep#L539) and [here](https://github.com/phalcon/cphalcon/blob/master/phalcon/Validation.zep#L463)).
Using Phalcon 4, I'm doing some database queries using query builder and PHQL. Both methods have an issue on using `LEFT JOIN`. Image any relation, ex. `customers` and `addresses`. Example...
I've overseen, that Phalcon migrations do not seem to support `ROW_FORMAT` option on creating tables. How can this be done (i.e. how to modify migration classes manually to change that...
Using Phalcon Migrations 2.2.4 with MySQL and MariaDB (current v8 releases). When creating a dump, the migration files for tables using numeric columns (i.e. `TYPE_TINYINT`, `TYPE_INT`, `TYPE_BIGINT`) are created using...