Or turn off the preview.
Rather than trying to race the thumbnail being created, IMO it’s far simpler to enter all the text of your post, then turn off the post preview feature (one click), add in all your youtube links, save your post, then the next time you make or edit a post in some other thread, turn the post preview feature back on.
No rushing, no possibility you’ll lose the race, no hassles.
To each their own. The fast-post method has never failed me, and I don’t have to bother with turning post-preview off and on again. Once you get used to it, it’s as easy as making any other kind of post.
Rapid posting has worked a little more than half the time for me.
It’s good to have confirmed that the &1/&2 trick works.
Ack, ignore this.
Certainly not an expert in the topic, but I can’t believe that we’re all that weird. I presume one of the key reasons why we prohibit image/media uploads is to minimize storage consumption and the associated costs (assuming Discourse makes you pay for additional storage). Managing costs is something almost every customer is probably interested in to some degree and not allowing media uploads is the obvious solution.
If this is truly the first official bug report that suggests to me that there’s something more nuanced about our issue than just the combination of no images + YouTube…we can’t be the only people using that no images setting (let’s face it, literally everyone links YoutTube constantly).
Image hosting is so dirt cheap these that it’s not usually much of a pricing concern. It’d cost you maybe $1-$2 per 100 GB. At Discourse’s scale, it’s probably much cheaper, and the forum admins can configure a bunch of settings to limit storage. Anyway, we had a whole other thread about that, in which the consensus was “it’s more of a bureaucratic hurdle than a technical one, and we don’t want to risk our owners having any second thoughts about our forum at all” (which makes sense).
As for the bug report, well, it doesn’t take much to make it happen… you can just sign up for a Discourse trial (no credit card needed), follow the few steps on that bug report, and make it happen for yourself (I did).
It probably just is an uncommon setting… “images in my forum or not” was more of a 1990s and 2000s concern and hasn’t really been much of an issue since.
Image hosting is certainly cheap to Discourse, but what they charge their customers for using it is largely unrelated to their cost. Maybe it’s a non-factor.
Whether cost is a factor or not, I think the argument that we have some novel setup solely due to the disablement of images seems unlikely.
IMO, their standard plans are a rip-off. Their baseline Business plan is $500/mo for 100 GB. We’d run through that in no time for images. Even for text it seems a little tight.
I’d guess we’re still big enough to need an Enterprise plan, which starts at 200 GB, but that’s still not much.
Discourse does support external image hosting, like via Amazon S3, but that would require some effort to set up.
Why do you think it’s unlikely when it’s in the reproduction…? The setting that forbids image posting also breaks YouTube links. That isn’t a blind conjecture, but trial and error on a Discourse demo instance I spun up and tweaked until I got the same error to happen.
Was there a mod note posted here for a brief second…? I thought I saw something about a pinned thread, but it disappeared before I could read it fully.
Like was mentioned elsewhere we’re in the “call for a quote” category of sites so it’s hard to find list prices. I have no idea what we pay for storage, or how the cost scales with usage, but I think it’s safe to assume that Discourse is likely to monetize the heck out of media hosting.
I’m simply saying that I find it hard to believe we’re in some vanishingly small minority who forbids images. People here keep saying this makes us some kind of unicorn, that doesn’t pass the sniff test. Simply checking that one box, unless it’s deeply buried in some hard to find INI file, wouldn’t be rare.
I beleive the root cause analysis is sound, but either there’s another less obvious factor also presenting in the testbed, or this issue is more widespread amongst the Discourse install base.