What's Changed

• [Fix] Prevent fetching if endpoint was not found by @dnwjn in https://github.com/VanOns/laraberg/pull/175

Full Changelog: https://github.com/VanOns/laraberg/compare/v2.0.3...v2.0.4

What's Changed

• Debug - fix #174 by @arman-arif in https://github.com/VanOns/laraberg/pull/177

New Contributors

• @arman-arif made their first contribution in https://github.com/VanOns/laraberg/pull/177

Full Changelog: https://github.com/VanOns/laraberg/compare/v2.0.2...v2.0.3

What's Changed

• Fix embed by @winkelco in https://github.com/VanOns/laraberg/pull/173

New Contributors

• @winkelco made their first contribution in https://github.com/VanOns/laraberg/pull/173

Full Changelog: https://github.com/VanOns/laraberg/compare/v2.0.1...v2.0.2

What's Changed

• Bug Fix for Embed by @shaunluedeke in https://github.com/VanOns/laraberg/pull/163

New Contributors

• @shaunluedeke made their first contribution in https://github.com/VanOns/laraberg/pull/163

Full Changelog: https://github.com/VanOns/laraberg/compare/v2.0.0...v2.0.1

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.

In this release;

• Update Gutenberg to v.8.1.0
• Add ability to change the default placeholder
• Bugfixes

In this release:

• Update to Gutenberg v7.7.1
• Support for Laravel Filemanager 2.x
• Minor bugfixes

In this release:

• Update Gutenberg to v6.6.0
• Fix bug where reusable blocks were not showing anymore
• Implement a temporary fix for the image block crashing when editing a page that got saved without an image selected

In this release:

• Update Gutenberg to v6.5.0
• More future-proof fix for certain Gutenberg button's missing the button type 'button' (Fixes #53)

In this release:

• IMPORTANT: laraberg_content now gets saved when it's parent model gets saved, this means we have to set the the lb_content attribute BEFORE saving the parent model.
• Fix issue where the laraberg_content wasn't deleted when the parent model was
• Refactored method names to follow the Laravel convention names.

Big thanks to @IsraelOrtuno !

The first stable Laraberg release is here!

Changes since v1.0.0-rc:

• Update Gutenberg to v6.2.0
• Fix bug where some buttons would not respond because of a missing 'submit' type
• Remove external jQuery and moment dependencies
• Remove options menu since none of the options here were serving any purpose

Now that Laraberg is no longer dependent on GutenbergJS it's starting to look and feel good enough for a v1 release. We'll use this release candidate to do some final checks and tests before the official release, so let us know if anything is wrong!

In this release:

• Rename Gutenbergable->content() function to laraberg_content() to prevent name conflicts.
• Fix accessor methods not checking of laraberg_content object exists before returning their value.
• Fix bug where some buttons (HTML-block preview) would submit the form.
• Add message explaining drag & drop is not supported yet.
• More bufixes & cleanup

Laraberg was dependent on the GutenbergJS package, and since that package did no longer receive any updates Laraberg was stuck on Gutenberg v4.8. This release removes the GutenbergJS dependency and instead directly uses WordPress' Gutenberg package. This also means that Laraberg is now using the latest Gutenberg version (6.1.1)!

More in this release:

• Allow overriding of models - thanks to @mikebronner
• Add ability to set the editor content from JS
• Sidebar fixes

In this release:

• Disable broken WP blocks
• Reworked side bar to fix #17
• Fixed notices #16

In this release:

• Use laravel attribute accessors instead of methods for getting and setting content. The methods used for this previously are deprecated and will be removed in a future version. Check the README for more information.
• Delete content when the parent model gets deleted.
• Rework css overrides so huge wordpress css file could be removed from the project.
• Add ability to set a custom callback for search calls (only used in Button block as far as I'm aware).
• Remove links to reusable blocks management page.
• Add more inline documentation.

In this release:

• Add ability to add form fields to a sidebar
• Add asset publish groups to prevent overwriting config when updating Laraberg
• Remove padding from .gutenberg__content

Changes in this release:

• Implement custom API prefixes
• Add init alias for initGutenberg
• Notices now stick to the top, even when scrolling down
• Bugfixes

The first beta release saw problems for some users. There are some important breaking changes, so to keep using your current install there are some things you may have to do.

In order to support MariaDB we had to stop using the JSON column type. This means that there are some changes to the database structure. The easiest way to get around this if you've already used Laraberg is to do a database rollback and then migrate again. For those of you who do not want to do that I have attached a migration file to this release that you can use to update your database. I'm sorry for this trouble, but since it is still only a beta release, it's better to fix these issues right now rather than later.

Other changes in this release:

1. Reworked Laravel Filemanager implementation. Fixes #4 & #8
2. Use Gutenberg notices for error handling.
3. Update JS file structure.