JohnD

DCP Community Administrator
  • Content Count

    3,500
  • Joined

Community Reputation

0 Neutral

1 Follower

About JohnD

  • Rank
    DCP Fanatic
  • Birthday 06/05/1955

Contact Methods

  • Website URL
    http://www.drumcorpsplanet.com
  • ICQ
    0

Profile Information

  • Gender
    Male
  • Location
    "O.C." & Cyberspace

Recent Profile Visitors

4,832 profile views
  1. I do not use Bitdefender, so haven't see this message ... and your note doesn't provide details of the message you've been receiving. I'll need more information if you'd like me to investigate further. I'll also need a screen capture of the page you receive it on - specifically the top half of the page that includes the advertisements. Most often these sorts of warnings are the result of Google Adsense adverts that include offending content. Unfortunately, we don't have any control over these adverts, other than to block the advertiser in our Google Adsense feed. I can assure you
  2. I am not able to replicate what you describe - testing with Chrome desktop and Chrome & Safari on iPhone. A single click is all it takes to open a thread either by an icon (unread 'dot' or 'star'), the thread title, or other associated links. All of these links appear to be 'regular' <a> tags, which provide the hyperlink. In other words, there should be no issue of Javascript not executing properly for these operations. We have very little control over how the content is actually delivered, without digging into the source of the templates provided by Invision - which I'm not
  3. I've been trying to keep-up with the changes being made by Invision, so we don't get too far out of sync with the current version. This helps keep the site/database safe, as well as your own devices. The 'theme' (color scheme, fonts, etc) is also the 'default' created by Invision - which I also try to keep in-sync with the 'default'. Updates used to take up to a full day when I had to manage multiple custom 'themes' and other hacks we had made to the system. I just don't have the time to dedicate to those customizations any longer - so we're going with the plain vanilla version. P
  4. DCP Members and fellow drum corps fans, As you may know, I don't comment too often on this forum - believing that my primary job here is to provide the 'soapbox' on which our members stand. I have had long-term relationships (20 years+) within the activity as a board member, advisor, donor, and fan ... so I have been careful to reserve my opinions mostly for the board room and my colleagues there, lest they be interpreted as a position of the organizations I am involved with or a reflection on them. That said, I feel that the recent announcement by DCI and those that will be forthcom
  5. DCP Members and fellow drum corps fans, As you may know, I don't comment too often on this forum - believing that my primary job here is to provide the 'soapbox' on which our members stand. I have had long-term relationships (20 years+) within the activity as a board member, advisor, donor, and fan ... so I have been careful to reserve my opinions mostly for the board room and my colleagues there, lest they be interpreted as a position of the organizations I am involved with or a reflection on them. That said, I feel that the recent announcement by DCI and those that will be forthcom
  6. I have just applied the most recent update to the system, now that things have settled down a bit. Let's see if the update resolves the issues you've experienced .... otherwise, I'll have to report the issue. Thanks -john
  7. OH - my bad. I mis-read your description, Randy. That's straight IPB code, so we'll have to see if they find a fix along the way. There is an update pending, which I'll apply after the pandemonium quiets down a bit in the coming week. -john
  8. Dang it Flo - would you PLEASE stop dropping during a corps performance. (500 Error on Apple TV)
  9. Randy - sorry for the delay in responding. Its been one of THOSE weeks, as you might expect. I suspect the issue is related to the fact that we use an API into the forum database from the DrumScorps app to get the forum content. I'm guessing that the 'filters' for ignored users (and probably others) is implemented in the IPB user interface, which the API probably doesn't consider. I'm not sure if we can add a filter to the request we pass the API to exclude those posts from the result returned to us. It will take a bit of research to confirm and resolve, which we can add to our lis
  10. My apologies for the delay in responding. There are a number of reasons for a 403 error - but it almost always indicates that what you're trying to send violates one of our security protocols on the server. I don't have enough information to further diagnose and with this week's traffic, it will be nearly impossible to locate the issue in the logs, unless you can provide source IP addresses and more detailed information. -john
  11. It *may* have had to do with the length of their drive afterwards and the lateness of their getting on the field. Leaving the show site a couple of hours later than planned can have a real impact on the corps looking at a long overnight drive.
  12. This was actually addressed in the previous post (Here) and the URL referenced was added to the BLOCK list for Google Adsense. If you’re still seeing the bogus link/pop up, clearing your cookies and browser cache may help. -john
  13. I haven't seen the redirect/message - but one of our admins has and provided a couple of clues. I've reviewed our system and data and don't find evidence of our being compromised, so the most-likely source is a nasty Google Adsense advert ... which would also explain why some are receiving it and others don't. I've added the domain that was referenced in the clues we saw to the BLOCK list on Adsense (which takes a bit of time to be active). Hopefully that helps. As always, DO NOT click on pop-ups or pages that you are unfamiliar with. An Ad-Blocker or browser plugin can help in ke
  14. After receiving another report, I was finally able to gather enough information, replicate the issue, and find the source of the problem .... the one I was able to catch. Our servers employ several layers of security and one of the many layers was interpreting the 'embed video' as a cross-site scripting (XSS) attempt and returned the 403 error. It took a bit of digging, but I was able to locate the event in the log. I believe I have neutralized that particular rule (leaving the other 1,000+ in-place) and my testing indicates that the 'problem' is gone. Thanks for your patience.