Remapping songs to the database table

Hello, I recently had an issue where I was getting the following message on the front-end of my site, just on the music pages:

Warning: mysql_query() [function.mysql-query]: Unable to save result set in ..../libraries/joomla/database/database/mysql.php on line 534

I did some research, spoke with my web host provider, and discovered that this was most likely caused by a corrupt database table. So I set up to find the damaged table, and just my luck, it happened to be my muscol_songs table, which has over two thousand songs in it. Well, my attempt to repair the table did not succeed and when I went to replace it with a backup (three different ones, actually) I could not get the table to load because of a memory limit issue; my settings are sufficient, it seems to be on the web host provider's end.

So I have all these song files uploaded in my songs folder inside my Joomla directory, but I'm not sure we will be able to save the table. If necessary, I can retrieve the basic table itself from a really old backup from when I first installed music collection, but of course it won't have most my songs in it. My question for you is this: what is the best way (if there is one) to have the songs in my joomla songs directory pulled into the database without having to re-upload all of them? The albums already exist, so I'm worried that if we just pulled the songs back in through the album feature it will create duplicates and a big mess.

Any insight would be greatly appreciated!
Responses (2)
  • Accepted Answer

    Sunday, August 12 2012, 05:08 PM - #Permalink
    well, the best way, as you describe the problem, is to use the ID3 tag scan folder function. it will import all the songs and create albums and artists if necessary (or use current ones if they are already there)...

    are you running version 2.3?
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, August 12 2012, 11:10 PM - #Permalink
    Yes, we are on version 2.3. The only concern I have with the ID3 tag scan is that the information isn't always consistent; depending how the information was included, artists may be in there with their names/albums/song titles listed differently (for instance, Pink can be found as "Pink" and "P!nk"). We had already cleaned up a lot of that, so having to use the scan feature would probably still be a bit of a mess for us. That isn't a criticism of your product, just a reality of ID3 tags :dry: .

    However, luckily for me I was able to finally get one of my backups to work and the table is repaired, so most of my stuff is intact. But now I know that the ID3 tags scan feature is still probably the way to go if something does happen in the future.

    Thank You!
    The reply is currently minimized Show
Your Reply