Link to "versions" not working anymore?
In Workers, I used to be able to click on the version number and it would open the site instantly - well, I'm pretty sure that was the case - but now it's not working?
Did something change on Cloudflare? is this a bug? is this expected? or maybe I'm being gaslit here and it never worked this way???
I also used to get a link back in my cli that I could click, and since wrangler version 4.30 - there's no link 😢
*p.s. also - why is there's a "workers" or "pages" tag 😕 *
7 Replies
It looks like you don't have preview urls enabled
In your Wrangler config, you can enable them with
preview_urls = true
and there's no workers/pages tag as they have dedicated channels #workers-help / #pages-helpStrange, let me see if one of my PR's killed my
preview_urls = true in the jsonc file.
Thanks for getting back to me - and will post in the relevant channel next time! (sorry!)Also possible you're now using Durable Objects
as per https://developers.cloudflare.com/workers/configuration/previews/#limitations we do not generate preview URLs if using durable objects currently
ah - I was about to write and explain that previews ARE on, but yes - dang it - I've just moved over to DO's!
Ah, that's - that's sad - very sad - haha - ok, oh boy, this is gonna be fun.
Do you know if it's part of the roadmap? or am I going to need to find a permanent solution to this?
I'm guessing the only possible solution today is to spin up "dev" worker - and then move from dev to prod and ensure to keep databases and all 'nsync? Or do you know of any other work-arounds?
mmm, maybe they can both reference the same database - that will help? or maybe that's bad practice as I may need to test migrations on the "dev" worker to ensure it works on production.
Maybe this is for the best 🤷
Preview URLS don't work with Durable Objects right now, so that's why you stopped seeing them. It's not a bug - just a limitation.
Best workaround is to set up a separate dev Worker:
-point it to its Durable Object namespace if you want safe testing,
-Or share the same namespace with prod if you need the same data(but that's risky)
No official timeline yet for Do preview support, so the dev/prod split is the way to go for now.
Thanks TakaDev92 - I've decided to create a completely seperate environment as a staging env, with it's own DB and DO etc etc. In the long run this will be a better solution anyway. But I do love the power of the preview URL's so hope support for Previews with DO's do come soon 🙂
That sounds like a solid approach.