Yaga 2.1.0

Bleistivt · February 2021

Vanilla 3.3 or higher is required to use this plugin.

You can download a zipped version here:

https://vanillaskins.com/plugins.html#yaga

...or visit the github repository here:

https://github.com/bleistivt/yaga

For more info about this YAGA fork, read https://open.vanillaforums.com/discussion/37990

Release Notes

Reaction customization

Reactions can now be fully customized. You can use your own icons, SVG images or even Emoji!

Note that the .ReactSprite class has been changed to .YagaReactSprite as there is a naming clash with the default theme (keystone).

If you have been using the old reaction sprites without any kind of customization through CSS, you can ignore this change.

Otherwise, you will have to replace .ReactSprite with .YagaReactSprite in your custom stylesheet.

"Best Of..." performance

The performance and memory usage of the "best of" section has been drastically improved.

This also includes the profile/reactions pages. These are now fully paginated (not just "previous" & "next").

If you are upgrading you will have to run dba/counts (tick "Recalculate Reaction.Latest") once.

Next release

APIv2 integration is planned for the next update.

Once Vanilla 4.0 is released, I will also look into cross-supporting the bundled Reactions plugin (possibly supporting converting between both).

phreak · February 2021

Yes, more features! Great work @Bleistivt !

meetdilip · February 2021

Great Share :)

At some point, please consider adding notifications into this plugin 👍️

Bleistivt · February 2021

@meetdilip it already notifies the user of badges received. Notifications for reactions would only be feasible for very small forums, otherwise, users would be quickly overwhelmed by the amount notifications.

Enabling this selectively for specific reactions (like promote) however would probably work. Please add your suggestion as an issue here, so I can consider it: https://github.com/bleistivt/yaga/issues

meetdilip · February 2021

Thanks for considering @Bleistivt

https://github.com/bleistivt/yaga/issues/30

I have added a request in your repo.

testing3 · February 2021

I tried to enable it but getting this error- Table 'GDN_YagaReaction' already exists.

I was using the original YAGA application, so I first disabled that and then removed the YAGA application folder, and then uploaded your plugin, but when I try to enable it, I get this error message- "Table 'GDN_YagaReaction' already exists".

And notifications for the reactions would be awesome! But obviously, the forum members should have a choice to disable/control it from their profile.

Kaspar · February 2021

https://open.vanillaforums.com/discussion/comment/262475#Comment_262475

Did you clear cache?

testing3 · February 2021

Yes, I cleared the cache multi times, and still not able to enable it.

Bleistivt · February 2021

@testing3 Has the old application been enabled at some point after the plugin has been active? This is the only way both tables could exist in your database (in which case the plugin can't know wether to convert the name or not).

I'm thinking about adding a check for this. Still, there is no way to know, which one the user wants to keep, so manual work is required.

Please check your database for the GDN_Reaction (uppercase!) and GDN_YagaReaction tables. If both are present, delete the one which is empty. The same applies for all other GDN_Yaga*-tables.

testing3 · February 2021

Hi @Bleistivt,

I'm testing the new 4.0 version on a test server, and I had completely removed the old YAGA application before installing your plugin, but I didn't remove the new Reactions plugin, I just disabled it, could it be the cause of the issue?

I just checked the database and found 3 tables-

GDN_YagaReaction (Not Empty)

GDN_reaction (Empty)

GDN_Reaction (Not Empty)

Bleistivt · February 2021

@testing3 It is compatible with the new Reactions plugin (in fact that is the reason for the fork). So this should not be a problem.

What about GDN_YagaReaction vs GDN_Reaction, how many entries are in each table?

testing3 · February 2021

@Bleistivt the GDN_YagaReaction has 56 entries, and the GDN_Reaction has 1,731 entries, the test forum is a clone of our live forum that I have updated to the 4.0 version for testing.

The main forum is located in a subfolder (domain.com/forum), and the cloned test forum is installed on a subdomain (forum.domain.com) where I'm testing your plugin and the new Vanilla 4.0.

Bleistivt · February 2021

@testing3 Just to make sure: The database is also a cloned, so they are not accessing both the same database, right?

If GDN_YagaReaction only has few reactions (and you are on a test installation), you may as well delete it (along with the other Yaga*-tables) and re-enable the plugin to try the automatic conversion again.

testing3 · February 2021

@Bleistivt Yes, the database is also cloned.

And here are the other Yaga tables, should I delete these?

GDN_YagaAction- 7 entries.

GDN_YagaBadge- 47 entries.

GDN_YagaBadgeAward- 5 entries.

GDN_YagaRank- 7 entries.

GDN_YagaReaction- 56 entries.

Bleistivt · February 2021

@testing3 That depends - how do they compare to their counterparts without "Yaga"?

testing3 · February 2021

@Bleistivt I deleted them one by one until the plugin stopped asking to do so 😉 now it's working like a charm.

Love the option to add custom icons from the backend.

Thank you so much for the hard work!

And I would love to buy if there would be a paid PRO version with extra bells and whistles, like notifications for reactions, different icon sets for different occasions like Christmas, Valentine's day, etc.