Wedge

Do all of the remaining topics in the OP need to be addressed?

Also, could someone look through all of the recent (i.e. 2014) topics in this board, and bump those that seem to require my attention? For instance, anything that is just a 'quick fix' on my side would be nice. It's not that I'm lazy -- I just don't have time to work on big thingies. I wasted a few days working on an extension of the Like system that I ended up ditching (for now?), so I'm a bit wary of doing that again.

Had a quick look at the SMF codebase, and it's doing the same.

So, basically, one would have to actually store the latest post for each board into a new fields in the boards table, then on the board index, retrieve the most recent post ID from all of these pertaining to boards you can read, and then it works... Except if the last post belongs to a topic with a privacy level you don't have clearance for, of course. In which case, back to square one.

Seems too weak to me...

Alternatively, just have an extra query requesting the last id_msg altogether, with a {query_see_topic} restriction, and then we're done.
It's an extra query, yeah... But it should be very fast.

I'm not even sure whether it's the SMF behavior or not...

Can anyone confirm?

Archived Fixes is a sub-board to Bug Reports, and isn't "requested" by the board index because of its position, and thus the last post date isn't calculated for it -- and not taken into account in the stats area. :-/

[Commit revision c64ce87]
Author: Nao
Date: Sat, 18 Oct 2014 20:19:53 +0200
Stats: 1 file changed; +1 (insertion), -1 (deletion)

• Add message ID to the post array, for plugins I guess. (PrintPage.php)

---

[Commit revision ae18f6c]
Author: Nao
Date: Sat, 18 Oct 2014 20:26:46 +0200
Stats: 1 file changed; +1 (insertion), -1 (deletion)

• I broke custom fields in the member list back in March... (Memberlist.php)

I'd be willing to help but only if they promise never to release any intrusive incentives such as a full page ad or an alert our whatever. A small banner at the top is okay. Seriously I tend to leave forums that have these splash screens asking me to install Tapatalk before I can even view a post... They're making money off this, not admins or users!

But it's a plugin..?

So... The feature I've been working on for the last couple of weeks (not that much work really, but I've been busy IRL as you all know) is working on my side, but I need feedback before I can commit it.

Basically, Wedge now allows webmasters to have more options than a 'Like' button[1]... Ideally (not now), I'll even let post authors decide what kinds of buttons are allowed on their post (e.g. if you're posting about someone's death, it would be wise to only keep a "Sad" button, so that no troll can press "Like" or something...)

Now this is where I need you guys... I've "simply" been reusing smileys for options, but I don't know if I should limit myself to smileys (honestly I think I will, because it means the code to add more buttons is already there), and WHICH ones I should have by default.

Here's the current list...

like ^_^
funny :lol:
love 8-)
what :^^;:
unsure :unsure:
meh -_-
sad :sob:
thanks :thanks:

Some of these are only in the 'Cyna' smiley set, which is probably not ever going to be added to Wedge, so I'll have to change them, probably :unsure: would become :-/, for instance.

I need to know if any of these choices are superfluous, if I'm missing anything important (should I have choices for "I agree"/"I disagree", for instance, or are the smileys enough?), and I don't know if they should be stored (in the database) as smiley codes (meaning they automatically adapt to the current smiley set), or image URLs. Currently, I'm using the smiley codes...

1.	Amusingly, I wrote this feature as something "original" for forum software, until I realized this week that a XenForo forum I'm lurking on has this as well... Not sure if it's as a mod or core, though.