Skip to content

v2.0.0

Compare
Choose a tag to compare
@mauricewijnia mauricewijnia released this 24 May 12:30

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-editor is 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.

  • Gutenbergable is no longer used, instead use RendersContent.
    • Rendered content is no longer stored in a table, so to migrate to v2 you have to move all content from the raw_content column in the lb_contents table to a column on your model's table.
  • Laraberg.registerBlock was renamed to Laraberg.registerBlockType
  • Laraberg.registerCategory was 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 mediaUpload function and passing it as an editor setting.