Apostrophe 3.42.0 Schema field UI improvements, per-document permission, and improvements/fixes #4100
BoDonkey
announced in
Release Notes
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Howdy from Apostrophe Central!

Per-document permission with new inline array options and relationship suggestionsThe big feature of this release is an update to the enterprise
@apostrophecms-pro/advanced-permissionmodule. Permissions are more granular with the ability to modify the permissions of the individual page and piece documents. Permissions can easily be set for users or groups on each document. You can also easily duplicate permissions between parent and sub-pages.In developing this module, we also improved the core
arrayandrelationshipschema fields to make your UI look even slicker. You can now choose to output yourarrayfields as a table, rather than an accordion, and add a label and icon to your empty inline array. Therelationshipfield has a new suggestion UI that pre-populates with recent items for editor selection. Arelationshipfield within an inlinearray? Ooh, la la!We’ve also added a few little touches that make it easier for developers to inject new buttons into Apostrophe’s piece manager dialog box, and also launch the editing experience for any page or piece programmatically.
We are starting to show a nice uptick in open-source development community input. This release has an update to the
piece-type-importermodule by justyna13 and justynalodzinska. Thanks! This module helps you to populate and migrate pieces from CSV files. We encourage developers of all skill levels to contribute. Come by the Discord server and check out ouropen-source-contributionsandopen-source-talkchannels.Our engineers are moving forward over these next cycles on per-locale permissions and putting together a new system for offering page templates. As always, we are interested in your feedback. Please visit our Productboard to cast your vote on what features we should prioritize or consider!
Until next time remember that in software development, optimism is great, but Cypress tests are better!
Apostrophe 3.42.0
Adds
style: tableon inline arrays. It will display the array as a regular HTML table instead of an accordion.See the array field documentation for more information.
draggable: falseon inline arrays. It will disable the drag-and-drop feature. Useful when the order is not significant.See the array field documentation for more information.
See the array field documentation for more information.
utilityOperationsfeature of piece types now supports additional properties:relationship: true(show the operation only when editing a relationship),relationship: false(never showthe operation when editing a relationship),
button: true,iconandiconOnly: true.When
button: trueis specified, the operation appears as a standalone button rather thanbeing tucked away in the "more" menu.
utilityOperationscan now specifyeventOptionswith aneventsubpropertyinstead of
modalOptions. This is useful with the neweditevent (see below).await apos.doc.edit({ type: 'article' })(the type here is an example). To edit an existing document add an_idproperty. To copy an existing document (like our "duplicate" feature) add acopyOfproperty. When creating new pages,
typecan be sent to@apostrophecms/pagefor convenience(note that the
typeproperty does not override the default or current page type in the editor).editApostrophe event is now available and takes an object with the same propertiesas above. This is useful when configuring
utilityOperations.content-changedApostrophe event can now be emitted with aselect: trueproperty. If adocument manager for the relevant content type is open, it will attempt to add the document to the
current selection. Currently this works best with newly inserted documents.
$t(key)to localize a string insidean interpolated variable. This was accomplished by setting
skipOnVariablesto falsefor i18next, solely on the front end for admin UI purposes.
choicesnow accepts a module prefix to get the method from, and the()suffix.This has been done for consistency with the external conditions syntax shipped in the previous release. See the documentation for more information.
viewPermissionproperty of schema fields, and renamedpermissiontoeditPermission(with backwardscompatibility) for clarity. You can now decide if a schema field requires permissions to be visible or editable.
See the documentation for more information.
Fixes
@apostrophecms/doc-typeand@apostrophecms/submitted-draftswhere we were usingcanCreateinstead ofshowCreateto display theCreate Newbutton or showing theCopybutton inManagermodals.Apostrophe 2.227.0
Adds
Apostrophe 3.x modules
@apostrophecms/piece-type-importer1.1.0This module adds an optional import feature to all piece type modules in an Apostrophe project. This feature enables importing pieces from CSV files where it is configured.
Adds
Enterprise modules
@apostrophecms-pro/advanced-permission1.3.0This module provides more granular control over content permission. It allows the creation of custom groups with proscribed abilities and the ability to assign users to as few or as many groups as desired. Contact us or visit our new pricing page to learn more.
Adds
Utilities
@apostrophecms/content-upgrader1.0.0A tool to migrate your content from Apostrophe 2.x to Apostrophe 3.x. That is, it creates a new database in the A3 format, and copies over the uploaded media. This tool does not upgrade your source code.
Changes
1.0.0for consistency.@apostrophecms/code-upgrader1.0.0The Code Upgrader handles a portion of the required modifications for an Apostrophe 2 (A2) codebase to run Apostrophe 3 (A3). It will also identify many specific lines and sections of code that a developer will need to convert manually.
Changes
Beta Was this translation helpful? Give feedback.
All reactions