Recent content by PaulB

As of XenForo 2.2.15, the first issue addressed by the patch file above has not been fixed, but the second issue has been fixed.

That's not a new bug. Some of the more popular ad blocking rulesets prevent the cookie dialog from showing. Disable your ad blocker and it'll resolve itself. It's probably best if the "Cookies" link just sends people to the full page rather than showing the cookie popup. Existing bug report...

This is just a small patch for PHP 8.3 compatibility issues that we've encountered so far. Notably, XF\BbCode\Renderer\Html attempts to increment a bool in a couple places, a stopSmilies and stopBreakConversion can be either bools or ints. It's not clear to me why they would ever need to be...

A coworker told me your meme was better than mine. Now I have to take you out--there can only be one.

@Paul B vs. @PaulB

Actually doing that in a way that wouldn't require a full XF update would require breaking changes to how XF handles updates in general, so I don't think we're going to see that on 2.x. Media site changes are infrequent enough that they might as well just be bundled alongside all the other...

Add-ons are effectively the way to go about that. You can also put the site in debug mode if you want to do it by hand, or you can manually edit them in the database. Using an add-on ties your updates to the add-on dev, whereas updating the vanilla entry keeps you on the XF update path...

I would caution against creating a duplicate media site as a workaround; that has long-term side effects that may not be immediately obvious: You can never delete the media site without breaking existing posts You now have to maintain a second media site by hand instead of relying on updates...

We're starting to see Twitter links that use x.com instead of twitter.com posted on our forums, despite the fact that x.com redirects to twitter.com. The "Share" button on tweets now gives an x.com URL. As such, match_urls should be updated to include x.com. Other XF customers also appear to...

Can you provide a full stack trace? resolveExtendedClassToRoot is being called too early; that’s most likely a bug in an add-on. It can’t be called before extendClass.

No; the of self constraint indicates that T must be self or a subclass thereof. Type constraints with template parameters would be useless otherwise.

XFES doesn't use Elasticsearch's GeoIP features. If you're exclusively using XFES (and not putting, say, access logs in Elasticsearch), you can simply disable GeoIP updates.

Some clarifications: ES needs you to keep a big chunk of RAM free so that the kernel can use it as a filesystem cache. That's "buff/cache" in the first post. The recommendation to set the heap size to half your RAM assumes that you have a system that's just running ES, and that you have a...

\XF\Pub\Controller\Conversation::assertViewableMessage, lines 1130 through 1141: protected function assertViewableMessage($messageId, array $extraWith = []) { $extraWith[] = 'Conversation'; $visitor = \XF::visitor(); if ($visitor->user_id) { $extraWith[] =...

Yes: there's a constant stream of security vulnerabilities being found in PHP. These days, most are relatively minor or don't impact XenForo, but eventually we'll see another big CVE that affects old PHP versions. As far as I can tell, there aren't any new breaking changes that are likely to...