It’s two questions really.
I’m not sure whether you’d regard them as issues?
I encountered these over the last few days.
1. Alonetone seems to be setting the song page and mp3 url from the displayed song title, is this the case?
It looks like the uploaded mp3’s Title attribute provides the default for this - I’ve been taking advantage of that for some time.
But if I later use Edit to change the song’s display title, this also seems to change the url?
This has a consequence of breaking any external links to the song that have been distributed.
I discovered it the other day when I got fed up with my somewhat “shouty” way of indicating that a song was a demo. I changed a few from:
My Lovely Song (SONGWRITING DEMO)
To:
My Lovely Song (Acoustic Demo)
The urls all changed, and the external links to the songs were then broken.
Did it used to do this in the “old” days? I can’t remember.
2. Alonetone no longer seems to strip the “troublesome characters” when generating the song page and mp3 url?
In the past, a song title such as:
Delta Dawn (COVER) w. Lady Jane
Resulted in the following url:
/tracks/delta-dawn-cover-w-lady-jane
Nowadays a song title such as:
She’s On The Train From Brighton (Acoustic Demo)
Results in the following url:
/tracks/she’s-on-the-train-from-brighton-(acoustic-demo)
This caused a developer on another site to have a fun few days in his java.
He had fun with the ( ) at first.
And then had a LOT of trouble with the ’
I believe his code was replacing them with character entities when referencing the mp3 urls, and alonetone was responding with a 404?
He’s over it now (), so no emergencies for me or him.
But I’m guessing you’re not aware, and you’d actually like to strip characters that could prove unwholesome to other consumer’s processing?
(and, of course, fixing 2 feeds into 1 and… “aghghgh!!”)
It’s definitely not a show stopper for me, but I said I’d let you guys know