Marius Wilms
Marius Wilms
We'll investigate, in the meantime try using whitelists when saving (also gives you more safety): ``` php $item->save(null, array('whitelist' => array('_id', 'title')); ```
`unset()` on a `Document` will indicate to **remove** a field mirroring behavior/name of [mongo's $unset operator](https://docs.mongodb.com/manual/reference/operator/update/unset/). Field removal/rename is not yet implemented in the `Exporter`. Even if those capabilities were...
Early beginnings/ongoing https://github.com/UnionOfRAD/lithium/tree/future/strategy-class
As long as this is solvable in userland, it does not have a high priority.
@shopblocks When you test and make the following ready for the framework's 1.1 branch, i'll merge it: https://github.com/UnionOfRAD/framework/commit/11d8d7a1b080b13f37e213caffac7fe4acc75305
@fedeisas Yes it's sparse, as sparse can get. Please open a ticket over at https://github.com/UnionOfRAD/manual so we have something to track it. Needless to say that we'd be glad for...
I can shed some light on it :)
Another idea would be to repurpose the `'list` option as it was done for datalists and text inputs. Please see https://github.com/UnionOfRAD/lithium/commit/cedc4d19550a9e42ba5250b9e906e8f2012896d1
My idea would be to _not_ create additional radios/checkboxes methods, but make people utilize `field()` in combination with `list`. Than any multiple-XYZ logic could be contained within that method. ```...
The only way I see is removing checking for `$_GET['url']` in Request and suggest the workaround @greut detailed for those who still need it: ```