grrr, the importer is alpha, too and Wedge.org was a heavily modified SMF version... ;)
I'm just sayin'. Your importer is priceless (otherwise I'd have rewritten it heavily, considering I have SVN access
:P), but it's definitely not ready for prime time. For instance, I experienced another 'duplicate key' problem with the member table at one point. It happened once, then the second time it worked. I had to restart the importing several times though. Once for the member table, and several times over another 'duplicate key' in the attachment table. I looked into the database and noticed that one of the only differences with other attachments, was that the message ID was relatively ancient compared to the other close attachment IDs. Which was surprising because it was posted at the same time as the original message... Anyway, I decided to simply remove the attachment (I edited the post to apologize for the issue, but it was not an important attachment anyway), and restarted the process. This time, it worked.
However, about 10 attachments (out of ~875) weren't imported. I'm talking about the database entries. Perhaps your importer tests against attachment errors and removes them in case there are any? Anyway, now here's how the attachment folder is structured: it's a serialized array with three folder names, attachments, and two sub-folders that are actually empty. I guess they'll be used once Wedge reaches a certain number of files in the folder? It already takes me over 2 minutes just to download the file index for that folder, very amusing... So, given that structure, I would have expected to see attachments moved over here. In fact, the only files that were in this folder were the avatars. Yay.
So here's what I did: I simply took the original attachment folder, renamed all files to give them the proper extension, and rewired the attachment folder to the DB setting. Then attachments started working again.
As for avatars, my issue was that they're of attachment_type = 1, meaning their filenames are in plain view. The importer didn't retrieve the attachment type, simply re-created the files in the attachment folder, and thus I was forced to reset the attachment_type flag in the database after I moved the folder to the root. Thankfully, it wasn't too complicated.
So, my main concerns for the future (and suggestions for improvement) would be:
- try and fix the duplicate key stuff...
- if avatars are static and in plain view (= EXCELLENT performance improvement even in SMF), do not import them as hidden files,
- offer users the ability to keep all of their data (gallery, attachments, avatars) in the same place as before (i.e. their old SMF install), and just update the Wedge settings to point to these folders. I think this would be really great, because it means not having to worry about moving files back into their original place when moving Wedge into the SMF folder.
Really, installing Wedge and importing SMF was the easiest part (except for the duplicate key problem). The hardest part was moving the folder. Considering that SMF users will install Wedge and use the importer *mainly* to test-drive it and decide whether they want to use it instead of SMF, it would be great to be able to keep all data in the SMF folder.
Congratualations, great to see Wedge in action :)
I'm still in awe. I wrote the skin, the theme, I did all of these little animations, I tested Wedge for a year and a half, and I still can't believe I'm freaking using it right now, on a public website. To me, Wedge was always my subject of study, the purpose of my work. Now, it is also a TOOL to help me do my job properly. I'm thankful to myself, to Pete and to everyone who helped build the project in the first place.
:)
