Travel Steps Storyteller

Changelog

0.6.2

• Trips, steps, places and subscriptions, and the data kept with them, have names that start with travel_steps_ instead of ts_, so they can’t clash with another plugin’s. The first request after updating renames what’s already saved. Core REST serves trips and steps at /wp/v2/travel_steps_trip and /wp/v2/travel_steps_step now, and a step’s position as the meta _travel_steps_lat and _travel_steps_lon. A visitor who subscribed to a trip sees the subscribe form on it again, but stays subscribed.
• Trip pages load Leaflet under the handle travel-steps-leaflet, so a map plugin that registers its own Leaflet as leaflet can’t replace the copy that ships with this one.

0.6.1

• If a step’s sync missed a place, add it with the Trip place pattern from the block inserter, then click the place’s first photo in its Trip photos block. That photo and the ones after it, up to the next place, show under the new heading.
• Fixes: links on trip pages are the accent colour again, instead of the blue of the app framework’s colour scheme; back closes an open photo instead of leaving the trip, on browsers such as Android Firefox that didn’t already; on a trip with hundreds of photos, tapping one late in the trip opens it, not the one before, in Chrome and other Chromium browsers on phones.

0.6.0

• Travel Steps is now Travel Steps Storyteller, the name it has on WordPress.org. It lives in the folder travel-steps-storyteller, so WordPress sees it as a new plugin: deactivate the old one, remove its travel-steps folder by hand rather than with Delete on the Plugins screen (which deletes subscriptions and cached photos), then add and activate the new one. Trips, steps, settings and links are unchanged. An authentication proxy that lets /wp-content/plugins/travel-steps/* through needs the new folder instead.
• Visitors can subscribe to a published trip from the end of its page. Once a day, at the hour set on the settings page, each trip with newly published days or photos emails its subscribers one plain-text roundup, with links to the new days and a link to unsubscribe. An email address is confirmed before anything is sent, and logged-in users subscribe with a button. The trip’s edit page lists its subscribers and says when the last roundup went, to how many, and how many emails the site’s mail refused. Subscriptions are included in WordPress’s personal data export and erasure.
• Opening a link from a subscription email only shows a page with a button, Confirm subscription or Unsubscribe, so mail scanners that open every link change nothing. A mail client’s one-click unsubscribe still works in one step.
• A password-protected trip’s edit page has a share link that opens the trip without the password. Changing the password stops old links working. Roundups for a protected trip carry the link, and a link to a day lands on that day.
• Trip pages have link-preview tags, so a shared trip shows its title, introduction and cover in chats and social media.
• As you read a trip, the map zooms to the route under the place heading you’re reading, and the other days’ routes fade. A long move zooms out, across and back in.
• On a phone, one finger scrolls the page over the trip map instead of moving the map. Pinching still zooms it.
• The trips page lists trips newest first. Drafts without dates stay at the top.
• Photos taken at home are kept, without a place, when they’re in the trip’s Immich album, or favourites on any trip.
• A trip’s edit page names the days that have photos but no step, because none of their photos is a favourite.
• The block editor shows a step’s photos taken before its first place heading in the first Trip photos block, as the trip page does.
• Fixes: the lightbox’s close button stays on screen while a phone’s address bar shows, and its arrows are hidden when there is only one photo; a < in a trip’s introduction that doesn’t start a tag is kept; a draft trip gets its own URL when saved, so it can’t share a published trip’s; a password set on a step is dropped, since a step’s trip password covers it; two requests can no longer both take a sync’s lock.
• Hardening: the app’s pages can only be framed by the site itself; trip photos can’t be set as featured images; a share link sets a cookie for its own trip only; subscription forms check where a post came from.

0.5.1

• Photos are served from /travel-steps/photo/, outside REST, at the same URL for everyone: their URLs no longer carry a nonce. A photo that isn’t there, or that you can’t see, gets the same 404, which caches don’t keep, and photos only some people may see can’t be loaded by other sites. Old photo URLs redirect to the new ones. Like the trip pages, photos need pretty permalinks, and an authentication proxy that lets /travel-steps/* through now lets their photos through too.
• The trip edit page shows an introduction of plain paragraphs as text, not block markup, and an ampersand as typed. An introduction with more than paragraphs, such as an image or a heading, links to the block editor instead, and saving the form leaves it as it was.
• Fixes: a backslash typed in a trip’s title is kept when the trip is saved.

0.5.0

• After an Immich trip syncs, or you pin, hide or show a photo or change the cover, WordPress caches every photo visitors can see on the trip in the background. The trip keeps working when Immich is down or the author’s key stops working, at the cost of disk space for the whole trip. A few photos that always fail no longer hold up the rest.
• A daily sweep deletes cached photos that no trip or upload uses any more. The new site setting “Delete cached photos after (days)” also deletes photos cached longer ago than that; 0, the default, keeps them. Deleting the plugin deletes the photo cache.
• Cached photos are named after a keyed hash of their id instead of the id in their proxy URL, so on nginx without the deny rule nobody can fetch a hidden photo from the cache folder by its id. Photos cached by 0.4.0 or earlier are renamed on the first request after the update.
• On a phone, press Edit photos on the trip page to pin, hide or choose a cover. Until then the photo tools are hidden and can’t be pressed by accident.
• On touch screens you swipe between photos in the lightbox, which fills the screen; elsewhere it keeps its arrows. It no longer shows the previous photo while the next one loads, and it stops downloading photos you’ve moved past.
• Editors of a published trip get a warning when some of its steps aren’t published, and those steps’ badges say “Draft, not public”.
• Immich photos without GPS that Dawarich placed get a town and country from the bundled place names, instead of joining the place around them or heading a day “Somewhere new”.
• Fixes: photo URLs are never marked for shared caches when the viewer can edit the trip or the URL carries a nonce; a cached photo deleted during a request is fetched again instead of sent empty.

0.4.0

• A published trip can have a password. Visitors enter it on the trip page; logged-in users on its viewer lists, and anyone who can edit it, see it without one. Core REST follows the same rule.
• In a trip of uploads, photos taken at home stay on their day, without a place: they add no marker, place name or country. The notice after a sync counts them on a line of their own.
• Visitors now see published steps that have no position, such as a day at home, on the timeline without a marker on the map.
• Sync clears a step’s position when it can no longer find one, so a step placed before you set or widened your home no longer shows there.
• A country named differently by Immich, Dawarich or the place names counts once in a trip’s stats.
• On the settings page, your own section is now “Personal settings”, saved with Save, and its radius is “Home radius”.
• Fixes: core REST no longer returns or counts (in X-WP-Total) trips and steps a visitor can’t see, however the query names them; password-protected trip pages are kept out of page caches.

0.3.0

• Trips can use photos uploaded to the trip instead of Immich, which is now optional. Uploads are stored privately, served without their GPS data, and their file names are kept out of every listing. HEIC needs WordPress 6.7.
• Places are named offline from GeoNames, so a trip of uploads gets place names without Dawarich.
• A trip of uploads takes its dates from its photos, and follows them as you add more.
• Authors and up can make trips, each with their own Immich and Dawarich API keys and home location.
• An upload with no time taken can be given one; the date and time are suggested from the file name where it has them.
• An Immich album trip takes any dates you leave out from the album.
• Fixes: other authors’ steps no longer appear in a trip; pin, hide and cover need permission to edit trips; a date that doesn’t exist is refused instead of crashing sync.

0.2.2

• The button under a step’s photos says how many more it shows (“Show 2 more photos”), instead of counting the photos already on screen too.

0.2.1

• Dates sent to Dawarich are URL-encoded, so servers read the “+00:00” time zone correctly instead of as a space.

0.2.0

• Dawarich is optional: without it, trips are mapped from where their photos were taken.
• Distance includes flights, and GPS glitches are dropped from the route, distance and countries.
• Settings: remove a saved API key, and paste a “latitude, longitude” pair for home. Unreadable home coordinates show an error instead of being cleared.
• Warnings when a synced trip has no favourite photos, and when published steps are hidden because their trip isn’t public.
• The trips list runs oldest first by start date.

0.1.0

• First release.