dwise1 writes in Message 5:
[utube=2e9IRdEIM-0&t=2382s]
But now even that doesn't work anymore. Or at least it's failing with increasing frequency making the entire evolution a crap shoot.
If I suggested this somewhere then I made a typo. You can either use a complete YouTube URL like this:
[utube=https://www.youtube.com/watch?v=2e9IRdEIM-0&t=2382s]
Or you can use the [utube] dBCode with local options, where the options require commas as separators:
[utube=2e9IRdEIM-0,t=2382s]
Sometimes when I'm mucking around in the text processing code for one of the dBCodes I'll think to myself, "Who really cares what the separator is," and I'll get more expansive about the separator for that dBCode as long as the particular separator doesn't matter, but I haven't documented that.
But there's a downside. Sometimes when you ask yourself, "Is the separator a comma or a semicolon or an ampersand or something else?", you'll pick one, it'll work, and you'll be happy you were able to remember. Then it won't work with another dBcode if it wasn't comma. I should allow use of a consistent set of separators across all dBCodes at some point. Unfortunately this isn't a high priority, so you're best off using comma as the separator.
--Percy