It's created by XenForo and it's not used otherwise. A file is created when the data is fetched from the oEmbed (YouTube's) server, I assume they get pruned automatically but I don't know how/when it happens.update. just realized that the oembed folder on my b2 bucket is now full of thousands of json files. are these also being used on every youtube embed? or they are just created by xenforo by default?
You'd have to manually editIs there any easy fix for the twitter embeds not working in the xF1.5 version? I'm soon upgrading to 2.x but just wondering if there was a temporary fix?
MediaBBCodes.php
and replace ?autoplay=false
with ?autoplay=false&parent=example.org
where example.org is the full hostname for the page that displays the embed. If you have other issues with the XF1 add-on please do post in the corresponding thread. https://xenforo.com/community/resources/s9e-media-bbcodes-pack.2476/i do wonder though. the embed code provided by twitter itself does not ask for your domain name. so how does that work? i assume this is connected to that CSRF thing?parent=example.org
That's weird, it looks like it's missing some of the CSS. Try disabling/reenabling both click-to-load option, see if it fixes it?on videos with long titles, the title goes out of the view.
I read that as Twitch. I think @OUTL4W was talking about Twitch, whose latest update requires the full hostname of every parent frame. Twitter should work fine afaik.i do wonder though. the embed code provided by twitter itself does not ask for your domain name. so how does that work? i assume this is connected to that CSRF thing?
Witnessed.@Xon Do you mean that in theory or is that something you witnessed after enabling it in the add-on? If that's something that happened on your board, what was the approximate number of current users?
internal_data
is handled by the plugable filesystem stuff XenForo has and the custom code on that site, but I'ld need todo more investigating.XF\Service\Oembed::fetchNewOembed
, which always fetches data from the source instead of hitting the cache. XF\Service\Oembed::getOembed
looks to be what you want to callfetchNewOembed
after checking the database so unless the Oembed service deletes rows in the database but leaves cache files on disk, it should generally be alright if I read it correctly. It does however allow for the possibility of a race condition in v2.6.1 where the database could be updated between fetches. In v2.6.2 there's only one fetch per page.getOembed
does check for concurrency across processes whereas fetchNewOembed
doesn't so that part could make a big difference under heavy traffic.I retraced how theI'm actually unsure why XF bothers storing it on disk. The entire record needs to be fetched from the DB, and the oembed data should be fairly small...
XF:Oembed
service works. I was operating on the assumption that the files on disk were only used temporarily and that the database was the real repository. In actuality, the oEmbed data is always stored in files and the database is only used to store logs. Since I only use data from the logs, that means the oEmbedCacheTTL
setting doesn't really matter for my use case and only the oEmbedLogLength
setting should be set to a high number, or 0 to keep logs indefinitely. XenForo's hourly cleanup is in charge of pruning the cache and logs.oEmbedCacheTTL
(7 days) to reduce the number of files on disk over time and set a large value for oEmbedLogLength
. The default is 90 days, it could be extended to a year or even be kept indefinitely.The add-on's CSS has been updated to correctly handle long titles.
The oEmbed logic has been updated to limit the number of concurrent fetches to prevent resource exhaustion. The number of fetches is limited to 1 per page, with a maximum of 3 concurrent fetches across processes.
This is a recommended update if you use the click-to-load feature with oEmbed enabled.
oEmbed media cache lifetime
could be a smaller number of our preference. oEmbed media log length
should be as high as possible (0 preferred). oEmbed media cache refresh
is irrelevant. Right?config.php
file has any option to change the location of the oembed_cache
folder! manual does not mention any setting for this amongst other folders that should logically be kept on internal storage! (sitemap comes to mind).We use essential cookies to make this site work, and optional cookies to enhance your experience.