This PR fixes #147. The issue was caused because the $entry->seo_social_images_theme field was requested on routes where it isn't added to the blueprint. We are resolving this issue by only adding to the preview targets when it's actually needed, at which point the field has been added to the blueprint as well.
This PR fixes #147. The issue was caused because the
$entry->seo_social_images_themefield was requested on routes where it isn't added to the blueprint. We are resolving this issue by only adding to the preview targets when it's actually needed, at which point the field has been added to the blueprint as well.