Wedge

The GOOD thing with the Wedge.org upgrade, is that now you guys can all follow whatever additions I made to Wedge, because they'll usually be reflected on Wedge.org... ;) Just check the revision number in the webpage footer to be sure.

rev 1476
(18 files, 8kb)

! The double-post merge button didn't show up in some situations... Scratch that, in *most* situations really, because of an inverted default value. Also updated subtext to mention the delay should be indicated in seconds. Eh, it might have been minutes, all right? (Display.php, Admin.language.php)

! Applying John's suggested hack to allow HTML inside macro options (like the logo param in the header macro.) Untested, but should work. (Load.php, Subs-Template.php)

! ssi_recentTopics() was always pointing to the last post, instead of the last unread post for members. (SSI.php)

* Tweaked Track IP page to allow for language strings to show the IP anywhere inside the string, rather than at the end. (Profile-View.php, Profile.template.php, Profile.language.php)

* I'm sure there's a reason why I added a line-break after the quick reply textarea. There must be. For that reason, I'm removing it to fix the current layout, and eagerly waiting the day I'll go 'doh!' and unfix it. (Display.template.php)

! Wrong hardcoded membergroup ID in the thought system. (index.template.php)

* Modified French version to use 'cookie' instead of 'témoin' most everywhere. I just fired up IE9 and noticed how Microsoft is saying cookie in French. Cookies are yummy, whatever country you're from. (Admin.french.php, Errors.french.php, ManageSettings.french.php)

* Now using Help icon instead of '?' character to link to help popups in the membergroup permission manager. (ManagePermissions.template.php)

- We don't need the 'Switch to Full Editor' button to be animated on page load... It's just a waste of energy. (topic.js)

! Ah, the joys of CSS specificity... A table cell with a left class should be left-aligned, even if its parent row has a center class or whatever. (index.css)

! Public thoughts could overflow when shown in Display userboxes. (sections.css)

I'm waiting for market shares to go below Opera's. I'm develoong with Opera in mind and hypocrisy is not my thing. ;)

I'll merge all my posts together as soon as I understand why it's not working right now.Haven't met the problem again. I still have the Draft problem though. If I'm reading a long post (and just that), and scroll down, I'll see the "draft last saved..." message.Where is that set already? Theme options? Settings?I'm getting 'not_googlebot' errors but not at the same URLs as what I have in my error log...!
Here's a sample log:


The IP resolves to a domain at googlebot.com, which seems to belong to google.com... So it's a false positive isn't it..?I'm afraid that when it comes to me, I won't promise anything before we even start working on Wedge 2.0... I got bitten in the ass by AeMe integration, and decided it's already good enough as it is. I'll write a custom importer once I'm ready to do it, so that we don't feel pressed for time.Yeah, unfortunately.
I thought we'd rewritten that, but we probably only discussed it...YES!!!!!! :eheh:
We should add an iPod icon if not already done :P

Doesn't happen to me...?

@Pete and all> Where is the option to disable posting groups in the userbox? I believe there is one, but couldn't find it... The admin search didn't help, either.

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.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. :)

That's how I remade the translation from scratch, but it was still a horrible experience...

The problem with Wedge is that we don't have a tool to help with translation. SMF has their language tool, which has a despicable UI but at least makes it easier to translate strings and share them with others. No such thing for Wedge, unless the SMF team decides to kindly let us use it (it probably isn't available under an open-source license.)

I'm actually very wary of releasing our language packs. We could do it right now to give users a chance to translate it before we release an alpha of Wedge, but Pete adds so many strings on a regular basis, it's going to be hard for translators to keep up at this point.

So I don't know.

Funny vid. But it still won't make me forgive them for IE6/7... :P

Guys you have no idea how much trouble it was to keep Wedge compatible with IE6 for all this time. It doesn't look great,