Recent content by Sim

Take a look at the XF\Service\User\UserGroupChangeService ... this core service allows you to define a usergroup change that applies to a user or group of users - and then removing users from that usergroup is as simple as removing the usergroup change - either for an individual user, or for a...

That's nearly 5%, which is pretty huge. If you aren't immediately removing those emails from your mailing list, you will be hugely damaging your sending reputation. Continuing to send emails to previously bounced, rejected, blocked or otherwise, email addresses is a sure sign of abuse (at your...

Yes. You might also want a general permission for your library to allow you to hide the log UI completely from admins who can't see any logs - you'd set that in the admin navigation entry for your log UI.

You're already creating a dependency between the addons - so just create the permissions (normally) at the addon level rather than the library level. Then create a code event in your library that addons can hook into (via a code event listener) to register the relevant permission key from the...

You're making a huge assumption that the phrase "lifetime" refers to the life of an individual person. It does not say that. Indeed, if you read the Cloud service agreement - which is the definitive source of truth on this matter, the language is very clear: "For the duration of your...

I think you're trying to solve a problem that doesn't really need to be solved - I don't understand your use-case. Exactly who are you going to be giving permissions to? Admin permissions are intended to be high-level rather than fine-grained (like moderator or user permissions). Are you...

Yes, if you're a small sender, you'll need to use a shared IP - but given that ESPs reply on their ability to be able to send emails, they tends to be far more strict about keeping the reputation of their IP addresses in good order, compared to hosting providers. Hint: don't use an ESP who isn't...

Using your hosting providers SMTP server is never a good idea these days - it is shared with all the other senders using that provider and you can almost guarantee that some of the users are abusing email sending - either deliberately or because they don't know what they are doing. You really...

What email provider are you using to send emails? 450 4.7.1 errors are related to reputation - the receiving servers are rejecting your emails because your sending reputation is bad.

Believe it or not - they've been pretty open about the fact that the way their network operates, it is actually very beneficial to them to have their freemium model due to their scale. Something to do with network transit costs I believe. I can't find the article written by someone from...

Common problem lately - AI bots and other badly behaved bots. If you haven't already - you should install @digitalpoint 's excellent App for Cloudflare https://xenforo.com/community/resources/digitalpoint-app-for-cloudflare-r.8750/ As for blocking - you want to start by identifying patterns...

Or you could use Monolog which is pretty much an industry standard with the ability to link into a huge number of external systems for log tracking. I built an addon for it: https://xenforo.com/community/resources/monolog-logging-service.6080/

I created some very basic Symfony Console commands using v7.3 and v5.4 and they both worked as expected. It seems to be something specific to the way things are set up with XenForo?

I just built a Laravel 12 app and it all works fine - noting that Laravel takes a very different approach to the Cli environment and has a lot of layers on top of the underlying Symfony command. Laravel also uses Symfony Console v7.3, whereas XenForo v2.3 uses Symfony Console v5.4 ... which...

Okay - so here's a weird edge case I haven't been able to work out yet. I'm building an addon. This addon uses a composer package. The composer package has a trait. I want to "use" that trait from the composer package in one of my commands. Adding the "use" clause causes the XenForo command...