That's an excellent question, in all honesty. We get reports every once in a while about the Like or Comment button showing up in places it shouldn't.. this occurs when 'other' extensions call the Content plugins, and we'll need to test and implement a method to ignore showing in the Newsflash module (as we agree it shouldn't either).
Let me look into this a bit more, and I'll let you know what we find.
Thanks, would be nice to be able to set it to be off because the newsflash module in the site that it's happening with is only 150px wide so it looks awful.
I've just had to reset my password and log in manually because Facebook is down. Never really thought how much of a problem that could cause for sites where people have logged in using their facebook account!
Let me start by saying that what I'm about to recommend is something we never recommend or suggest.. making a modification to something that's part of Joomla core. However, in this case, for now (and for a quicker answer), we must.
Basically, what's happening is the the mod_articles_news is calling the content plugins before the articles are rendered. There's actually a mechanism built into the content plugins that let our plugin 'know' where it's being called from (an article view, a module, etc). However, the mod_articles_news module is actually lying, in a way, by saying it's actually the article component. To fix this, our best answer is to simply comment out the line this is occuring on, so it doesn't call the content plugins at all.
If this makes no sense, no worries. I just need to explain the background. To fix, please edit the following file:
At line 92, you'll see the below line:
$results = $app->triggerEvent('onContentBeforeDisplay', array('com_content.article', &$item, &$params, 1));
Please comment this line out by putting a hash '#' sign at the beginning of it.
That should fix you right up, but it will prevent the content plugins from being called in that module, which may cause other issues. Please let us know if it does, and good luck!
Great! Glad to hear that got you going for now. We'll try to find a better solution that doesn't require a change to Joomla, but for now, just remember you made that change in case you upgrade Joomla and the problem comes back.