Gabriel Torres

All good, everything is working fine, I was probably tired when I tested this.

@Nathan Explosion @Matt @Adriano Faria Thanks, cleared the cache here and the pop-up window is now showing up when I hit the "X" button for deleting a user. However, when using a search option and clicking in the "Prune Members Found" link, I get straight to the "Confirm Prune" page instead of the pop-up window asking if I want to delete/hide/leave the contents. Could you test this on your side to see if this is an issue with my install, the expected behavior or a bug? Thanks. Matt, can you move this topic to the correct forum, as this is not a "feedback" issue anymore, but a technical problem at my side? Thanks.

This is actually something I'd love to see added to the platform. In the past, we achieved this with a third-party plugin, which became incompatible with PHP8 and we had to remove. There is actually an app for that currently available in the marketplace: https://invisioncommunity.com/files/file/10175-tb-banned-members-enhancements/

Same happened here. I had to go to the Marketplace section inside ACP and look for it to update it to the latest version. I knew a new version was out because I am subscribed to receive emails whenever the app is updated.

I know that it wasn't present before. I am suggesting you to add this is a future version. Thanks, I will test this again! I may have missed something here.

@Nathan Explosion @Adriano Faria I will investigate this further and let you know what I find. Thanks!

Wow. Different behavior here. Running 4.7.11.1. No popup is shown. Maybe because you are using dev mode?

@DawPi Installed the latest version and when adding the content, I missed a tag for the user's name! So we can write something more personalized like: Another issue I faced is that when a post is hidden, no notification is generated. The notification is generated only when a whole topic is hidden. You may want to take a look into this. Thanks.

Just keep both options, then! Max number of lines AND max number of chars. We have this disabled here.

@Marc Stridgen At least here with us, we are always looking into ways to reduce the size of our database and pruning unecessary data. Our community for 20 years now, so you can imagine the size of everything here. In our case specifically, we think we can do a nice cleanup by pruning old spammers (e.g. over 1 year ago) and their offending posts/topics. Banned users are a different case, however, with new privacy laws in our country, it is always a concern to keep personal data from these users...

@Nathan Explosion A couple of suggestions to improve this amazing app, if possible. In summary, add options also to the topic title, in order to prevent low-quality titles: 1. Minimum number of word/characters in the topic title. 2. List of ban words for topic title. Here we would enter phrases such as "help me" and others that don't help others to know beforehand what the topic is about. I hope you can add them to the app. Thank you in advance! Cheers.

@Nathan Explosion Excellent app, we were really needing it here. The "limits enabled" string is hard coded in the two available templates. The best would be to include it as a language string: <li>{lang='neapp_contentlimits_type_word'} limits enabled E.g. a new language string as: %s limits enabled Just my two cents! Cheers

PS: Ditto for the "Prune Members Found" option.

I actually found a workaround. Use the search (gear icon) the the ACP member page to select a desired criteria, and then click on the "Spammer" button. This time the "prune members found" option will show up! 😉

Hi, If we delete a user from its profile in the ACP, we are asked what to do with the user's content (delete/hide/leave). However, clicking the "X" button in the member's list (see below) performs the "leave" option. This is really annoying! The system could show a popup asking what we want to do with the content the user posted. Not to mention that there is no way to mass delete spammers/banned users, functionality that has been already asked by several board owners... 😉 Thanks!

+1

Hi, This is an old issue for us. We can limit signatures only by number of lines, but this is insufficient for us, as some users are abusing this and posting really long lines, so their signatures are huge. It would make more send for us to limit the number of characters, not lines. Another suggestion for signatures would be that links to contents such as topics wouldn't be converted to their "embedded" version, but kept a normal URL link. Currently we use a custom plugin to fix this, and it would be nice if this was a core feature. Thanks.

@Daniel F Jeez! Thanks! I will take a closer look and fix the boo-boo I've done to our database.

@Marc Stridgen @Daniel F Nevermind, I found the culprit... In the past I manually deleted some members using a MySQL query, and I haven't deleted the corresponding records in the core_follow table. Therefore, the issue is entirely my fault. I no longer will delete users using queries, as this breaks things up... Thanks!

Hi, This is regarding the Pages (cms) app. We have a couple of databases with the review option enabled. Now, when I try to answer a review, at the front-end everything seems to be working, but the answer isn't saved in the database (I know because the review_author_response row in the cms_database_reviews is NULL for the review I replied to). I tried with thee default, unmodified theme, to the same result. It was working before when we were running an older version of IPS, but this issue only came to my attention today, when I tried to reply to a customer. Thanks!

As I explained in my post, this is not a theme issue. The error is thrown when one of the followers simply don't exist. The member_id is there in the core_follow table, but the member with that ID doesn't exist at the core_members table. Deleting this rogue records solved the issue for me.

@Marc Stridgen As I mentioned, I deleted the offending records. My best bet is that a routine in charge of deleting users is not deleting the corresponding records in the core_follow table. I would suggest testing this by getting a test user, making it follow another user, then make the test user request his account to be deleted, approve this deletion and checking if the record in core_follow table was deleted as it should.

@Vasile Rogoz @Marc Stridgen Today I saw this very same error in our system log. The OP failed to provide more detailed info. This error shows up when trying to see the full list of followers from a user. E.g.: https://invisioncommunity.com/profile/536186-marc-stridgen/followers Here, this error was being thrown when trying to see the follower list of a specific user. All other users the follower list displayed just fine, without throwing an error. So I knew it had to be an issue with that single user. Upon further investigation, I discovered that there was one row in the core_follow table that was pointing to a user that no longer existed. Deleting that specific row solved the issue. In fact, I found a total of 10 rows (out of 460,000) with the same issue. Deleted them all with: DELETE FROM core_follow WHERE follow_member_id NOT IN (SELECT member_id FROM core_members); Now, why this inconsistency happened? I have no clue. Maybe this is a bug caused by a third-party app, maybe it is a core bug, caused by a routine that should have deleted the corresponding rows at core_follow when the user was deleted (maybe when users request their account to be deleted?). I have no further info for you at this time, but you ought to test this further. I hope I have helped. Cheers!

We also need to swap the location of the <br> tag, so we don't end up with two <br> tags when no navigation bar is present. On line 12 Where: {{endif}} <br> Should be: <br> {{endif}}

Hi, If you take a closer look at the user's all followers list, you will notice two things. Please consider this link as a reference: https://invisioncommunity.com/profile/87228-andyf/followers/ 1. The backgroup is gray. IMHO, it should be white. core > front > profile > allFollowers Where: <ul class='ipsDataList'> Should be: <ul class='ipsDataList ipsAreaBackground_light'> 2. The top pagination is too close to the <h3> header. More spacing is needed. See: Where: <h3 class='ipsType_sectionHead'> Should be: <h3 class='ipsType_sectionHead ipsMargin_bottom'> Just my two cents. Cheers!