VaBeach_Guy

Thanks, whatever it was, it seems to have resolved itself overnight.

It was just brought to my attention that images can't be posted due to the following error: Any ideas what's going on with that and how to correct the issue?

I did read it all and went into that area and didn't find the settings. Why didn't I find them? Because the area that I needed to go into was right in front of me and I didn't notice it lol. After looking 3 or 4 times, I finally noticed it. It did remove the permission for viewing profiles, but I'll have to dig into it deeper (as has been said), to do what I'd like to do. It's not a HUGE problem, just an annoyance. So if I can't do what I'd like to do, it's not a big deal. But I do wish it was a set option.

That was my initial thought when I began looking for a solution, and I know that years ago we could restrict guests from seeing profiles, but I can't find the setting for that anywhere, now. So I assume that it was done away with, unless I'm just missing it.

Is there a way to prevent avatar/profile images from displaying for guests? I ask because there's a few avatars on my site that are of bikini clad women, nothing containing nudity or anything like that, but the Google AdSense system thinks they're 'porn' and I constantly get 'nasty grams' from them telling me that ad serving to particular pages is disabled due to sexual content. I dispute it for a manual review and they reverse the action. Not a real big deal, but annoying. If I can prevent AdSense from seeing the images, problem solved. But I'm not seeing any settings that might accomplish this. Is there a way to do this?

Apparently, either I or Adsense enabled auto ads in April, because it's been running for that long and I've either forgotten or just didn't know. But, it hasn't been an issue for all this time. Maybe it was an issue before my upgrade (which hadn't been done since 2020), but it's not an issue now.

I can't swear that it was after my upgrade a few months ago or before. I'll run a test and see what happens.

In the past when I tried auto ads, it displayed for everyone even thought I had members excluded. I want to exclude members for a couple of reasons. One, as a benefit of membership, they see no ads. Two, members tend to want to 'help' the board earn money by click, click, clicking as many ads as possible, and that will cause Google to eliminate our ability to have ads.

Do auto ads actually increase revenue? In other words, is it worth going through the hassle of trying to exclude member groups?

So far, so good. Since switching, there's been zero fake registrations whereas before that, there were dozens (or more) per day.

We aren't getting spam posts, but we are getting A LOT of registrations that, if approved, would lead to spam posts. We're using Invisible reCAPTCHA, would one of the other options be better than that one?

Any updates on this issue?

I got it worked out. The iframe code that I used and that works for me is: <iframe allowfullscreen="" frameborder="0" height="270" src="VIDEO ID GOES HERE&embed_domain=YOUR DOMAIN GOES HERE" width="480"></iframe><br />

When you do a live stream or a video premiere on YouTube, a live chat is also included for viewers to interact in real time. There's a way (apparently), to embed this in a website, but so far I haven't been able to figure out how to get it to work in a thread. The code is pasted below (with generic YouTube and URL info). Does anyone know how to make this work in a thread? <iframe width=”350px” height=”500px” src=”https://www.youtube.com/live_chat?v=yourvideoid&embed_domain=yourdomainnamegoeshere.com” ></iframe>

The one that wouldn't unarchive (on its own), is ok now. The other thread is fully visible, but the 'most recent post', only covers up to the first 100 pages of the thread (over 1500 pages). All of the posts are there, and if you click on 'January 1' to take you to the most recent post, it actually takes you to the real last post in the thread. So it's just that 'January 1' date and the member who posted it, that's not right (Feb 14 and a different member are correct). Might that self-correct or is it just a little glitch?