It's the same as other callbacks in XenForo in that it only accepts a static method. You're passed the \XF\Widget\PhpCallback instance as an argument and expected to return a string, so you could rewrite your class with that in mind. However if it's for an add-on and the widget is meant to be...
Sure:
{{ date(date_from_format('U', $thread.FirstPost.last_edit_date, 'UTC'), 'c') }}
Though I would note the structured data testing tool seems to show it all gets picked up without issue as-is:
https://search.google.com/test/rich-results/result/r%2Fdiscussion-forum?id=zqnAwb-wrnkebG8fuGJ9RA
Unlikely, search engines are pretty smart. The interface is presented in the local time-zone (or guest time-zone), but those are provided with time-zone information as well. For example from this thread, 2025-06-06T20:39:28+00:00 and 2025-06-06T13:39:28-0700 are equivalent from the perspective...
The JSON+LD schema dates are always in UTC, and include time-zone information so they can be adjusted back into any timezone as necessary by schema consumers. This applies to datePublished as well.
Actually, looks like there might still be some issues there unfortunately :( It still seems to select the parent container and so forth in our testing. There might be some other tricks we can apply here though (like applying it more broadly for the touchhold duration as you say). We'll have to...
Nobody ever replied to confirm, but a fix for a similar issue was rolled out here a while back:
https://xenforo.com/community/threads/reaction-issue-on-android.228554/post-1738866
It's not always easy to ascertain if issues are duplicates or different bugs with similar symptoms. Can anyone...
The fallback page uses the same code/macro as the menu, which is pretty convenient. We could split them in theory, I guess, but it doesn't really seem worthwhile when it's only 4 URLs without the token. The (fallback/GET) URLs for each variation are noindex too in 2.4.
To be honest, I'm not...
Yeah, most of the value proposition of WebP is that its lossy compression is quite good on average (though individual results can vary, of course).
Whether a WebP is lossy or not is stored in the file but it's not exposed to us via GD or Imagick so we have no way of knowing currently (beyond...
100% compression means to minimize compression as much as possible but is a distinct concept from lossless compression. GD did not introduce support for lossless WebP until PHP 8.1 so it's not something we've supported there in XF 2.3. ImageMagick automatically enables lossless compression if...