At one time I kept all of my licenses up to date, I did this for years, but after years of extremely poor support (slow, not incompetent), and lack of updates, I found that I was wasting money keeping my licenses up to date. I have to wonder why others see no value in keeping their licenses up to date. Maybe IPB should focus on the reasons why customers see no value in keeping their licenses up to date. I like the idea of paying for the "suite" all at once though, would make it much easier to keep track of as I have far too many licenses already, and it's a PITA to keep track of what licenses are up to date and which are expired.
I currently have the tags hook enabled, but it's quickly growing and will soon contain too many tags to keep it enabled. It would be nice if the admin could limit the number of tags to show in the hook and then arrange it based on the most popular from that limit.
I think IPS might want to fix up their current COPPA system as it leaves site owners open to litigation. It would also be nice to be able to enter your own message into the COPPA field if you wanted to filter and add your own message instead of the COPPA form.
This is getting stupid, what ever happened to parent being responsible for their own children? Shouldn't the parents be the ones who get into trouble when their kids lie and join a site? This world is upside down.
For any forum owner who has a site that may be considered in any way directed at children, even if it's not, the current COPPA verification setup can leave the site owner vulnerable.
From the FTC Website: http://www.ftc.gov/p.../coppafaqs.shtm
39. Can I block children under 13 from my general audience website?
Blocking children under 13 from participating in a general audience, or teen-directed, website does not violate COPPA. However, as described in Question 38, above, should you choose to block children under 13, it is important that you design your age collection input screens in a manner that does not encourage children to provide a false age in order to gain access to your site. If you take reasonable measures to screen for age, then you are not responsible if a child misstates his or her age. For example: Ask age information in a neutral manner at the point where you invite visitors to provide personal information or to create their log-in user ID. In designing a neutral age-screening mechanism, you might consider:
Making sure the data entry point allows users to enter their age accurately. An example of a neutral age-screen would be a system that allows a user to freely enter month, day, and year of birth. A site that includes a drop-down menu that only permits users to enter birth years making them 13 or older, would not be considered a neutral age-screening mechanism since children cannot enter their correct age on that site.
Not encouraging children to falsify their age information, for example, by stating that visitors under 13 cannot participate on your website or should ask their parents before participating. In addition, a site that does not ask for neutral date of birth information but rather simply includes a check box stating “I am over 12 years old” would not be considered a neutral age-screening mechanism.
In addition, we recommend using a temporary or a permanent cookie to prevent children from back-buttoning to enter a different age.
Note, however, that if you ask participants to enter age information, and then you fail to either screen out or obtain parental consent from those participants who indicate that they are under 13, you may be liable for violating COPPA and the Rule.
Yeah, my members had a fit when I upgraded my forums to 3, so I can understand your apprehension, but I think 3.2 offers so much more that I can't resist the urge to upgrade all my forums. Maybe you should set up a test site for them to check out before making the decision and see their reaction?