exposer with media embed or native joomla 4

Hi Marco
I started to switch sites to joomla 4.
Until now I put custom fields: econa, acf youtube .... as thumbnail.
With joomla 4, I can finally use the native embed code: youtube, pdf, soundcloud ....
How to make the thumbnail take the native content of joomla 4?
category with module: https://v2.clibre.eu/fr/infos-sur-le-libre
article with image: https://v2.clibre.eu/fr/infos-sur-le-libre/expolibre
article with video: https://v2.clibre.eu/fr/infos-sur-le-libre/si-c-est-gratuit-vous-etes-le-produit
If necessary I can give access?
regards

Hi Marco
+1
Thanks

Hi herve

Sorry have forgotten to post my answer :-)

you are talking about "native" j4 embed code?

I'm sorry but i don't know that j4 offers this features. Can you give me a source / info where to find these options in the backend?

kind regards

​

Marco

Hi Marco
On https://www.youtube.com/watch?v=yt8ipm-HN1E ~19 mn
This means that video files: youtube or other pdf, souncloud can be integrated natively (joomla 4).
This opens up a lot of possibilities so that extensions don't need to be compatible with a lot of extensions.
I'm just working with a plugin like https://onlinecommunityhub.nl/joomla-extensions/ochfitvids to make sure that media embeds or iframes are rendered responsive.
I sent the access by mail

Regards

Hi Marco

+1

Thanks

Hi herve

Unfortunately I don't have so good news for you. I have tested the whole thing for a few days now - the problem is this new feature refers to content IN the article (i.e. in the article body). The problem here is that Exposer, to show the image / video / map etc. has to search the content - for every single TAG. And yes of course it works - but the load time of the page would increase (based on the type & structure of the content) by a multiple - Already in some simple tests I had load times that were no longer acceptable and the searched content was placed relatively "far up" in the article.... It simply takes too long for the server to scan the content, then the resource (URL) has to be extracted, processed and displayed in the exposer. The whole thing not only sounds complex - it also takes forever - and to be honest, the error-proneness is quite enormous.

​

In short, this cannot be implemented at the moment - we will have to continue using third-party custom fields - but I'll keep at it, maybe I'll come up with a good idea in this context.

​

Sincerely

Marco

Hi Marco
ok I understand.
I hope you will find a solution, I am also looking for

Regards