It should be using the same API key as ‘normal’ twitter widget, if twitter widget works, then twitter metro should work as well.
I don’t think we had any problems with this module, perhaps try to verify all modules, make sure twitter is correctly configured and try again.
If the CMS is in debugging / test mode, it generate produce logs about such error - make sure the duration back on Log page isn’t too low or that you don’t use PAGE/Function filters that would not match the error you’re looking for.
I’m not sure why would it have issues rendering the template - is that using one of the pre-defined templates (is the issue occurring on each one of them?) or did you modify the template?
I’m not sure what the problem was.
Performing the installation verification of the modules did not work.
I have deleted in the modules table the register for the module Twitter and Metro Twitter, in this way both appeared again for installation.
Performing this procedure worked.
What motivated the bug I do not know, I’m just using the CMS without any customization 1.8.2 with upgrade from 1.7.9
Interesting, presumably you did the same thing after upgrade, as from memory twitter/twitter metro modules are not installed by default - although you probably had the twitter module installed in 1.7.9 so after upgrade you just installed the metro one, I wonder if that caused some sort of mismatch along the way.
It’s hard to say why it didn’t work / installed correctly, @dan any ideas based on Laercio’s log?
In any case I’m glad that re-installing those two modules solved the problem.
Perhaps the SQL upgrade step which inserts those two modules didn’t work correctly. I don’t think its a general issue as we’ve run lots of upgrades with success.
The modules table contains a class name, which is used to load the Module handling class - it seems that could not be found Xibo\Widget\Twitter.