Randy Calvert

I guess I’m confused here… 4.7.3 uses the same exact upgrade scripts from 3.X. It’s incremental and takes the older ones and steps them up with next version changes. So the files related to old version are going to be the same. What are you gaining by this? Also IPB has never distributed old versions of the software. Even back in the 3.X and 2.X days… old versions were not available after a new one was released. This is by no means new or different.

If they’re old and never used, they were most likely registered by the spammer months ago and “saved”. Many sites have rules that restrict accounts less than XX days old (say 30 days). I would be more inclined to believe it was a data breach elsewhere if it was long term member accounts that had historically been active and participating on your site suddenly spamming. But an account that was registered and never used that surfaces months later does not scream external data breach.

@teraßyte is spot on. 🙂 By the way... there's a handy guide to getting started creating your first forums/categories in case you find it helpful.

If you are wanting to do this on a per-member basis, you can find their account in the ACP. Click on "Edit Password". You can either enter a password for the member directly (which will not be emailed to them) OR you can click the link to force reset the password. If the user is currently logged in, they'll be logged out. They'll get an email prompting them to reset their password. If they follow the link, they'll be able to set a new password. It is important the user's email address is still valid, etc for this step to work obviously. 🙂

You spelled "everything" correctly this time! 😄

Your older version will not support PHP8. Your newer version won't support the older version of PHP however. So basically you're going to upgrade to PHP8 first. (Then use the compatibility checker to make sure your new PHP8 has all of the required modules.) That will essentially bring your website offline... however that's short term. Upload the files for 4.7.6 to your website. If your PHP8 is compatible, it will work to launch the domain.com/admin/upgrade, (login with your ACP credentials) and it will walk you through updating all of the database changes that are needed to get you to the latest version.

February release looks to be pretty interesting. 😄

What path are you trying to access specifically? Are you trying to access it from ACP or from the front end?

Just because you are an admin does not mean you're also a moderator. Did you also define the user as a moderator as well? ACP > Members > Staff > Moderators If the user is not listed there (or within a group specified there), they won't have access even though they're allowed access to ACP.

You don't add answers in the ACP. It's unique to whatever is picked by the user when they setup MFA. If your security question is "What street did you grow up on?" ... the answer would be different for me than it would be for you. You don't want to ask questions like "What is 2+2?" because ANYONE could answer that. It should be a question that has a unique value to the person.

You can turn it on/off as you see fit. So you could have it off, and turn it on.... then decide to turn it off for a year... then come back and enable it again. (This time even changing where the data is stored theoretically.) Now... again, it does not happen instantly. It can take days/weeks to complete depending on how many topics need to be changed and how busy your board is. So it's not something to just randomly change every few hours.

Technically you could change ANYTHING in the name of the forum and it would redirect. For example, this support forum itself... https://invisioncommunity.com/forums/forum/497-help-support/ If I change it to https://invisioncommunity.com/forums/forum/497-help-me-help-me/ When the server processes the forum ID (497) in this case, it issues a HTTP 302 redirect to the value stored in the database. Below is an example of the HTTP headers showing this: Because it's a 301 code, Google will know it's a permanent redirect and will not penalize you for duplicate content.

Think of it this way… the further behind you are on versions, the harder it is to upgrade. Moving between minor point versions are MUCH less likely to run into issues. But the further behind you are, the more likely it is you’re going to feel pain. Upgrading from 3.X to 4.X is like 100 upgrades rolled into one. It WILL be painful. However just one will be fine in 99% of cases.

If the screen is just only displaying white, it means that errors are being suppressed. Try adding the following to your htaccess: php_flag display_errors On You can also look in your server’s Apache error logs for details as well.

It means the underlying issue that allowed this situation to happen will be fixed. If something is already preventing you from using the auto updater with the current version, nothing in future releases will fix the CURRENT updater other than downloading the files from your client area and uploading them to your site (aka “a manual update”).

This is a browser requirement. You need to work with your host to setup SSL for your site. Once done, follow the following guide: Basically once SSL is setup, you change your board path in constants.php to be HTTPS instead of HTTP.

Per the first post... Once you have a paid account, you'll have to wait a short while for it to sync and realize your account is paid. I would suggest waiting an hour after you activate it at least.

Glad you were able to get it resolved. 😄 Sometimes it's only after you say something to support does it actually start working! I see it happen EVERYWHERE not just here. 😄

It sounds like you actually deleted that member group. Create a new member group called "Moderators" or whatever you want it to be. ACP > Members > Groups I actually have one called "Global Moderators" that are unrestricted moderators and another just called "Moderators" that are individuals who moderate specific forum(s).

Because the server is making the request, Cloudflare is never called. Cloudflare is only called when someone types in "youdomain.com" because your domain is pointing DNS resolution to them first. Your server in this case is making a call to "api.giphy.com". As a result, the DNS resolution would never trigger a call to Cloudflare.

You can define moderator groups by going to your ACP. ACP > Members > Staff > Moderators That is going to be domain.com/admin/?app=core&module=staff&controller=moderators If you don't have a moderator group there already, you can add one. In the upper right side of the screen will be a green "Add Moderator" button. Click it. You'll see a screen that says: Pick which group you want to be a moderator and choose Save. You can then edit that group if you don't want them to be an unrestricted moderator.

You might want to post this in the 3rd party resource author's support topic... IPS staff cannot provide support for 3rd party applications, so you'll need to ask the author. If you click on the link below and choose "Additional Information", you'll see all of the various methods the author lists for getting support.

ACP > Members > Staff > Moderators Check to see if you have an existing member group for moderators. If not, add one. You can edit it to select which specific permissions they should have (and where). If you don't apply any limits, they'll be considered to be unrestricted moderators. Once that is done, assign your specific moderators to that group. So if "Bob" is supposed to be a moderator, set it as his primary or secondary member group. ACP > Members > Members You could just assign moderators without setting a group, but it means you have to set permissions for each specific person instead of the group and have them inherit it automatically. Also take a look at the following guide for setting up moderators:

I don't use the member map application, and that table exists for me.

Giphy will return a JSON string with a HTTP status code of 200. It does not have one fixed IP.... it has different IPs based on where you are around the world. You can't just whitelist a single IP and it solve your problem. IF you do have outbound HTTP restrictions, you would need to allow all outbound requests for the hostname.... not the IP address. Just FYI... I can almost guarantee that CF is not your problem. CF is involved on the INBOUND request (because its a reverse proxy). Meaning someone types in www.yourdomain.com and it routes to CF which in turn sends it to your server. The call to Giphy is essentially the opposite. Your server directly initiates a request to the Giphy server which is not routed through CF. So you're not going to be whitelisting anything related to Giphy at Cloudflare. Also if it works sometimes, but other times it does not... you're not running into a whitelist issue. If it was blocked by the firewall, it would always fail until whitelisted. If it's intermittent, I would highly suspect something within the network stack OR a high load on the server, or something similar that is causing your problem.