Recent content by Jeremy P

Yeah, this was fixed shortly after the release unfortunately. A workaround is offered above.

It does for pages (ie. page 2+ of a long thread). You can place this line before the <title> one: <xf:page option="pageTitle" value="{{ page_title()|to_upper('ucwords') }}" />

You can assess whether you have an unexpected influx of visitors/bots, a poorly optimized database server, or potentially add-ons which introduce suboptimal queries. If you’re using a shared host, they may be able to assist by looking over log data.

This is a server resource limit. It’s worth assessing whether you have an unexpected influx of visitors/bots, a poorly optimized database server, or potentially add-ons which introduce suboptimal queries.

You can remove hard-delete permissions from staff, in which case they will only be able to soft-delete content. You can also remove the 'Manage nodes' permission from administrators to prevent them from being able to remove a node.

You can edit the PAGE_CONTAINER template. I think replacing the existing line with the <title> tag with this would do what you want: <title><xf:title formatter="%s" fallback="{$xf.options.boardTitle}" page="{$pageNumber}" /></title> Then you can edit the title_page_x phrase to swap the | for an -.

Actually, in lieu of the earlier file, I think if you drop in this one (to js/xf/attachment_manager-compiled.js) it should work in the meantime: https://xenforo.com/community/js/xf/attachment_manager-compiled.js?_v=7d806492

Away from my desk for the night but I can see about uploading a quick fix tomorrow.

Yeah, it happens anywhere you upload a JPEG I think. The JS file change was a hotfix that has since been reverted in favor of a proper fix.

Duplicate: https://xenforo.com/community/threads/resource-manager-not-able-to-attach-image.221930/

Yeah, I think AVIF might but I believe encoder/decoder support for it was lacking last I checked.

It tends to make performance worse overall as it increases the initial network payload, which is detrimental in the same situations the effect is otherwise useful.

Something I have in my notes for future ideas is a BBCode renderer geared specifically towards search indexing, which opens the door to many improvements like this. Right now I think we index the BBCode itself, markup and all.

Yep, but we prefer the Open Graph description if it’s set as that’s typically what it’s there for. Most all platforms do the same: IMDB just happens to fumble this: <meta property="og:description" content="1h | TV-MA"/>

This isn’t really about where the files are stored, it’s about what origin they’re served from. Browsers require SVG <use> elements to be served from the same origin, and they actually lack support for CORS entirely. If you can proxy the requests elsewhere from your web server, you’re free to...