You've got karma!
Several people still want to use the karma feature, which was removed from 2.1. Rather than leave those users in the dark (and I don't think they'd like to use the Likes feature (pun unintended), I decided to rebuild it as a mod.
Screenshots attached below.
This mod does not edit any files, partly due to the use of custom profile fields, but also because SMF 2.1 introduces hundreds of new hooks (haven't counted).
Open sourced under the MIT license. Link to project on GitHub: https://github.com/live627/smf-karma
~~~
Win a free cookie (not provided by me) if you can guess the reference in the title!!
Screenshots attached below.
This mod does not edit any files, partly due to the use of custom profile fields, but also because SMF 2.1 introduces hundreds of new hooks (haven't counted).
Open sourced under the MIT license. Link to project on GitHub: https://github.com/live627/smf-karma
~~~
Win a free cookie (not provided by me) if you can guess the reference in the title!!
-.-
It's not SPAM
Or something like that
First of all we added option NOT to delete karma data from upgrade process so you are safe to upgrade, now question to OP, will your modification converts current data into its own? or just use the existing data?
Thanks for the modification
Next time could it be a good idea to make the topic global or something like that? At least a lot more people would vote
Breaking it out of the core has consequences for them. More importantly, it has all kinds of other consequences. It means you absolutely ensure your modding functionality is up to scratch. It has performance consequences. And probably most compelling of all, you can add to its functionality separately from the main core, meaning you can turn around updates to it separately of the forum - adding in functionality that users want without waiting for another major release of SMF.
On the other hand it also encourages doing things previously unheard of. Right now the calendar depends on SMF's posting routine; adding a new calendar entry with a topic ties them together and if so doing, it means every time you view a topic you end up looking for whether or not there's a related calendar entry. This is a non-trivial performance problem.
If you were to decouple calendar events from main posting, you would avoid that performance hit while still being able to do what you want to do with calendar stuff.
and, if 33 people voted, then that's 33 people who cared enough to vote...
As for global topics... nope. Those who care can view the development threads and comment - those who don't care enough will take what we make and go from there.
As for the calendar... as arantor says... there are VERY good reasons for decoupling it
2.1 has not removed the calendar. It is still a core feature.
The point being made was that it has been fiercely debated both ways to remove it in a future version and make it a plugin - and at the same time make the plugin system much more reliable so it would be much saner to actually make it a plugin if it were actually done (and it would be available with 3.0 for that reason).
The calendar is a strange beast. It is used by a tiny percentage of the SMF userbase... but those that do, make heavy use of it. It is a maintenance nightmare, it has a number of bugs in it, it is also a performance hog (more than it needs to be) and a plugin with proper importer would make a lot of sense for various reasons.