Wedge

Really, it only triggers if Wedge can't fix the tags by itself.

So you didn't notice the name inversion either..? ^^

And how did you test, with two local accounts, maybe..?

A couple of weeks ago, I was looking into XF's trophy system, and tried to think of something for Wedge too, that would look a bit like it, but also be an indicator of someone's implication on a forum... So, I started devising (additive) points attributed by post (1), thought (0.5), per direct post/thought reply (since we have this in the database) (0.5), likes (depending on what it being liked, I couldn't make up my mind), topic (I think I settled on 0.2 per reply to it), but then I decided awarding points to replies might encourage trolling. Anyway, I couldn't settle on other things like points awarded for gallery albums and items, topic and profile views (minus bot visits), and more place-specific areas like uploading a plugin or theme here, or being marked as the one who successfully replied to a topic[1], so I just skipped to something else that needed my attention, so it's funny to see a discussion about something similar, but I don't really think it can be done, without at least giving the admin the ability to change the attributable points per item, and that's where it becomes complicated I guess. Ultimately, I wanted to see if we couldn't replace post-based groups with points-based groups, that is, awarding shy people for still being part of the community. But then, what prevents you from just Liking every single post in the forum..? A ban threat, maybe....? :lol:

Anyway, that's where I was at that point, and I couldn't decide, so I think I added it somewhere in my to-do list, and you know the story about my to-do list... It grows about 5 times faster than it shrinks, so it's never ending.

1.

That one is actually interesting; I forgot to mention that earlier, sorry. I mean, when I click "Mark as solved", it always says I marked it as solved, but I'd like to be able to mark someone else as the solver, so maybe we should have an "Accept answer" option per-post in solvable topics, so that we can properly 'thank' the one who actually solve your problem... Hey, why not..?

rev 2153
(8 files, 7kb)

! Got rid of a long-standing bug where, with Pretty URLs enabled, a name would occasionally drop out of the who's online list... Well, technically it's impossible to fix without being to reproduce, so I just added a fail-safe, and for the rest... Does it really matter? It happened once every six months, or something -- bot visits included. (Who.php)

* Restored personal_text modification to the profile area. Originally, I removed it to use thoughts instead, but since I decided to make it opt-in through the 'Posterity' feature, I might as well allow you to change it. And I might as well change my mind later. But I think once I've got privacy boxes set on this, it'll suddenly turn out to be all right to use it along with usertitle. Or something. Still, I think we really need to add some description of Personal Text and Personal Title below the options, because it can be confusing. I know it was to me, back in 2005 or something... (Profile-Modify.php)

* Translation. (ManageSettings.french.php, Notifications.french.php)

! Typos, including one in a variable name... 'Tis the season. ;) (ManageSettings.english.php, Notifications.english.php)

! Commenazi -- mostly a typo on the word 'readability', poetic irony. (Class-Notification.php)

* Vanity restyling of the language area search box. Don't bother. (ManageLanguages.template.php)

@ Note for Pete: feel free to revert the Who fix, if you're in a mood to spend a day trying to reproduce it, or something...

Also, Godboko, when you hit 'Like' on Pete's post above, it generated an error in the log. A few others triggered one too, but I wanted to ask if you could unlike, then like it again? (And possibly also like this post, just for my tests...)

I'm trying to determine if the error is due to the upgrade process hiccups from yesterday, or an actual bug in the current code base; thanks!

Crap... Bug is still there. Icari just tried liking my post, and it triggered the error.
Anything in your page when you liked, Icari..?

Bed time for me, unfortunately...

rev 2149
(2 files, 1kb)

! I actually swapped parameters when calling cache_prepare_key, which is the reason why admins were getting 'undefined s' errors in the log. A big oops. I take it that everyone trusts my code so much, they don't review it, right..? I should feel honored :P (Subs-Cache.php)

! Fixed typo from Dragooon's original notifications contribution, which made periodical e-mails fail entirely, as the DB table couldn't be found. (Notifications.php)

rev 2148 -- only a partial fix, as I have more errors to look into, but apparently limited to me, so I'm not in a hurry, ah ah...
(2 files, 1kb)

! Fixed a missing 'return' in the last patch, causing a cascade of errors in notifications. (Class-Notification.php)

! I also have my share of untested code, though: a missing $st variable in the latest Subs-Cache refactoring. Uh oh. Now that fix looks ugly... (Subs-Cache.php)

rev 2147 -- all of my current committable work -- and Dragooon's.
(5 files, 3kb)

* Committing a few changes to the structure of the contact list tables. They still aren't in use, but I wanted to have them in, just so Pete can protest/revert the changes, in case he finds them to be ineffective. (I'm never too sure about my work on MySQL performance, he's my god when it comes to that.) The idea is that list IDs should be linked to the owner ID, so that they don't get a list URL like action=profile;sa=contacts;in=12345, or something like that, but a shorter number instead, yeah, that totally deserves 4 lines of description in this commit, eh..? (install.sql)

* Applied Dragooon's patch that promotes my avatar code hack to a more generic status, yay again. (Class-Notifier.php)

* Applied Dragooon's patch that promotes my member_from code hack to a more gen... "Hey, haven't I done you before?" (Wowbagger, Class-Notification.php, Notifications.php, install.sql)

@ Fixed patch's cache flushing code, to use null instead of array(), as per Pete's suggestion, and use the proper TTL (86400), as per my own non-suggestion, but whatyagonnado. (Class-Notification.php)

! Looks like it's possible for a message to be emptied entirely by parse_bbc, as evidenced by an error in my log some time ago, so I'm adding a fail-safe that should cost no extra cycle. (Subs-BBC.php)