Recent content by mattrogowski

Controller Plugins sort of act like traits for shared behavior in controllers, and Entity Behaviors allow for shared behavior on saving and deleting. For other uses you can just use traits.

I don't believe this is supported, no. We don't have any plans to disassociate the donations from a campaign, but the goals are optional. The campaigns are simply the way the donations are listed, there has to be some way to display them. I'm not sure what the real world difference would be...

Definitely not a good idea considering 7.4 has been totally unsupported by PHP since November 2022. That's one very significant reason to upgrade. This line of thinking is also what keeps people using very old versions forever, which holds developers back from being able to use newer PHP...

We no longer update our addon resources here, if you use our Install and Upgrade addon it should notify you of newer versions in your Admin CP for any addons you have a licence for on your account.

Hm, it shouldn't do, XF responds with a 200 OK status when logging this error so as far as Stripe is concerned it's been accepted. Check the Stripe webhook logs to see which ones returned an error response and what the status and message body was.

All a webhook is is a HTTP request to the specified URL - it has no semantic understanding that a particular payment is only relevant to one of the sites it notifies. Each event in Stripe isn't linked to a specific webhook URL, so it will notify them all for all events. So Stripe isn't doing...

There is a bug with the moderator log entry, when logging out of the account you logged into as. The user_id column in xf_moderator_log gets set to the currently logged in user ID, which then stores the log as being performed by that user. This means when you go to the moderator log in the ACP...

Ah I didn't notice the ID in there, it seems to be related to deleting a node and having a stale thread in the database, so that makes sense, thanks.

Tried searching but ironically there were no matches 🥁 ... Anyway, as of earlier today I've been seeing these errors logged by the hourly similar threads rebuild: XFES\Elasticsearch\RequestException: Elasticsearch error: No query registered for [match_none]...

Out of interest, why would you stop using the theme because it requires a helper addon? 🤔

Yes, that's where they're designed to show as there's limited space to show it anywhere else. The HTML for the avatar is around line 243 of the thfeature_macros template, you'd need to play around with restructuring this HTML so that message-avatar site alongside message-userDetails.

Can you upload a more complete screenshot of that page? I'm not sure what theme you're using but I can't see anywhere by default that has an avatar that small where it is there. To make them circular, edit thfeature.less, around line 43 remove .avatar {border-radius: 0;}

You would be able to do that theoretically, yes. The plugin only deals with posts as it creates the associated thread, and as you say pages don't have comments - even if comments were added though the plugin wouldn't attempt to create a thread, or an associated page node either. But the way...

Unless I'm misunderstanding what you mean by "widget"... It's only posts that are supported with the iframe, the WP post is linked to the thread and it iframes the comments. There isn't currently support for any integration with pages between WP and XF.

So this isn't a widget for the front end, this is just the meta box on the post composition page that you use to configure the thread when the post gets created. The UI you have here is just WordPress letting you control which meta boxes display when you create a new post.