Makoto

This is the support and feedback topic for the Account Deactivation application, If you run into any issues, or have any questions/concerns, please let me know!

Thank you for your purchase! Both of these features will be added in the future releases. Right now this is still an early beta of the application (hence the discounted price) and am working to make sure all the more basic features are functioning as intended first. Currently the application will format prefixes when selected using the regular "Item prefix" option in the tag menu, I'll also be adding in the option to require prefixes/select which prefixes can be used on a per-forum basis in the next release, but want to see if there's a way I can cleanly hook into the native "Item prefix" menu instead of requiring two different forms for it as happens with Advanced Tags and Prefixes, Keep in mind everything here was rebuilt from the ground up and naturally I can't just copy features directly from the old Advanced Tags & Prefixes mod, so when doing everything for IPS 4.4 and onward I want to make sure everything it's done to modern standards and in as user-friendly of a way as possible.

Hm. This is not currently a feature, but I'll see what I can do.

Ryan has discontinued support and development for his original Advanced Tags and Prefixes application, and it hasn't seen much further development since its initial launch anyways as Ryan hasn't had the time to work on it. Radical Tags has been rewritten from the ground up for the latest releases of IPS. It replaces the old prefix editor which requires HTML knowledge and manual styling with an easy to use editor anyone can use, or, for more advanced users, provides a fully featured templating system. In addition, it adds support for tag aliases, automatically converting tags to prefixes, more advanced tag management features, and in the future will support things like multimoderation tools for tags and Prefixes, prefixes for gallery albums, tag/prefix filtering and more.

This is the support and feedback topic for the Radical Tags application, If you run into any issues, or have any questions/concerns, please let me know!

A new maintenance build has been released. This resolves the cause of the "Malformed kickbox response" errors being logged and an issue with the use counter on the cache table identified by @vicentiu

If you have installed the application but are not seeing the settings for it and it is not blocking registrations, there might have been an issue installing the application in your specific server environment. Can you please send me a PM here or on Slack so that I can investigate this for you further?

Hi @vicentiu! Can you please confirm what version of IPS you are running, and let me know what disposable e-mail domain you are testing with? Also note that this is an Application, not a plugin, so it must be installed from the Applications page.

Hi there! Thank you for your feedback! Kickbox is an extremely reputable service and their API service is solid and well tested, so I put a lot of trust in their service. On top of that, their for-profit parent service allows them to provide the disposable e-mail validation service 100% free without needing an API key and with no usage limits (the other options you listed above have usage limits that would be extremely restricting on larger communities, unfortunately).

The issue with "Malformed kickbox requests" being logged will be resolved with the next maintenance release, which will be posted by Friday, https://dev.taiga.sh/ips/Indisposable/milestones/3 @Gabriel Torres let me know if you're having any issues with logging and I'll make sure that's investigated before then. If you just mean identifying members without manually running the reindex task, keep in mind it will only automatically re-identify these members when they log into their accounts. (So you may actually want to go ahead and run the reindex task again if you plan to use the filters for bulk mailing, otherwise it should still work as intended for forcing members to update their e-mails and group promotion rules)

Do you mean registrations, or existing members? Are you seeing members with disposable e-mails that it is missing, and are you referring to the Members table, or the Logs table?

Yep! Responses for non-disposable addresses are temporarily cached (currently for a few days). The reason they're only temporarily cached is just to ensure that the domains aren't disposable e-mail addresses that haven't been caught yet. On top of that, there is a hard-coded array of 149 well-known trustworthy e-mail domains (from all countries) stored in the validation class that is checked first, which includes services such as gmail, hotmail and so on. So it will never even need to query for those, it knows those are legitimate right away. I've worked to make sure everything is built with performance in mind so you should have nothing to worry about, but I'm here to help if you do run into any issues!

Can you post the exact error you are getting when running the reindex script?

@Gabriel Torres, @MediaDIGI.com, Sorry about that, please upgrade to 1.2.1 and see if this resolves the issue! (I'm using a new local build script that wasn't pulling the latest setup files from my development server, so the 1.2.0 release was missing a file needed to create that table. 1.2.1 will check if the table exists and create it if not.) I've got that fixed now so it won't happen again in the future! @Gabriel Torres, That shouldn't happen again, I apologize for that. I've made some performance improvements to the rebuild script that should help speed it along this time, however. This list will also now be automatically populated with 1.2.0, so you don't need to run the script unless you want to immediately have all the members indexed.

Version 1.2.0 has been released! This is a major release that primarily adds support for either prompting members with disposable e-mails to update on login (optional), or forcing members with disposable e-mails to update before they can access any area of the site. This additionally adds the logging feature requested by @Gabriel Torres. Next on the update list will be better member filtering and support for taking actions against members with disposable e-mails in bulk. Also, if you've been enjoying the application so far, please consider giving it a review! It'll help me a ton and I'd be very thankful ヾ(＾-＾)ノ

Another login handler bug when attempting to delete members before the application is configured, Call to a member function link() on null in the member.php hook.

Another bug to report: Attempting to uninstall the application before configuring the application/login handler results in an error that both breaks the application and prevents it from being uninstalled:

I've been talking with the Kickbox team and there shouldn't be any rate limiting causing Kickbox to return the null responses that we're seeing in our server logs. So I'm going to add some extra logging to the next release and see if we can't narrow down the cause of the issue there. Like mentioned above though, it won't cause the application to stop working and it only seems to occur when running the reindex tasks, but I'd still like to prevent it from occurring at all if possible.

Small bug to report: When using \IPS\nexus\Support\Request notifications, the Discord bot sends the links as frontend links instead of AdminCP links (that is, they send the links for the person who created the support request (the user) which will return an error, not the links for administrators to view/respond to the ticket).

My end-goal might be to just integrate with the Members listing page instead of essentially replicating it in the application itself. This way you'll be able to filter by disposable members there, and use IPS' native tools to prune members with disposable E-mail's all at once if you'd like (which would take care of suggestion #3). @AlexJ Do you think a solution like that would work for you?

Release 1.1.0 uploaded which adds support for the above. Next release will implement sorting forums by topic reputation, https://dev.taiga.sh/ips/topic-reputation/issues/2

Next release should add support for calculating the total reputation earned by a topics author, instead of just relying on the first post: https://dev.taiga.sh/ips/topic-reputation/issues/1

Logged the above request here: https://dev.taiga.sh/ips/Indisposable/issues/6 I'll also be implementing support for requesting/requiring members change their e-mail if they're using a disposable address in 1.2.0, https://dev.taiga.sh/ips/Indisposable/issues/1 I plan to hopefully have this out by next week, but if you have any other ideas or run into any issues before then, be sure to let me know and I'll see if I can work them in to the release schedule! https://dev.taiga.sh/ips/Indisposable/milestones/2

@Gabriel Torres Awesome! Glad to see it's helping you out so much! Thanks again for the feedback, that sounds like a good idea! I'll add IP logging as a feature to implement in the next release.

Profiles on IPS have virtually no meta tags, at all. This could be improved by adding a link to the users avatar and maybe a general description line like so, $description = "Explore {$this->member->name}'s " . \number_format( $this->member->member_posts ) . " posts on " . \IPS\Settings::i()->board_name; $newMeta = [ 'title' => $this->member->name, 'description' => $description, 'og:title' => $this->member->name, 'og:description' => $description, 'twitter:description' => $description, 'og:image' => $this->member->photo, 'profile:username' => $this->member->name, 'og:url' => $this->member->url() ]; \IPS\Output::i()->metaTags = array_merge( \IPS\Output::i()->metaTags, $newMeta ); Otherwise links to profiles contain no description or anything aside the default og:image if you have one set in the settings.