teraßyte

If you are using Pages, the best option is to make custom templates with all that information removed (or hidden for specific groups) rather than adding per-database settings. There are already way too many settings there. 🙄

Since you're also switching the PHP version you need to do a manual upgrade. The automatic upgrade from the ACP won't work in this case. Here's a link to the guide: https://invisioncommunity.com/4guides/advanced-options/server-management/install-and-upgrade-r259/#manualupgrade

As Randy said, there is no way to alert admins with a notification that a user clicked the link. However, if you're interested, it is possible to create a custom modification for it.

It's in the alpha testing stage right now. There's no specific release date just yet. 🤷‍♂️

It's called Topic Summary. You can enable it in ACP > Community > FORUMS > Settings > Forum Settings TAB. 👍

If I had to guess, with the upcoming v5. Invision Community 4.x doesn't even support 8.2 yet, and never will most likely.

Nope, all's good. The "Fix This" text is simply the default text for that button. I always thought it was confusing and they should change it, though. There's nothing to "fix" when Redis is enabled. 😋

Yes, that's all normal. You have a couple of old values that aren't used anymore in 4.7 (banned_group & auth_group), but they won't cause any issues if you leave them there.

I used to have some very easy $5 modifications before. However, at some point, the minimum cost possible on the IPS Marketplace was set at $10 to cover fees, eventual chargebacks, payout fees, etc. That change increased the cost of all those small plugins that used to be $5. Selling it for $5 on my site and $10 in the old Marketplace would have made things unfair for those who used it. With every developer handling things on their own/separate sites, you might see smaller prices for minor v5 modifications. No idea if it will happen or not, it's just my thought. 🤷‍♂️ EDIT: @opentype also made some fair points, though. The marketplace gave a lot more visibility to the available modifications. I still think IPS should have kept the Marketplace available, but make it redirect to the developers' sites (just like Invisioneer does). The idea included adding a big red warning about not supporting anything in it. IPS didn't think it would be a good enough solution, though. They wanted to avoid any kind of possible misunderstanding and decided to remove it all.

You'll need to find out which task exactly is causing the issue. Is there any locked task in ACP?

Have a look at this file https://ipb.silvesterwebdesigns.com/file/7-wordpress-sso/ by @stoo2000

It's the query that loads the popular content for the leaderboard page. Example here => https://invisioncommunity.com/leaderboard/

I see some hooks in that backtrace. Try disabling all 3rd party modifications and run again the task. Is that OutOfRangeException error still being logged?

This is certainly doable, but it would rely on hooks (unavailable in v5). If you plan on updating to it quickly, it's probably best to wait and see how we'd be able to handle it there (if we can at all?). There should be ways to do it still, but until we see the code... 🙄

I can't think of anything else, unfortunately. The sortby value is what the framework uses in several functions, some of which I can't even hook in. I don't think changing it to another variable is feasible. Considering v5 won't have any hooks, and that Q&A forums are also going away, I don't plan on rewriting this plugin from scratch to change how it works to try and somehow work around this problem. At this point, your best option is to disable the plugin and wait for v5.

Hmm, wait. Are you saying Google can't index any pages starting from 2 because they all have the sortby value in them (which is not there by default)? If that's the case I can add a check to exclude adding it if a bot/search engine is viewing the topic, but I'm not sure if Google would then complain that your site is showing different content compared to guests. Since they're not indexing any sortby links it should be fine, though. 🤔

My plugin simply changes the default sortby value from votes to date when there is none specified in the URL/request. Everything else is then handed to the framework to handle behind the scenes. There's nothing I can really change with it. 🤷‍♂️

I've seen the automatic upgrade break down a lot recently, and almost all people were using PHP 8.2 (which is not supported). As Jim said, check that your PHP version isn't above 8.1. If you already have the correct PHP version, a manual upgrade (reply above) is the next best option.

The function that checks if the IP is banned or has made too many bad requests is the function _checkIpAddressIsAllowed() in system/Dispatcher/Api.php on lines 198-230.

It clears up after 5 minutes: /* If we have tried to access the API with a bad key more than once in the last 5 minutes, throw an error to prevent brute-forcing */ if ( \IPS\Db::i()->select( 'COUNT(*)', 'core_api_logs', array( 'ip_address=? AND is_bad_key=1 AND date>?', \IPS\Request::i()->ipAddress(), \IPS\DateTime::create()->sub( new \DateInterval( 'PT5M' ) )->getTimestamp() ) )->first() > 1 ) { throw new \IPS\Api\Exception( 'TOO_MANY_REQUESTS_WITH_BAD_KEY', '1S290/D', 429 ); } It's also possible to make a modification to whitelist IP addresses. It needs a couple of hooks on some functions, but it's doable. I did it for a client before as part of a bigger request.

Time to see the ACP then. 😋

What error are you seeing exactly?

Usually, you just upload from the root folder and the correct folders/files are properly overwritten. There's no need to upload every single file in its correct path/folder. What FTP application are you using?

As Marc said, that's the correct place to upload the files inside the folder ips_xxxxx. There are quite a lot of files that will be useless after the upgrade there, but you can worry about deleting them later. While I always suggest cleaning up the old files, you should confirm that the upgraded suite works as expected first.

To upgrade such an old version you need to: Switch to PHP 8.0 and check the requirements are all good. (Don't use 8.1 because it causes a few more upgrade errors compared to 8.0. The old upgrade steps were never written for 8.0/8.1 which didn't even exist at the time.) Manually upload the new 4.7 files to your server. Go to /admin/upgrade to start the upgrade process. Before doing the upgrade, you also should uninstall any 3rd party applications/plugins that don't have any updated version for 4.x, if not a lot of extra tables/columns/settings (maybe even tasks) will remain in the database. Considering how old the version is, doing a test upgrade in another location is usually a good idea, especially if you have lots of 3rd party modifications installed.