Wedge

Are you looking for the importer tool?

Well, here it is! :cool:

https://github.com/Wedge/importer

Keep in mind, though:

- It's only tested on SMF 2.0 forums.
- Also, it comes with no guarantee, and it doesn't import any media files for now (including avatars and attachments).
- This is only there to help you test Wedge on an environment with more posts and users.

Hopefully, TE will improve the whole thing soon, or Pandos, or I'll do it, but frankly I doubt it. This is not a priority for me, I'm afraid...

I'm going to bed now. That leaves you guys unattended for about 6 to 7 hours. If you're unsure of what you're doing, just wait until tomorrow.

@Farjo, are you using Xamp, WampServer or something else?Thanks! Technically it's not a release, though... The long awaited Alpha 3 is coming this week, but I'm only releasing it once all server installation issues are solved.Yeah, I'm hoping that the more skilled users will take an interest in looking at the source code, and see how awesome it is.

For me, personally:
- Class-Skeleton.php, because (1) it's my first attempt at doing pure OOP programming, (2) the skeleton system is VASTLY superior to SMF's layer system.
- Subs-Cache.php, which has so many cool features.
- Class-CSS.php, and its wonderfully obfuscated code. Even I have some trouble reviewing it, from time to time, ah ah.
- script.js, gives you an idea of the amount of work that went behind rewriting SMF JavaScript code. I didn't simply integrate jQuery deeply into it -- I used all of my JavaScript knowledge to make the script as smooth, fast and short as possible. It's optimized *to the byte*. sbox.js is also an interesting piece of JS, in that it is superior to all the competition (jQuery plugins for select box replacements), and does it in *half the size* of the closest 'optimized' competitor (about 2KB gzipped). Again, a lot of work went into this.

For Pete -- I have to say, I think he would like to show off his ban code. Or perhaps his plugin code. He put many months of work into both of these, and it was all very carefully planned ahead. I'm pretty sure he'll push the SMF team into allowing these bits to make their way into SMF 3.0. In a few years time, then...Pete has been putting a lot of work into SMF 2.1, too. Sometimes I'll have a look at a list of his commits, pick a random one, and see that he's taken one of his Wedge commits, or ideas, and put it straight into SMF 2.1. It's a bit strange, considering he disavowed Wedge after leaving us. Is he trying to disavow SMF, too? :^^;:
Anyway...

Last year, Pete posted a quick list of features from Wedge that aren't in SMF. (Yes, because he loved SMF and wanted to rejoin them. I'm confused right now.)
http://wedge.org/pub/smf/8175/smf-with-a-different-name-huh/
Of course, many more features were added since then.
I'm pretty positive that despite having talented people in its team (shout out to Suki), SMF has no way to catch up with Wedge, because by the time it does, Wedge will still be more advanced, because I'll be busy catching up with myself.

I'd recommend you compare Wedge with Elk instead. Apart from the silly name, it's better than SMF in every respect.Please make sure you enable debug mode in Admin > Server > Debugging (which disabled PHP minification) before you post error logs. Line numbers are useless to me if the file is minified.

Okay, I'll just disable this feature in my next commit. During alpha testing, it's unwise to make debugging harder by default... :^^;:Isn't this not because of the Wine skin (not theme!), but because you're browsing through the Theme parts of the Admin area?
I should have specified: the Theme handling code is STILL in Wedge, but it will eventually go. It does NOT work, obviously, because themes themselves don't exist anymore. I just thought that you guys would rather have Wedge earlier, than wait for me to clean everything up and make it look like themes never were here to begin with.Thanks!
I'll make sure to pass it along to Pete. (Well, of course I won't, but I'm sure he's reading.)

Thanks!

Addendum: a few of the things missing from the current alpha...

- Topic privacy, not working I believe. Should be easy to fix. Just can't bother, for now.
- Contact lists: you can only manage them from user profile pages. I still have to write the UI to manage your existing lists all at once.
- Contact list privacy doesn't correctly nest in thoughts.
- Notifications aren't up to the task. They'll do mentions and likes just fine, but one needs to use that system to handle topic notifications as well, and then remove 'regular' topic notifications from the codebase. Also, fix scheduled e-mail notifications.
- The Weaving (default) skin needs some more work. :edit: And by that, I'm implying that you shouldn't try doing a 'proper' skin for now, because it'll be broken if Weaving changes too much. Unless you're prepared to fix your skins later, of course. I know I would.

:edit: - Themes are removed from everywhere, except the Admin area. If you navigate to the Themes area over there, you'll get bad error messages, so... Just don't bother, because it won't work anyway.

That's not ALL that's missing, but just a few of the things I'll have to focus on, after (1) I'm done with fixing the Wedge install & run process on other servers, (2) I take some time to have fun with JavaScript again. (I'm going to give another try to responsive sidebars, now that Chrome for Android finally removed its annoying swipe overrides.)

http://dev.mysql.com/doc/refman/5.5/en/blob.html

"BLOB and TEXT columns cannot have DEFAULT values."

offlimits_msg and data both are TEXT columns.
How come you're getting an error on this, then..? And just these two? There are plenty of TEXT fields... :-/

Try deleting all of wedge's htaccess files first. Can you then access the CSS.gz file directly?
If not, try deleting the root one. If it doesn't work it's probably a perm issue. If it works, reupload the htaccess and try to delete small sections of it until you find which one crashes it.

I'm trying to understand why compressing JS and CSS would generate a 500.

Okay, in Admin > Server > Settings (the first submenu), you should be able to choose what compression type to use. The default is Packer. Can you try other types, and tell me if they all generate a 500..? (Yes, included the uncompressed one.)

Okay! I merged your post to the original topic (repo name poll), and split this topic from my first post, so it'll look more like a 'proper' topic. ;)