| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2022-05-24 | 1.2 kB | |
| v2.0.0 source code.tar.gz | 2022-05-24 | 4.5 MB | |
| v2.0.0 source code.zip | 2022-05-24 | 4.5 MB | |
| Totals: 3 Items | 9.1 MB | 0 | |
Updating from v1 to v2
There are some big changes in Laraberg v2.
- Content is now stored in a column of the model's table
- WordPress packages are available in Javascript, this means we can use a lot of the functionality, like hooks, that's already available in Gutenberg.
@van-ons/block-editoris used to render the editor, this makes it a lot easier to keep up with the latest Gutenberg versions.- Server side rendered blocks are now supported
Unfortunately this means that updating to v2 is not a straight-forward as we would like it to be.
Gutenbergableis no longer used, instead useRendersContent.- Rendered content is no longer stored in a table, so to migrate to v2 you have to move all content from the
raw_contentcolumn in thelb_contentstable to a column on your model's table. Laraberg.registerBlockwas renamed toLaraberg.registerBlockTypeLaraberg.registerCategorywas removed, you can use the wordpress exports to register categories.- The configurable sidebar was removed.
- Laravel File Manager is no longer supported.
- This can be solved by implementing your own
mediaUploadfunction and passing it as an editor setting.