riverbankcms 0.32.1 → 0.33.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/acceptance/matrix.mjs +3 -3
- package/dist/cli/index.mjs +14798 -12641
- package/dist/cli/init-docs/content/cli-reference.md +14 -1
- package/dist/cli/init-docs/content/content-management.md +17 -4
- package/dist/{entryCommands-KmqgJ44o.mjs → entryCommands-wcOr-fKy.mjs} +948 -560
- package/dist/{eventUpsertInputSchema-DQd8P8BZ.mjs → eventUpsertInputSchema-Df67rs3n.mjs} +2 -2
- package/dist/load-config-CKgy6Yct.mjs +4 -0
- package/dist/{load-config-C_QmGbxS.mjs → load-config-CexajivS.mjs} +2 -2
- package/dist/{plan-BKUvYkD2.mjs → plan-Bhv4iKa3.mjs} +1 -1
- package/dist/scaffold/index.mjs +2 -2
- package/dist/{sdk-event-upsert-D6oZBDR5.mjs → sdk-event-upsert-Y4Iyx0N4.mjs} +34 -11
- package/dist/{src-gbODrFjm.mjs → src-90EK8rKq.mjs} +144 -29
- package/dist/testing.mjs +4 -4
- package/package.json +1 -1
- package/dist/load-config-CTqBfOO9.mjs +0 -4
|
@@ -967,6 +967,19 @@ riverbankcms event occurrence cancel summer-fest summer-run <occurrence-uuid>
|
|
|
967
967
|
riverbankcms event occurrence delete summer-fest summer-run <occurrence-uuid> --yes
|
|
968
968
|
```
|
|
969
969
|
|
|
970
|
+
`event occurrence cancel` cancels a date's bookings, refunds them where they're
|
|
971
|
+
due one and emails the people booked. The result counts the bookings cancelled and
|
|
972
|
+
refunded, `--json` includes `cancellationResult` with the refund and email status,
|
|
973
|
+
and the command warns if any emails or refunds need attention. On a course the date
|
|
974
|
+
is dropped instead: everyone enrolled keeps their place and is told about it.
|
|
975
|
+
|
|
976
|
+
`event cancel`, `event offline`, `event occurrence update` and `event occurrence cancel`
|
|
977
|
+
need `--yes` on a remote target, because they reach people who've booked. So does
|
|
978
|
+
`event upsert` when the input cancels a run (`"status": "cancelled"`) or chooses what
|
|
979
|
+
happens to bookings (`--bookings`, or `bookings` on a run). Any other upsert, and
|
|
980
|
+
`event occurrence add`, doesn't need it, and local runs never do. `push events` has its
|
|
981
|
+
own `--yes` rule, described under Push.
|
|
982
|
+
|
|
970
983
|
Schedule syncs refuse changes that would move or cancel existing bookings unless you
|
|
971
984
|
choose a booking action explicitly. Use `riverbankcms push events --bookings move`
|
|
972
985
|
(or `riverbankcms push all --bookings move`) to move eligible bookings to their
|
|
@@ -976,7 +989,7 @@ cancelled as reviewed. Use `--bookings cancel` to cancel every affected booking.
|
|
|
976
989
|
while saving, its booking stays on the original date, which remains an exception.
|
|
977
990
|
|
|
978
991
|
The same flag works with a direct write:
|
|
979
|
-
`riverbankcms event upsert yoga --file yoga.json --bookings move
|
|
992
|
+
`riverbankcms event upsert yoga --file yoga.json --bookings move` (add `--yes` on a remote target).
|
|
980
993
|
SDK callers send `bookings: 'move' | 'cancel'` on each affected member of `runs`.
|
|
981
994
|
This is request consent, not a schedule setting: pulled files do not remember it.
|
|
982
995
|
|
|
@@ -662,9 +662,10 @@ It participates in normal media usage and recipe validation.
|
|
|
662
662
|
|
|
663
663
|
Public maps render ready inline SVG with theme tokens and attribution. Import
|
|
664
664
|
`@riverbankcms/sdk/styles.css`; no map JavaScript or vendor requests are needed.
|
|
665
|
-
Without a ready drawing, retain the details and ordinary directions links.
|
|
666
|
-
|
|
667
|
-
|
|
665
|
+
Without a ready drawing, retain the details and ordinary directions links. A
|
|
666
|
+
venue or business-address map loads its own place through `getPublicMapLocation`
|
|
667
|
+
when block data is prefetched; a custom footer callback receives this as
|
|
668
|
+
`footerBlocks`, as long as `Layout` has a `client` or `footerBlockData`. Private
|
|
668
669
|
provider evidence, job/storage keys and archive descriptors are never public.
|
|
669
670
|
|
|
670
671
|
### Event Category File Format
|
|
@@ -681,6 +682,18 @@ provider evidence, job/storage keys and archive descriptors are never public.
|
|
|
681
682
|
}
|
|
682
683
|
```
|
|
683
684
|
|
|
685
|
+
### What happens when a venue or category field is missing
|
|
686
|
+
|
|
687
|
+
`riverbankcms push` treats the file as the whole record. If you remove
|
|
688
|
+
`description`, `capacity` or `mapEmbed` from a venue file, or `description` or
|
|
689
|
+
`color` from a category file, the push clears that value on the site. A venue's
|
|
690
|
+
`locationValue` is the exception: if you leave it out the saved location stays,
|
|
691
|
+
so set it to `null` to remove it.
|
|
692
|
+
|
|
693
|
+
Your own scripts work the way the dashboard does. When you call
|
|
694
|
+
`client.venues.upsert()` or `client.eventCategories.upsert()`, any field you
|
|
695
|
+
leave out keeps its saved value, and `null` clears it.
|
|
696
|
+
|
|
684
697
|
### Event File Format
|
|
685
698
|
|
|
686
699
|
`content/events/yoga-class.json`:
|
|
@@ -813,7 +826,7 @@ export default defineConfig({
|
|
|
813
826
|
// denyIds: [...]
|
|
814
827
|
// roles: { editor: { ... }, administrator: { ... } }
|
|
815
828
|
},
|
|
816
|
-
// Settings sidebar (General/Emails/
|
|
829
|
+
// Settings sidebar (General/Emails/Team/etc.)
|
|
817
830
|
settingsNav: {
|
|
818
831
|
// mode: 'augment' | 'restrict'
|
|
819
832
|
// allowIds: [...]
|