Albert Boada
Albert Boada
Recently _Mixcloud_ has started returning incorrect data on _Embed v3_: https://oscarotero.com/embed3/demo/index.php?url=https%3A%2F%2Fwww.mixcloud.com%2Fmalka11%2Fmalka-pres-lockdown-sessions-anjuna-history-2010-2020-%2F Whereas it still working as expected on _v4_: https://oscarotero.com/embed/demo/index.php?url=https%3A%2F%2Fwww.mixcloud.com%2Fmalka11%2Fmalka-pres-lockdown-sessions-anjuna-history-2010-2020-%2F Any idea on what could have changed (either on _Mixcloud_...
Current behaviour of the library when facing this scenario: ```json { "foo": [ {"bar": [null, null, 3, 5, 6, null]}, {"bar": [1, 3, null, 5]} ] } ``` ``` foo[*].bar[]...
Filtering for relations configured this way (associative conditions) was NOT working: ``` php var $hasOne = array('Located' => array('conditions' => array( 'Located.model' => 'Employee', ))); ``` Filtering for relations configured...
Patches Array Datasource by disabling fields-filtering feature, since it was not behaving properly when querying hasMany/HABTM related models (see commit's source code for detailed explanation). > The reason for this...