I just did an import from smf2. It worked fine on my machine but when the client ran it, a bunch of images got tombstoned, and recover from tombstone says to run rake uploads:fix_relative_upload_links Does anyone have a guess what might have gone wrong?

And now a bunch of images are just failing to render. That is, something like ![Green.jpg|1200x500](upload://6YplhQc9EFUmImEodEaVrSE7wMl.jpeg) is rendering https://host.com/images/transparent.png

Hi @pfaffman , did you find a resolution to this? I’m seeing the transparent.png in this thread: Rebaking old posts won't pull new S3 CDN URL after S3 bucket rename - #10 by Brad_Wood

Yeah, saw your earlier post and didn’t have a good answer. That S3 stuff can be tricky. My best free answer is make sure you follow the example in Using Object Storage for Uploads (S3 & Clones) (with CDNs for discourse and the bucket). If that doesn’t work and you have a budget I can have a closer l…

What causes rake uploads:fix_relative_upload_links

Поддержка

Brad_Wood (Brad Wood) 12.Январь.2021 21:28:23 3

Привет @pfaffman, вы нашли решение этой проблемы? Я вижу transparent.png в этой теме: Rebaking old posts won't pull new S3 CDN URL after S3 bucket rename - #10 by Brad_Wood

Тема		Ответов	Просм.
Missing uploads after S3 → S3 migration Support	0	435	16.05.2022
Rebaking old posts won't pull new S3 CDN URL after S3 bucket rename Self-hosting	14	1879	12.01.2021
Migrate_to_S3 Fails on Rebake Self-hosting	17	2497	10.09.2022
[Paid] Restore broken images uploaded to S3 Support	4	901	27.05.2018
Old image uploads become broken images Support	64	8771	08.06.2024

What causes rake uploads:fix_relative_upload_links

Связанные темы