square_eyes

Thanks!

Same issue for me

And I concede, that my issues above may not be related to the plugin. However it happened almost immediately after I installed it. Based on my past experience it’s better to report it.

I would have said third party, but that’s the plugin. The attacker would be a fourth party. That’s all.

My last chat plugin brought me all sorts of grief with XSS attacks. I’d love the developer to weigh in here with his opinion. It’s a great plugin, but not if it exposes my site.

Seemed I was on the receiving end of a brute fore attack last night

From my host…

“I have reviewed logged data on the server and found that your site was being hit quite a bit with WordPress login requests from 213.158.82.62 today:

[root@myhosthere /my/root]# awk ‘My IP Address Here/ {print $7}’ /usr/local/apache/domlogs/user/mysite.com | sort | uniq -c | sort -rn | head
2217 /wp-login.php

This seemed to cause some issues with the account hitting some of the resource limits we have on our shared servers.”

Wordfence found the following new issues on “”.

Alert generated at Tuesday 25th of February 2014 at 10:39:37 AM

Warnings:

* Modified plugin file: wp-content/plugins/quick-flag/database/ip2country.db
* Modified plugin file: wp-content/plugins/quick-flag/database/ip2country.version

Hi alysko, can you give us some context? Was this a 4th party XSS injection? Who detected it? Or is this in the source code?

FYI I’m a user, not the developer.

Also, if I was to make a script to run on the database it would probably be further automated. Maybe by python, to look at the duration and if it’s over a certain amount calculate and set the correct value. I had planned this, but the issue is only cosmetic. So it’s not high on the list of priorities.

I don’t mind the 0.00 I have gotten used to it. If I can hide it on the web that’s fine for me. It shouldn’t affect your plugin because the players should be able to trigger the song change. Also I set manual fade, start, stop settings a lot because my DJs don’t always make their intro/outro graceful.

Long files show as 0.00 in your app. I have so many I would just hide track length if I had the option. Here is some more info on the bug.

https://support.spacialaudio.com/forums/viewtopic.php?f=20&t=35518

It’s cosmetic as SAM handles the file correctly and the proper duration is displayed when it’s playing. The SAM PHP web pages don’t seem to have an issue handling it.

Note this is in 4.9.x (which many people still use). I have no idea if it was fixed in later versions.

Ah yes I noticed that after writing:) Can’t wait for dynamic updates. I have some aspects of my website cached but I assume it doesn’t have this yet as I had to refresh to see a song change.

Nice work! Perhaps maybe the comments tag.

While you’re at it check boxes for all of the above would be useful for people not wanting different info.

As an example, most music on my station is pre-record 2hr mixes. SAM has a bug that means it cant display track length after about two hours. So lot’s of my track lengths are 0.00.

I don’t know how hard that would be to implement though.

This is a great plugin. Happy to help out with testing etc.

How odd. I don’t have a description tab on the plugin. I have a description tab on the WordPress plugin page but I don’t see any shortcodes.

Like I said. Crazy pills:)

I’ll continue the feature request thread here:)

Excellent plugin by the way!

:: +1 Album art. Here’s another example https://tinyurl.com/pud9wla
:: Nowplaying widget, with artwork & auto update via Ajax. The existing PHP web pages calculate update time by the database (start time + track duration)
:: Song info popup