Thomas Hunziker
Thomas Hunziker
You could just have a table where you store the change. But then I'm not sure if it is that important. The purpose of the plugin is to get data...
> In my opinion, the more data you have, the better, even if you don't plan on using it right away. Google and Facebook for sure share this opinion. :smile:...
> Overnight we had some guy think he was being funny or something and send in totally bogus stats, like Joomla 1.0 running on PHP 6.4.0, which obviously would never...
You could do some ip checking to prevent the same guy sending data multiple times with different ids. Or limit it at least to a certain value or something. Validating...
Another verification could be that the server makes a 'callback' to the plugin, verifying the id and maybe a property somehow. This would make it a bit harder to fake...
Also run into this today. Using the official SDK kit is no option for me as it imho requires PHP 5.5 and my code has to run on PHP 5.3.10+....
Thanks! Didn't know that.
I think the issue is on this line: https://github.com/mediaelement/mediaelement-plugins/blob/5a854644445ffce95df2b40564e5da83c30dcedf/src/playlist/playlist.js#L84 Should be ``player.setSrc(player.playlist[++player.currentPlaylistItem].src);``
It's a known issue and apparently expected behavior by the dev. But not by the user. And it certainly doesn't mean it is the correct thing to do. Also, with...
> Not if the old URL was falsely 200, e.g. @Bakual 's example in the description. That's not a valid URL, current router return something valid which IS wrong! That...