sadams101

I am using the latest version of IPB, and have my board set to allow guests to report posts. What appears to be spambots have been submitting spam via guest reports, and they have been blocked in my ban settings with 198.144.159.* The problem is that I am still getting reports from IP addresses within this subnet that should be blocked. How are they able to bypass the ban setting block on them, and still submit spam using the report post feature? I believe there may be a bug in your system that allows this.

Thank you both. Any reason why neither of these show up when I search the ACP area, for example using " IndexNow" or "Google Tag" or "GoogleTag"?

I have two questions, and can't find anything in my ACP about these settings. 1) What is googletag, and how do I enable it? 2) I understand what IndexNow is, and have upgraded to 4.6.11, but see nothing in my ACP for settings for IndexNow. Is this enabled automatically?

Ok, I did go to the end of each forum, and in 4 found and deleted what looked like corrupted posts...3 of which were dated 1969. This did fix the issue with your plugin throwing the errors, so thank you. However, the only question remaining in my mind is, why would your plugin throw this error, but not the default IPB skin?

Thank you for your reply. When you say that I might recognize corrupted forum posts by dating my forum back to 1970, do you mean changing my server time to this, which might cause many other issues, or do you mean just the time in the ACP for IPB? I do have a test site, and could do this to figure it out. Also, after making the time change, how would this help to find those corrupted posts? I know this is far beyond any support you might offer for this plugin, so thank you in advance for any help!

But if there are no PHP errors when running it, then it is compatible. PHP writes new versions to be backwards compatible, and in some instances they remove deprecated code that is no longer compatible--this causes errors and things to break if you still use such code. I guess what I'm saying is that if nothing breaks, and there are no errors, then what would be the concern with running it now? PS - There were tons of issues for me running PHP 8.0, and I had to upgrade many custom plugins and apps. Besides the cache issue, which turned out to be a problem with my Redis installation on PHP 8.1, I have not seen any errors at all when running PHP 8.1.

Thank you. I assume that others are running PHP 8.1 at this point. My plan is to try it again and keep an eye on my error logs to make sure all works ok.

The source of my issue was that I did not have Redis properly installed on PHP 8.1. I took care of this issue, so I'm curious to run PHP 8.1. Are there any known issues when running PHP 8.1 with the latest version of IPB? Can you please explain what you mean here by "not yet fully supported"?

Any reason you're not currently doing that?

So I logged out of ACP, then back in, and the error is gone now. When will you support PHP 8.1? It is faster than 8.0 or 7.4.

It was enabled when I switched yesterday to 8.1, then saw the errors today. After reverting back to PHP 8.0.15 I am still seeing this error...I cleared the ACP cache, not sure why: Cache Not Working Caching is not working correctly. Review your caching method configuration and adjust the settings as needed.

After upgrading to PHP 8.1 I am suddenly getting the errors below. My directories are 755 permissions, and haven't changed. I use Redis Caching Any ideas? Data Storage Not Working Data Storage is not working correctly. Review your data storage configuration and adjust the settings as needed to improve speed and performance of your community. Cache Not Working Caching is not working correctly. Review your caching method configuration and adjust the settings as needed.

There seems to be an issue with Enhanced Forum Views 1.4.0 after I updated to PHP 8.0.15. I am seeing a strange error that happens when you go to the last page in a form category: https://www.celiac.com/forums/forum/5-coping-with-celiac-disease/page/642/ But if you go to the 2nd to last page, or any other page in the category, you don't get it: https://www.celiac.com/forums/forum/5-coping-with-celiac-disease/page/641/ I have tested this out, and if I disable Enhanced Forum Views Disabled1.4.0, this error goes away, and the last page in my category works, and does not throw an error. Here is the error info: The log entry was triggered by a guest (Guests) 1 hour ago The URL of page the error occurred on was https://www.celiac.com/forums/forum/5-coping-with-celiac-disease/page/642/ BACKTRACE:

In the end it may not matter, as I do know that there is a canonical link to my base URL from the /index.php version, however, to be SEO technically correct there really should be a 301 redirect as well. So far I've not found a way to make this work that doesn't create issues.

I spoke to soon, and edited my response...for some reason it isn't redirecting, and stays on the /index.php

Unfortunately it doesn't do the redirect.

I am wondering why this simple mod rewrite to eliminate a duplicate home page is causing errors: # Remove index.php from root URL RewriteCond %{THE_REQUEST} ^[A-Z]{3,9}\ /index\.(php|html) [NC] RewriteRule ^index\.php$ https://www.mysite.com/ [R=301,L]

Around the time that IPB started its tags, I decided to not allow bots to index them. My reasoning was that having bots hitting hundreds, perhaps thousands, of searches per minute would slow things down on my site, and thus be bad for SEO, given just how much Google now weighs site speed into their algorithm for search results. Additionally, given that Google has a "crawl budget" for each site, my thought was that I'd rather have bots focus on indexing the new content, rather than indexing what are simply search results on my site. My decision could be wrong, and perhaps the good SEO from bots clicking on my tags and indexing them might outweigh the bad. My hope is to hear from others about how they handle this issue.

Right...I think we all understand this. He's not been heard from since Jan 2021. Unfortunately I'm unable to wait until he's back here to update this application, as I need it updated for 4.6 and php 8. Some of you may be in the same boat. If anyone is interested in a version of this that is PHP 8 and IPB 4.6 compatible, please contact @DawPi

Sorry, I was able to update my version of this app to work with PHP 8.0, but unfortunately can't share this, as I don't have permission form newbie LAC.

Yes, I understand this, and my post was meant to reach out to others who are using this app.

I am checking here to see if anyone is using this app in PHP 8.0? I have tried, but this app is causing a server 500 error in PHP 8.0 when someone clicks on either the clubs or blogs link. Unfortunately I can't find anything that gets logged about this error in the server's php error logs, or in the ACP logs. I believe the Apache error it triggers must preclude a php error from getting logged. Has anyone else had this issue? Also, I am now working with a developer to try to get an update to this plugin, and at least fix this issue. I will post here my progress on it.

Hi Marc, I can assure you that the block was gone when I tried to connect yesterday. It's a simple .htaccess block to my test site, and when it was removed yesterday I was unable to access marketplace, and got that error. Today, after clearing various caches and removing the .htaccess block I was able to connect. Thanks for following up!

I am getting this error after restoring a database backup on my test site (wheat-free.com). I do not use any cloud services, and my firewall is not blocking you. What could cause this?

After more research, I realize this is coming from one of my custom plugins...sorry!