mesteele101

In the last week or so I have been getting dozens of New users accounts that appear to be spambots. I have setup reCAPTCHA 2 and it appears they bounce right through it. Appears to be multiple machines infected because these accounts are coming from different email addresses and different IP addresses. About 8 out of 10 are actually getting validated. Is there a way to stop this?

I am having a rage of IP's coming in that I would like to block. How would I do this? The IP address resolves to: abts-north-dynamic-216.234.68.182.airtelbroadband.in The above is the same except the IP changes, and different gmail accounts are used to register. Thanks...

Is this good on 4.1.19.4 ?

OK, so I don't have pages I Didn't see anything in the description that it required Pages?

Ok, so how do you add an RSS feed to the Ticker? Everything I enter prints out in the ticker.

Will this work on 4.1.19.4?

Can you post a snapshot what it looks like with the user picture applied in wide screen, and what it looks like in mobile mode with the user picture?

I was wondering if there was a way to reset the default theme back to stock. Removing all modifications?

IPB 4.1.18.2: Causes the custom items in Profile Information not to display on new entries. Users before updating to 4.1.18.2 will display correctly in Profile Information. New users Profile Information entered in does not show for accounts created after updating to 4.1.18.2

Have you tried Feed Widget... I had multiple problems with the (NB40) RSS Sidebar Widget.

Go change your upload limit in PHP.

This is interesting. I would be very interested in knowing a couple of things. 1) Is there a way to globally force groups to adhere to the two step verification? 2) Is there a way to incorporate this into new user registration (IE: instead of email they are required to get a verification and type in the code to complete registration)?

Just updated to 4.1.13.2 and the database problem is still there. Not sure if the database problem IPS fixed was related to this?

After updating to 2.1.0 I went into support and went into Something isn't working to fix something else and I'm getting the below and IPB doesn't fix it. The above could have happed prior to updating to 2.1.0 as it has been months since I've used the support option to check things. I've tried it several times and it's not getting repaired.