riverbankcms 0.33.0 → 0.35.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.
@@ -426,7 +426,6 @@ For theme and footer pushes, stale resolution updates only the metadata timestam
426
426
 
427
427
  ```json
428
428
  {
429
- "homepageId": null,
430
429
  "seoDefaults": null,
431
430
  "logoIdentifier": "positive-play-primary-logo",
432
431
  "logoDarkBackgroundIdentifier": "positive-play-logo-light",
@@ -586,7 +585,7 @@ riverbankcms entry upsert blog-post my-post \
586
585
  | ----------------- | --------------------------------- |
587
586
  | `--data <json>` | Entry data as JSON string |
588
587
  | `--file <path>` | Path to JSON file with entry data |
589
- | `--slug <slug>` | Entry slug |
588
+ | `--slug <slug>` | Slug for a new entry. An existing entry keeps its address; to move it, edit `slug` in its file and push. |
590
589
  | `--title <title>` | Entry title |
591
590
 
592
591
  ### entry publish
@@ -207,7 +207,6 @@ Use `content/settings.json` as the repo-managed source of truth for branding:
207
207
 
208
208
  ```json
209
209
  {
210
- "homepageId": null,
211
210
  "seoDefaults": null,
212
211
  "logoIdentifier": "positive-play-primary-logo",
213
212
  "logoDarkBackgroundIdentifier": "positive-play-logo-light",
@@ -513,6 +512,10 @@ riverbankcms push --env=remote --yes
513
512
  ]
514
513
  ```
515
514
 
515
+ **Changing an entry's address:** edit its `slug` and push. The push diff shows the change, and the push moves the entry to the new address straight away, the same as changing it in the dashboard. If the old address has been live, it redirects to the new one. If another page or entry already uses the new address, the push stops and tells you, and nothing in that entry changes. New slugs are cleaned up (`My Post` becomes `my-post`), and a slug you've pulled and not edited is left alone, even if it isn't in that form. Only a push moves an address, because it compares your file with the site first: `entry upsert --slug` sets the slug of a new entry and leaves an existing entry's address where it is.
516
+
517
+ Don't change the slug of a singleton entry, because its address comes from the content type's route pattern. Product, category and team member addresses are changed in their own settings, so a push refuses those too.
518
+
516
519
  ### Page File Format
517
520
 
518
521
  `content/pages/home.json`:
@@ -682,17 +685,26 @@ provider evidence, job/storage keys and archive descriptors are never public.
682
685
  }
683
686
  ```
684
687
 
685
- ### What happens when a venue or category field is missing
688
+ ### What happens when a field is missing
686
689
 
687
690
  `riverbankcms push` treats the file as the whole record. If you remove
688
691
  `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
+ `color` from a category file, the push clears that value on the site. The same
693
+ goes for `seoTitle` and `seoDescription` on a page file (the SEO title goes back
694
+ to the page title).
695
+
696
+ There are two exceptions, because leaving these out shouldn't lose something
697
+ that's hard to get back. A venue's `locationValue` stays if you leave it out, so
698
+ set it to `null` to remove it. A form file's `settings` stay too, including its
699
+ notification recipients, so set `"settings": {}` to clear them.
692
700
 
693
701
  Your own scripts work the way the dashboard does. When you call
694
702
  `client.venues.upsert()` or `client.eventCategories.upsert()`, any field you
695
- leave out keeps its saved value, and `null` clears it.
703
+ leave out keeps its saved value, and `null` clears it. `client.pages.upsert()`
704
+ and `riverbankcms page upsert` do the same for SEO fields: `null` puts the SEO
705
+ title back to the page title, and an SEO title you never set follows the page
706
+ title when it changes. `client.forms.upsert()` keeps the saved `settings` if you
707
+ leave them out, and any `settings` you send replace the saved ones.
696
708
 
697
709
  ### Event File Format
698
710
 
@@ -175,6 +175,7 @@ When portal auth is enabled, `riverbankcms init` generates these reserved routes
175
175
  | Route | SDK helper | Scaffold template |
176
176
  | --- | --- | --- |
177
177
  | `/portal` | `createPortalPage` from `@riverbankcms/sdk/next` | `portalPageTemplates` |
178
+ | `/portal/continue` | `createPortalContinuePage` | `portalPageTemplates` |
178
179
  | `/portal/tickets/[registrationId]` | `createPortalTicketPage` | `portalPageTemplates` |
179
180
  | `/portal/digital-products/[entitlementId]` | `createPortalDigitalProductPage` | `portalPageTemplates` |
180
181
  | `/portal/digital-products/[entitlementId]/files/[assetId]` | `createPortalDigitalProductFilePage` | `portalPageTemplates` |
@@ -190,8 +191,8 @@ resolver receives `content.type === 'portal'` and `content.site` on these routes
190
191
  The file route authenticates before redirecting to a signed download URL.
191
192
 
192
193
  For a custom host, `CustomerPortal` from `@riverbankcms/sdk/portal/client` takes
193
- `siteId`, `apiBaseUrl`, `portalToken` (nullable), `demoEmailSuppressed`, plus optional `callbackPath`, `logoutPath` and `bookPath`
194
- (defaults `/api/portal/callback`, `/api/portal/logout`, `/book`). Wrap it in the
194
+ `siteId`, `apiBaseUrl`, `portalToken` (nullable), `demoEmailSuppressed`, plus optional `logoutPath` and `bookPath`
195
+ (defaults `/api/portal/logout`, `/book`). Sign-in always goes through `/api/portal/callback`. Wrap it in the
195
196
  site's `ThemeScope`. This is a reserved route component, not a CMS block.
196
197
  `@riverbankcms/sdk/portal` remains the server helper entry.
197
198
 
@@ -204,8 +205,7 @@ includes it); this protects emailed gift tokens in outbound referrers.
204
205
 
205
206
  For a custom host, `RedeemGiftCard` from `@riverbankcms/sdk/gifting/client` takes
206
207
  `siteId`, `apiBaseUrl`, `siteTitle`, `publicContactEmail` (nullable), optional
207
- `token` and `code`, and optional `callbackPath`, `portalPath`, `homePath` (defaults
208
- `/api/portal/callback`, `/portal`, `/`). Its `onSignedIn` callback refreshes host
208
+ `token` and `code`, and optional `portalPath`, `homePath` (defaults `/portal`, `/`). Its `onSignedIn` callback refreshes host
209
209
  chrome after sign-in; the Next helper supplies that callback. Wrap the shared
210
210
  component in the site's `ThemeScope`. The callback POST expects JSON
211
211
  `{ portalCode }` from the same origin and returns JSON without redirecting.
@@ -311,6 +311,14 @@ riverbankcms delete entry <content-type> <identifier> --yes
311
311
  - Verify `key` is unique across all content types
312
312
  - Check for syntax errors in config
313
313
 
314
+ ### push-config refuses a content type change
315
+
316
+ Entries keep their data under field ids, so `push-config` won't remove a field or change its `type` while the content type has entries. The whole push stops before anything is saved, including with `--dry-run`, and the message names the content type and field. `--force-content-types` doesn't override this.
317
+
318
+ To rename or retype a field, add a new field beside it, move the content across, and leave the old field in your config as an optional leftover. Or delete the type's entries first, and you can then change its fields however you like.
319
+
320
+ The keys `event`, `course` and `service` are reserved for bookings, so you can't create a new content type with them. Use a different key, like `workshop` or `service-tile`.
321
+
314
322
  ### Entry page not loading (hasPages: true)
315
323
 
316
324
  - Verify `routePattern` is correct (e.g., `/blog/{slug}`)
@@ -277,3 +277,4 @@ Use a preview API key when `RIVERBANK_PREVIEW_MODE=true`; content/live keys cann
277
277
  4. Confirm the URL starts at `previewUrl`.
278
278
  5. Confirm the preview shell loads and editable content appears.
279
279
  6. Confirm `/api/preview/keep-alive` returns without authentication errors during the session.
280
+ 7. Change an entry or block with the CLI while the preview is open. The preview should reload by itself. A command that changes nothing doesn't cause a reload.