@iparr I believe this is 100% valid. I’ll make it do errors only display in DEV via the twig variable output.

In anything other I’ll just error to log file.

@iparr I've finally got a chances to push changes to the plugin I made this morning tagged v1.1.3.

It comes with better sub prop handling, if the property is missing, as well as a new valid methods as a TWIG variable and new method on the field. See README for more information.

I've tested this and it's allowed me check for valid oEmbeds in a much nicer way. Thanks! Great work.

Thanks for the issue report and glad it’s working for you now. 👍

Hey, I think this has regressed or alternatively I've misunderstood something.

I have invalid fields that I'd like to test for in Twig.

I'm using:

{% block.embed.valid %}
…

or {{ block.embedId.valid }} or {% if craft.oembed.valid(block.embedId.valid) %}… and both still result in errors.

So how is best to test for valid fields on the front-end?

I would like this re-opened if possible @reganlawton

I'm still not sure how to test for embeds that are invalid.

For example, when a URL like this https://thesludgelord.bandcamp.com/album/metal is rendered invalid because an owner removes it, then my website breaks with a Caused by: Embed\Exceptions\InvalidUrlException error.

How is best to combat this?

I'll have to look into this I've been smashed lately when investor deadlines but have a few tweaks needing to be done to the application

@iparr I have updated the handling a bit better if you want to take a look at this in the latest v1.3.9

Sorry, if I use it with the same example as above, I still get:

Serialization of 'class@anonymous' is not allowed
↵
Caused by: Embed\Exceptions\InvalidUrlException
Invalid url 'https://thesludgelord.bandcamp.com/album/metal' (Status code 404)