teraßyte

Yes. You can find a list of people available for paid work on this page: https://invisioncommunity.com/third-party/providers/ I'm also on that list, and I often help with upgrades. If you want, you can send me a PM with more details about your situation.

All those 4 warnings/errors in your screenshot will go away once you update to the latest 4.7.10 version. Or are you saying you are already on version 4.7.10 and those notifications are still there?

As the error says, the script wasn't able to write the file to your filesystem. Check the permissions for the /datastore folder (either 777 or 755; depending on your server configuration). If permissions are okay check that you still have space available on your server.

Oh wow, it took me a whole minute to realize it's from a widget. I didn't even remember it existed. Looks like it's using a different template so I need to add a new hook for that. I've added it to my to-do list.

Looks like your Pages (cms) application files aren't updated correctly to the latest version. To fix this is should be enough to re-download the ZIP file from your client area and manually re-upload all the files from it. There is a chatbox hook in the error backtrace, so it might be related to that. Try disabling the application and see if that fixes it. If you're using a custom theme try also switching back to the IPS default, non-customized one.

There should be an error_log file on your server (or maybe visible from your control panel; depends on how the server is configured). See if there's anything logged there. If you can't find the file, try asking your hosting for its location. I see Marc also mentioned: Maybe IPS will be able to have a quick look themselves since they have your FTP access.

It was a bug in previous versions because of the new future publish option. The bug was fixed in either 4.7.8 or 4.7.9, can't remember right now. Either way, since you've updated to 4.7.9 the issue won't happen anymore. The only way to fix already edited old posts is to change the post data directly in the database (always make a backup!) or using a modification.

Oh, I missed that part of your post. I can indeed see why it would be a problem with your situation. I can't really think of anything else right now. 🙄

A workaround could be to set up the Members group to not be able to send PMs unless they have at least a few posts. Once they make the required number of posts you can move them with an automatic group promotion rule to another group that can send PMs.

Adding validation for 3rd party login methods is not possible. Unless I remember wrong, they specifically have rules in place that no further validation should be required.

The badge icon is indeed not displayed on posts, you can see the same happening on this site: Once awarded, the badge icon appears only in the user's profile: https://invisioncommunity.com/profile/145950-teraßyte/badges/ => Helpful for a post in a topic

Did you test with 4.7.9 or 4.7.10 Beta? Unless I remember wrong, this is already fixed in 4.7.10 Beta.

Double-check that the Physical Address field is not partially auto-filled before clicking the save button. I noticed that sometimes the browsers auto-fill it with only a few values, and the form complains it's not a complete address when it's submitted.

It's not working because the URL is not the same as before. In the previous screenshot, you were using the /forums/ folder, but not in your latest screenshot. The check requires the same exact URL, not just (sub)domain.

That's the wrong value. The cronjob needs to run once per minute, not day.

Oh, I see. In that case the default converter won't support that kind of custom item. You have 2 options: Manually add the posts. Hire a 3rd party developer to create a custom conversion script for you: https://invisioncommunity.com/third-party/providers/

@Marc Stridgen Just a little update: the unread page is as fast as usual now. Maybe the recent upgrade fixed whatever was wrong with it. 🤔

You'd need to install the Converters application to import them. A list of what can be imported is available near the bottom of this page: https://invisioncommunity.com/services/convert/ Here's also a guide on how to get/use the application:

That is not something Invision Community does. Maybe your server was hacked, or some other script you use is injecting that code? As a first step verify what the file in that include path contains.

I tried visiting the url in your screenshot, and I got get the 500 error you mentioned. If that error_log.0 mentioned above is empty, the error is probably being saved somewhere else. Or maybe the error logging option is disabled at the server level. 🤔

@Adriano Faria In the past, I overloaded the function \IPS\Member::__set() checking for the key pp_reputation_points and then checking if the do parameter starts with (un)react. That should cover all areas I believe. # We're updating the 'pp_reputation_points' value and we're (un)reacting if ( $key == 'pp_reputation_points' AND \IPS\Request::i()->do AND ( mb_substr( \IPS\Request::i()->do, 0, 5 ) === 'react' OR mb_substr( \IPS\Request::i()->do, 0, 7 ) === 'unreact' ) AND \IPS\Member::loggedIn()->member_id ) { // Your code } You also need to account for when the reputation is rebuilt though. That check is not included in the example above. It requires hooking the function that rebuilds the count and passing along some kind of flag. If you want to check only removeReaction() skip the do=reactXXX check. That said, this kind of code doesn't let you know which reaction is actually being removed. It only acts on the points being updated. If you require to run it on specific reactions only, I have no idea how, unfortunately.

@Marc Stridgen Recently I've noticed the unread stream is extremely slow to load. It can take up to 15+ seconds. Most likely the screenshot above is caused by the page timing out when loading.

I doubt anything will change for 4.x at this point. My only hope is that they'll implement something for 5.x... 🙄

What happens exactly? Are you getting a 500 error, perhaps? Or something else? Your server logs will probably have more detailed info about the issue.

The best way is to compare the list of folders/files on your server with the list from the ZIP file you download from the client area for the manual upgrade. However, if you don't have any 3rd party modifications installed, it might just be easier to remove all files except /plugins and /uploads, and then re-upload a fresh set of files from the ZIP file. Anyway, be sure to always take a backup before doing this kind of cleanup.