Currently, you the Entry and Title class throw errors if you try to save them. This is intentional. Saving all the fieldtypes (reverse hydration) is a big hurdle.
There's also the issue of validation. If you truly want parity with EE core, you should probably validate according to EE spec (title length, url_title allowed chars, etc). You should probably use Ardent to utilize its built-in validation .
alexmglover
commented
9 years ago
Currently, you the Entry and Title class throw errors if you try to save them. This is intentional. Saving all the fieldtypes (reverse hydration) is a big hurdle.
There's also the issue of validation. If you truly want parity with EE core, you should probably validate according to EE spec (title length, url_title allowed chars, etc). You should probably use Ardent to utilize its built-in validation .