It is now possible to edit the title and description of a file that has been previously uploaded to the site. To do this, visit your artist control panel, go to the files page and click the edit link next to the file you wish to edit.
I have started a thread to discuss how to make the site easier to use. Please
join the discussion. You can post any questions you have in here as well as get some useful information from answers that have been provided. Some of these answers will eventually go into an FAQ (Frequently Asked Questions).
Changing the description doesn't work for me... I can enter a description and even the preview works and when I commit, I get a message that says the changes were successful. But on the download page, there's still no description and if I click on 'edit' again, it doesn't appear either.
Changing the title works however. But there's an issue with the browser cache. For example, I have the song with the title "Five". I click on 'edit' and get to the page where there's the input box with the text "Five" in it. I change it to "Five2" and commit the change. So far so good. Then I click on 'edit' again and it takes me to the page with the input box again, but there's still "Five" written in it, because that page got retrieved from the browser's cache. If I hit refresh, it reloads and properly shows "Five2". That edit page should be marked as non-cachable.
I've had those cache issues with own projects and my solution was to mark *all* pages as non-cachable, when they are sent to a logged in user. This might be overkill, but at least that edit page should be marked that way.
Thanks for the report.
I can confirm saving the description doesn't work. I thought it did. I guess I need to be a bit more thorough in my testing in future.
I see immediately what I've done wrong. I'll upload the fix when I get the opportunity.
Would you mind telling me how to go about setting pages to be non-cachable?
Are you using Opera? I did find that it tends to cache pages for rather a long time.
Thanks again for pointing that bug out to me.
Edit: Fixed the non-updating descriptions bug. Cheers.
Editing description works now, thanks.
And yes I use Opera.
Setting pages as non-cachable is done via header(). I use the following combination in my scripts, which I probably have stolen somewhere:
header("Expires: Mon, 26 Jul 1990 05:00:00 GMT");
header("Cache-Control: no-cache, must-revalidate");
header("Pragma: no-cache");
The Cache-Control header has many ways of specifying things, for full documentation see the specs for HTTP/1.1 (RFC 2616). The Pragma header is for older clients, especially HTTP/1.0.
You might want to make sure that these headers are only sent on pages that you don't want to cache, not on all, unless you don't care about the additional bandwidth/load. As mentioned above, you might want to send the headers conditionally, only if it's for a logged in user.
I can make the headers unique to a page. They can be set before I insert the echo statement for the output from the template parser.
Thanks for that. It's nice to have someone who can provide some kind of feedback on things.
Edit: The changes have been uploaded. Do they fix the caching problem?
Yup, caching problem is fixed now for description editing.
Cool, thanks.
You could've waited another day. I've got some new upload code that needs testing
. I managed to fix a bug relating to MP3 SHA1 tags where either the tagless or full hash would be blank. Since you use OGG, that should be no problem but I might've broken something with that. Don't think I did break anything but you never know.