teraßyte

Did you notice the issue after a recent upgrade? Most likely the language pack you have was not updated for the version you're using. If you're sure the language pack is updated for your version try installing a new copy of it and see if that works.

It's always possible to just restore the backup in a different location (even locally), retrieve the photo, and upload it to the user's profile on the live site. As long as you're willing to go through with it just for a photo. 😋

Hey there. Been a while! 🙂 Sure, if the suggestion above about the language pack doesn't work send me a PM with the details and I can have a look. 👍

There's some kind of bug in the code that sends out the emails most likely. They'll probably be able to check it only on Tuesday (6 September) though.

Which version are you using? There was a patch released at some point that had to do with dates. You can check in "ACP > System > SUPPORT > Get Support" if you have any pending patches that need to be applied.

Most likely one (or more) of your applications/plugins is not compatible with PHP 8. Check if there are any updates, if there aren't disable all modifications, switch to PHP 8, and then re-enable the modifications 1 by 1 checking which one is causing issues. Or, you can just wait for version 4.7.2 to come out of beta since it contains a tool that can tell you which modifications won't work with PHP 8.

Add this to the custom.css file of your theme: .ipsQuote_citation { color: white; }

I can see the sitemap just fine when I view the url: https://www.vespaonline.com/sitemap.php There must be something server side that is blocking Google's IP or useragent. It should show more details about the error if you click the bottom-right arrow in your screenshot.

Ok, so robots.txt is not the problem. What do you get if you try to submit the sitemap in Google Webmaster Tools? If there are issues it should say something there.

Do you get any specific errors? Maybe you have a robots.txt rule that is stopping google from indexing your site.

There have been a few topics about missing the core_follow_count_cache table lately. 🤨

Makes sense. I also have some apps/plugins that extend files in different applications and they only work when it's installed. This kind of error should be shown only with IN_DEV enabled ideally.

IPS has barely started supporting PHP 8.1 with the 4.7 version and there are still some minor issues here and there. I suggests testing the upgrade using PHP 8.0 to be safe.

@Jim M Twitter's site has changed a lot since the guide was posted and the way of setting up the application is completely different now:

That's something your hosting needs to change in the MySQL configuration file. Instead I see a different issue in your screenshot: you have a mix of utf8 and utf8mb4 tables. You should convert them all to utf8mb4.

This is the support topic for this modification:

The task usually updates several users at once when it runs. It does a batch of them rather than a single one. From you screenshot it clearly updated 5 members 2 hours ago, then 4 member 1 hour ago and finally 1 member 10 minutes ago (I guess it was the last user that needed an updated, thus the single-member batch).

Most likely it's the profilesync task updating their accounts automatically.

If you can setup a cronjob just like the the text says.

You can edit that setting in ACP > Community > FORUMS > Settings > Forum Settings TAB > Default forum view.

Have you uploaded the developer files before you enabled IN_DEV?

IPS doesn't save the login success/failure. You'd need a 3rd party modification:

Looks like your language pack is missing several language strings and it's displaying their keys instead. Is that the default language pack or a custom one? If it's a custom one try using the default one and check if it still happens. If it's the default one, try adding a new language pack and check again.

Depending on the server configuration, installed modifications, and how things are setup there can be a large number of different issues. Or if you're lucky (no modifications installed, etc) none at all. When a forum is several versions behind I usually suggest trying the upgrade on a test copy in order to see how it goes, and eventually fix any bugs you encounter so that you're ready for upgrading the live site with no surprises. Another thing would be checking which modifications and custom themes you use (if any) and see if there are updated versions of them for the suite version you're going to upgrade to. For example if a modification critical to keep your forum working is not updated you'd have to first reach out to its developer and see if they can update it. If they're not available you may need to update it yourself (if you know how) or you may need to hire a different developer to update it for you. There could also be modifications that aren't updated but that you don't mind losing either. Some modifications might still work without changes, but themes surely won't since they won't support all the new features IPS added. As an example I recently upgraded a client's forum from 4.2 and beforehand I updated 3 custom modifications for them since the original developer wasn't available anymore. We also did a test upgrade and found some columns from old uninstalled modifications that caused errors during the upgrade process. Thanks to that we fixed the live site's database and ended up avoiding the error completely. As I mentioned above anything can happen and there isn't really a list that covers known issues: the best way would be to compile your own list by making a test upgrade and seeing what happens directly.

If I recall right, only accounts with ACP access are automatically excluded from promotion/demotion. There's no additional setting to exclude other specific groups. In theory you could add them to a group with ACP access but totally restrict their account so they can't actually do anything (except changing their email address or password).