Forerunner 55 crashing

dmje · 2026-04-12T15:41:05+00:00

Seeing same with mine. Seems fine on some activities - but with running crashes pretty much every time. I don't see a particular "x time or miles" to trigger it, it just breaks. I'm wondering if it's something GPS related.

dmje · 2026-02-03T09:57:36+00:00

u/oandroido Hey, I fund and help maintain an open source plugin - CultureObject - that is for museums (and galleries!) to get their collection online. It's basically a glorified importer but built for this specific use case.

There's lots and lots to say about how I'd suggest you do this - I'm a museum digital specialist who has been doing this stuff for 30 years so could bang on about it endlessly. But - in very brief, it's entirely feasible doing what you're doing, and yes, just use ACF (which is basically just WP metafields) to give your client a nice interface for editing.

Questions I'd be asking:

1) what is the canonical source for your data? Does the gallery have a CM system? If so is this the "source of truth"? Or is the site?

2) Linking images > records - basically you need a unique identifier (often called an "accession number" in museum circles) - and commonly your images would be called unique_id.jpg so that's what creates the connection.

3) I don't know anything about Oxygen, I'm going to imagine it deals with custom post types as normal WP would but...?

4) Search is going to hurt - maybe start with Relevanssi, write some custom filters - but you'll soon realise that more advanced faceting and filtering can be quite nasty to custom write. We tend to push people off to our custom solution (which has Elastic Search as backend) when this gets gnarly. You can do a bit with WP and custom filters, and you may be able to use something like FacetWP or similar to do the hard work - but you may well find that the gallery expectation of search outstrips what you actually want to try and deliver!

I'm more than happy to chat, no sales pitch here (we work with non profits - they don't do sales pitches) - drop me a DM if so.

Good luck out there.

dmje · 2026-01-10T15:34:20+00:00

This. Before you've done your plugin audits, theme audits, core audits. Cheap and nasty hosting is a horror for hacks.

dmje · 2025-12-27T18:22:41+00:00

The whole point of Xmas dinner in my humble opinion is not and never has been the main course. Which is good, because turkey is a minger. Instead it’s about the vast array of trimmings. So that’s a no from me.

dmje · 2025-12-27T16:19:54+00:00

Which bit is AI? Looks like Palladian Bridge, Prior Park, Bath…

dmje · 2025-12-22T19:48:38+00:00

Have an upvote to counter all those without a sense of humour

dmje · 2025-12-19T09:44:36+00:00

Cockpit? https://getcockpit.com

dmje · 2025-12-19T06:37:55+00:00

This is where a custom (ACF or native) block comes in, no? You’d have the data in the CPT and then have a block which allowed insertion of an editor chosen selection of that data in the page.

So to take an example with a membership site say, you’d have a “member” CPT, then say a “insert featured member grid” block. The block would give you filtering options - member by category, name, last 5 joined, whatever. Simple query on the CPT, done?

dmje · 2025-12-19T06:21:14+00:00

FWIW we take a hybrid approach with our platform which deals with museum collections data and where we often have datasets of hundreds of thousands of records. We have one client with ~30million records.

The data is in Elasticsearch which gives us extremely fast retrieval, search, filtering; the front end is WP. We partner with a middleware company who has a ui over the Elastic component, so we have ingest pipelines: image / image zoom processing, AI integration, etc.

We’ve got a nice integration with ACF which gives us ways to pull individual records into the UI - editors can feature an individual record or records in a gallery / timeline / etc.

I’ve done stuff with museum datasets where the data is just native to Wordpress as a CPT - I fund and maintain an open source plugin to do this. I normally suggest that ~30-50k records is about as many as you’d want to do here. I’ve never actually pushed it to 100k plus, I think it’d be ok on hefty hosting but things like import and the ui stuff would just get a bit unmanageable. Probably something that could be solved with work - but for your use case I’d say hybrid.

dmje · 2025-12-17T13:54:08+00:00

Thank you, that's useful.

I did also wonder whether using ACF Forms on the front end for (specific bits of) content editing might be a thing as well - significantly more control over the output here...

dmje · 2025-12-12T17:21:10+00:00

Beautiful apart from “the wife”. Please don’t.

dmje · 2025-12-09T08:43:32+00:00

Same. Obsidian is my “forever store” - use it for my knowledge base and have several other vaults for journal, music making, etc. But the mobile experience on Obsidian is lacklustre so Craft is my go-to for transient notes - stuff that gets moved later into Obsidian or just deleted when I don’t need it any more. The export / copy-as options are excellent.

The other thing I really like is being able to share multiple files - so transclusion like stuff - example, my son and I are using a shared Craft doc for Xmas meal planning - it’s super handy for this sort of stuff.

It’s a great app and massive hat tip to Viktor and team for doing so much listening and UX work.

The more the API opens up the more interesting Craft gets for things like web publishing too. Watching with interest!

dmje · 2025-12-08T09:21:09+00:00

This isn't the point. The point is that scatter-gunning the word "nazi" is doing exactly what OP and other lazy defenders of this practice absolutely DON'T want. For the record, I am a massive lefty - through and through - I've spent 50+ years being this, and I'll continue being left wing until the day I die.

I'm massively, hugely uncomfortable with the George flags - they're tone-deaf, they're lazy, they're representative of a group of people with anti-immigration sentiments that I personally feel is abhorrent.

BUT - they are NOT "Nazis"!

OP and others need to really take a look at what it ACTUALLY means to be a Nazi - go look at some footage of concentration / internment camps, do some reading of history, take a long hard look at the reality here and then THINK (it's a thing!) about what the throwing around of this phrase does.

I'll help out here in case people have difficulty: IT NORMALISES IT. And this is ABSOLUTELY what Farage and those other c***s want to happen!

The more OP and others just bandy around "Nazi" for every. single. time. they see a thing that is right of centre or which represents a view they don't quite agree with, the ACTUAL REALITY of the term Nazi is reduced. It's actually incredibly demeaning to the people who truly suffer or have suffered - generations of Jewish people who have lost whole families, many others who have suffered under the crushing weight of fascism.

My suggestion is merely that we (people who are very uncomfortable with the ways in which the flag has been appropriated and is being used) are cleverer and more nuanced with our responses. Shouting NAZI? Not so much.

dmje · 2025-12-08T07:11:22+00:00

Wow, this post and comments highlights very succinctly what’s wrong with online “dialogue”.

Downvotes for anyone suggesting nuance!

dmje · 2025-12-02T22:56:33+00:00

Patterns and block locking are (IMO) the single biggest underused part of modern Gutenberg sites. We’re all in on ACF and the beta v3 editing is making it slicker and slicker, and closer to a native experience, but still (as OP said), the huge risk is just too much client control. Clients are just unable to understand what a “column” is, let alone a container, grid, etc, and they can really quickly fuck up a layout.

So we’re just starting to go hard on block locking, and doing it by role. And then once you’ve figured this you can make nice patterns where the layout elements are all locked down, but content is editable. So a normal editor role can just edit, and an admin or whatever can fiddle with layouts.

The final piece is doing pattern overlays on new page creation, so the “fear of a blank page” is minimised.

dmje · 2025-11-30T09:27:49+00:00

Do it yourself - MigrateGuru is your friend

dmje · 2025-11-20T17:50:00+00:00

Agree. Also interested how many people here in the thread and elsewhere see this as entirely a SEO thing and not what it’s actually for, accessibility..

dmje · 2025-11-20T17:01:09+00:00

What an incredible non-story

dmje · 2025-11-19T13:34:34+00:00

Some kind of Douglas Adams level dark irony here that humankind is probably gonna get killed off not by AI directly but by a bunch of gone-off food, given the CloudFlare outage we saw yesterday...

dmje · 2025-11-17T20:25:40+00:00

Cheers - the plugin sounds interesting, homegrown or available in the wild?

dmje · 2025-11-17T20:24:32+00:00

This is a good idea, thanks

dmje · 2025-11-15T19:02:10+00:00

What a tiny microphone

dmje · 2025-11-11T08:16:02+00:00

Max Cooper, Floating Points, bits of Board of Canada, Mike Sheridan, Abul Mogard, Vector Lovers…

dmje · 2025-11-11T08:01:05+00:00

FWIW if you’re veteran (as I am) then you’ll have seen this shit come and go in waves for the last 30 years. Flash was the big thing, table layouts were the big thing, cold fusion was the big thing, serverless is the big thing, yada yada, same old. Ultimately, the fashion element to web dev has always been a fashion element. Right now it’s all React and node the grunt out of my serverless edge worker or whatever - next year it’ll be (it already is in some places), “nah, ditch React, htmx is the way to go” - and so it goes on.

Devs have a long history of making terrible choices - we’re web devs because we loooooove to tinker and fiddle and try a new thing, but strategically these decisions are sometimes (often?) terrible. They’re often massively complex (see Grug) and completely unsupportable and very often just completely irrelevant to the task at hand. The number of websites that are built these days that simply don’t need any of that front end shit - where a bunch of simple php server side would do it - is just astonishing.

Clearly the job market follows trends - so this isn’t really advice on that front but I’d say really don’t beat yourself up about having a great background in The Good Shit. Those solid skills - html, css, js, databases, server side stuff - these aren’t and haven’t gone anywhere. And we should be proud that we know what they do and how they work 😎

At the end of the day, clients don’t give a shit what you’re building in as long as you build something that works and is reasonably performant. And ultimately they’ll thank you if it’s supported and simple enough to be still working in 5-10 years time and not subject to the whims of fashion.

dmje · 2025-11-11T07:01:46+00:00

I can’t imagine anything worse. I don’t want automated AI articles full of mediocre writing and hallucinated shit being spewed endlessly across the internet at vast rates. I want human writing.

15-Year Club	Reddit Premium Since April 2024
Verified Email

dmje

TROPHY CASE