Randy Calvert

Have you tried disabling all of your third party modifications and testing with a default theme to make sure there is not a plugin/application causing a problem? Regarding the PHP error... that's happening because the script is trying to use more memory than your PHP.ini allows (which is 134MB). My guess is there is a 3rd party resource again that is triggering this. And regarding the ModSecurity issue... I would personally disable mod_security. It breaks more than it fixes. But again, that's between you and your host.

https://www.webpagetest.org/result/220924_AiDc9C_88B/1/details/ Webpagetest shows REALLY long times to download basic files. You're talking 8 seconds to download a static file. So that's not an IPB problem, but instead something either in your PHP setup or a lack of system resources. I would suggest working with your hosting provider on that.

Also… one thing to try… disable all 3rd party applications/plugins. See if the performance is still bad. It’s possible that a 3rd party tool is misbehaving and slowing things down.

Then I suggest finding a new host. This is not a software problem. The error is reporting the MySQL table is damaged and needs to be repaired. This is something we can’t help you with. You either need to fix it yourself or have your hosting provider do it.

Did it happen on the test site with ALL plugins disabled or just your prod site that has various third party resources? You’re literally going to be spinning your wheels and getting nowhere until you have this happen with no plugins. And from experience… ONE of your plugins is responsible. It’s going to be a matter of finding out which one it is. I know you don’t want to try disabling them, but you’re going to have to decide which is more problematic for you.

His last post was almost 2 years ago and his signature indicated he was in the hospital. It is unlikely he is going to be updating this soon unfortunately. (I pray he had a speedy recovery and is just stepping away from programming for a bit.)

By any chance do you have any posts scheduled for publishing in the future?

When you click on the magnifying glass, what is the actual full error and trace?

If you don't know what you're doing, I would highly suggest reaching out to your host for assistance. If you do something incorrectly, you could break your site to the point where you have to restore from backup. You're literally playing around with the "guts" of your site. With that said, there are tons of guides out there. Just hit up Google for "phpmyadmin repair table". You'll get results like: https://www.servercake.blog/how-to-optimize-and-repair-tables-using-phpmyadmin/

If the author does not have a valid license, it will be hard for them to test their code on the latest versions. So that is a good policy for IPS to have. Hopefully they are able to renew their license and continue offering the app. Otherwise, you might check if they are willing to let another active developer take over the app or something.

Is it October yet?! It's almost Halloween!!!!

No. It does not change the search index itself. Just want is interpreted as the results ranking.

When you switch to PHP8, make sure you run the compatibility checking script to make sure you have all of the required PHP modules installed. If you’re not running any plugins and running into issues, in many situations the new version of PHP is missing a required module.

You can comment out the lines I pasted above and it will keep email flowing for now with your site back online.

Why are you trying to install it in a sub folder at all? Just install it in the root. You’re asking for trouble and a rob of unsupported complexities otherwise.

@Jon Erickson... tried to install 1.0.14... when using PHP 7.4 or 8.0 (currently supported versions of PHP for IPB), it triggers an error that disables the full site and ACP with the following message: ErrorException: Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 8.1.0". You are running 8.0.20. (256) #0 [internal function]: IPS\IPS::errorHandler(256, 'Composer detect...', '/var/www/html/a...', 24) #1 /var/www/html/applications/awsses/sources/vendor/composer/platform_check.php(24): trigger_error('Composer detect...', 256) #2 /var/www/html/applications/awsses/sources/vendor/composer/autoload_real.php(25): require('/var/www/html/a...') #3 /var/www/html/applications/awsses/sources/vendor/autoload.php(7): ComposerAutoloaderInit56a710c1e4edbbc536d58cfc31cc8a09::getLoader() #4 /var/www/html/applications/awsses/Application.php(27): require_once('/var/www/html/a...') #5 /var/www/html/system/Application/Application.php(705): IPS\awsses\_Application->__construct() #6 /var/www/html/system/Application/Application.php(149): IPS\_Application::constructFromData(Array) #7 /var/www/html/system/Dispatcher/Admin.php(348): IPS\_Application::applications() #8 /var/www/html/system/Dispatcher/Admin.php(68): IPS\Dispatcher\_Admin->buildMenu() #9 /var/www/html/system/Dispatcher/Dispatcher.php(110): IPS\Dispatcher\_Admin->init() #10 /var/www/html/admin/index.php(13): IPS\_Dispatcher::i() #11 {main} applications/awsses/sources/vendor/composer/platform_check.php Line 7 appears to be the problem: if (!(PHP_VERSION_ID >= 80100)) { $issues[] = 'Your Composer dependencies require a PHP version ">= 8.1.0". You are running ' . PHP_VERSION . '.'; }

Perfect. Good to go now! 🙂

I received a notification that an application had an update within the ACP. I chose the option to install it, and now site wide, I receive the message: ErrorException: Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 8.1.0". You are running 8.0.20. (256) #0 [internal function]: IPS\IPS::errorHandler(256, 'Composer detect...', '/var/www/html/a...', 24) #1 /var/www/html/applications/awsses/sources/vendor/composer/platform_check.php(24): trigger_error('Composer detect...', 256) #2 /var/www/html/applications/awsses/sources/vendor/composer/autoload_real.php(25): require('/var/www/html/a...') #3 /var/www/html/applications/awsses/sources/vendor/autoload.php(7): ComposerAutoloaderInit56a710c1e4edbbc536d58cfc31cc8a09::getLoader() #4 /var/www/html/applications/awsses/Application.php(27): require_once('/var/www/html/a...') #5 /var/www/html/system/Application/Application.php(705): IPS\awsses\_Application->__construct() #6 /var/www/html/system/Application/Application.php(149): IPS\_Application::constructFromData(Array) #7 /var/www/html/system/Dispatcher/Admin.php(348): IPS\_Application::applications() #8 /var/www/html/system/Dispatcher/Admin.php(68): IPS\Dispatcher\_Admin->buildMenu() #9 /var/www/html/system/Dispatcher/Dispatcher.php(110): IPS\Dispatcher\_Admin->init() #10 /var/www/html/admin/index.php(13): IPS\_Dispatcher::i() #11 {main} I have tried enabling recovery mode to disable the applications, but it is still not loading the ACP. Any ideas?

Q&A is a feature that can be enabled when new accounts are being registered. You can provide a question (such as "What color is the sky?" and provide an answer (such as "blue"). In order to create the account, you would have to answer that question correctly. You can find it in yourdomain.com/admin/?app=core&module=moderation&controller=spam&tab=qanda The challenge with these is that you need the question to typically be something your community would know, but not easy enough for human spammers or automated system to already have the answer to. (For example "What is one plus two?" with the answers being "3" or "three".) Chances are the bot has seen those questions before and could answer them. But if the questions are too hard, legitimate members may not be able to answer them and register. The suggestion was to extend the same system used for registration to use it also when someone attempts to make a donation. In order for that to be done, someone would need to develop a plugin that makes donations available to guests again (since it's blocked now in the software for guests) AND also adds that Q&A logic to the donation area.

The IPB software is reporting the path it is using to PHP. It does not know and is not told by PHP what path to use for the CLI. Unfortunately this is caused by the way your hosting provider is setting up PHP on their servers.

This is not something you can check on/off in the core platform, but it's a relatively simple template edit. In the global template, you can do something like: {{if \IPS\Member::loggedIn()->member_group_id === 4}} SOME CODE HERE THAT WOULD ONLY SHOW TO ADMINS {{endif}} If you wanted to show some code to a bunch of different member groups... {{if in_array( \IPS\Member::loggedIn()->member_group_id, array( 5, 10, 11 ) )}} SOME CODE HERE THAT WOULD ONLY SHOW TO SPECIFIED GROUPS {{endif}}

All of the app_scanner references are because of the extra level of debugging added. They're not a problem and IPS has already said they're lowering the level of debug data in a future release.

Captcha alone won’t solve this problem unfortunately. It’s super easy to solve it once manually and then trigger a bunch of automated attempts afterwards.

They’ve “earned” that avatar after all of their time. Haha The avatar is not necessarily a corporate badge that gets turned in upon leaving. (But then again… I’m most likely not the right person to ask as I may or may not have taken a couple of extra pens from the supply closet in my time…)

Ultimately removing the script is all the proof you need. Ad networks are tremendously bad for site speed. It’s literally the cost for monetizing your site. The code while it may have loaded in 258ms stops all other code from working in parallel because it says it is the most important thing. It is like saying you have 10 cashiers in a store checking people out but any one cashier sees a specific person ALL of them have to stop and wait for that one person to finish checking out because it might be necessary later. Some ad networks are worse than others for performance but even Adsense kills page load times unfortunately.