teraßyte

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.

Yeah, I've already reported it as a bug and it's been acknowledged: No ETA on a fix though... 🙄

Until IPS adds it, this plugin I made has the option to replace the author data with the last poster data for the topic feed widget: It only replaces the profile link and date though, if you want to show also part of the last post it's not possible with it.

That link doesn't work without an account to login. What is the account error on that page? You can either copy/paste here the error or post a screenshot of it.

When an ajax modal popup is loaded, and it contains pagination, changing the page changes also the browser tab's URL, but closing it doesn't restore the original URL. You easily can verify the issue on this site by viewing a file with at least 2 pages of logged downloads. Here are the steps to reproduce: Visit this link: https://invisioncommunity.com/files/file/10121-tb-log-attachments-downloads/ Click the Who downloaded this? link => The browser tab's URL remains as-is: https://invisioncommunity.com/files/file/10121-tb-log-attachments-downloads/ Now click to load the modal popup's second page of downloaders => The URL changes to: https://invisioncommunity.com/files/file/10121-tb-log-attachments-downloads/page/2/?do=log Close the Downloaders popup => The URL still contains the log/page data from #3. Click F5 to refresh the page => The page reloads the download logs's second page (#3) instead of reloading the file's (#1). There should be a way to pass an option to not update the URL in some cases. While I doubt this will be fixed for 4.x, it's something you should consider for 5.x at least.

@MynDoSCSC Uploaded a new 1.1.4 version with the fix currently pending IPS approval. Here's the changelog:

@MynDoSCSC Is that the modal popup on the front end to view the download logs? While I can't reproduce the 403 Forbidden issue, I'm noticing that the pagination is not working properly, so the issue might be related. I'm going to take a look and let you know.

What Invision Community version are you using?

As a workaround, you can temporarily move those users to a different group and avoid searching inside it for users to delete. Once you're done move them back to their original group.

You can create a Group Blog in ACP: And then disable their group option to be able to create new blogs.

The IndexNow integration in ACP has no setting to enter an API key. 🙄

Nevermind. I failed to see you mentioned you're using the Source button. It's doing what it says, it lets you see the source HTML... 🙄