Randy Calvert

Ips4.php is a script that will tell you if your server has the required PHP modules installed. Run it AFTER switching to PHP8. (You want to test the new version of PHP, not the old one.) Once you see everything green, you can upload a set of the IPB files from the Client Area. Once those are uploaded, run the upgrader at domain.com/admin/upgrade.

You waited too long to do an auto upgrade. Make sure any third party resources you are using are updated and support PHP8. Then you need to download the IPB files from your client area. Switch your site to PHP 8. Make sure your PHP8 version has all of the required modules. Upload the latest IPB files to your site, and run domain.com/admin/upgrade.

Why would you want to do this? It would mean any action you take as an admin with hidden content could simply be undone by the person. So for example someone who posted something that should not be posted because it's against your rules could simply unhide the post you hid.

If it's spamming the same thing, look at the IP addresses and see if they are in the same range. If so, block the /24.

Who knows... Google does what Google wants and does not explain their reasoning or answer to us peons. 🙂

Sorry, not me.

Woot! Even more for less… That’s always a winner!

If this is an initial installation you need to check to make sure you meet the system requirements. If those are met, check your server’s error logs to see what is failing.

Did you check to make sure you meet the system requirements for installation? If you meet all of the system requirements, you will need to work with your host to check the server’s error logs to see what is failing.

There is no “orphan” file checker.

If you are set to use cron jobs, if the task is not running… there will be a big warning shown on the front page of your ACP.

https://invisioncommunity.com/contact-us/ Choose Accounts & Billing

If you have access to the server logs, look in the cron job log (typically /var/log/cron). If you don’t see an error warning in the ACP it’s fine.

Just adding that does not add risk. But the question becomes what you do with the data input by the user.

Are FURLs working properly?

If you are looking to cancel an IPB package, use the following link: https://invisioncommunity.com/contact-us/ Choose "Accounts and Billing.

Huh? I’m not sure you’re quite understanding what has been said so far. IPB5 will be available for both self hosted (classic) and cloud. When IPB5 is released, users will not be required to immediately upgrade. They can continue to use IPB4. IPB4 will continue to receive technical support and bug fixes for quite awhile after version 5 is released. They’re telling folks that the deprecated features won’t exist in 5. That does not mean they’re being removed from version 4. (No clue where you’re getting that idea because that is NOT what the announcement says.) At some point however (like a year or so after 5 is actually released is the general time I’ve seen discussed) 4 will some day fully go away. It won’t be maintained forever. (The same thing happened when 4 game out… 3 was supported concurrently for a year and even a second year following 4’s release for security updates before eventually being fully ended.) Given the depreciation timeframes noted, it can be guessed that IPB5 won’t come out till 2024 at the earliest. That means we’re talking 2025/2026 before it could actually go away at minimum. That gives you PLENTY of time to plan for your site.

Once you place an order, it will be given to @Olivia Clark to setup the transfer and work out the details. She covers the things needed (such as needing to provide an export of your database and a copy of your home folder) and will help pick a time that works for both you and IPS to take your site offline for the actual migration. The time of the transfer itself… it is generally @Marc Stridgen who will make the magic happen. My migration was super smooth… they have the process down to a fine art at this point.

Might want to post that in the feedback forum instead in the middle of a help topic. 🙂

Also if you are changing php.ini… those changes might not be picked up until Apache is restarted.

This took 4-5 hours once for me. It looked to be stuck but eventually resolved itself. (I came back the next morning and it completed.)

Have you confirmed your localhost environment meets all of the system requirements for running IPB? If you can't run recovery mode or access the admin CP at all, it sounds like a bigger system configuration issue. By the way... my personal suggestion is to not use your own computer for testing backups. I would suggest using the same server on a separate subdomain. Something like test.yourdomain.com. That way you know the system configuration is the same in your test environment as it is in your production environment.

I’m glad you got to the bottom of it! The good thing about the situation is that you learned how to troubleshoot better going forward!

This means your CRON job is still pointing to an old version of PHP. It is not the PHP version of the site itself. (The server has multiple versions of PHP running and the cron is pointing to 7.4 still.) Once you can actually login to ACP, you’ll want to get the correct path to update your cron that runs every minute.

First, turn off the CDN to make sure it is not interfering with anything. I see your site online. It looks like chatbox is still turned on? But again, I don't see errors as I browse around. It's possible bad JS or other files are cached at your CDN. Since we would both be connected to different CDN servers, my server may not have the bad files. A purge of the CDN might solve it. (That's also why turning off the CDN is a good thing to do when troubleshooting so you eliminate it as a potential problem.)