After updating to Yoast SEO/Premium 7.4, a warning message is showing on customer's site:
Warning: Illegal string offset 'url'in /home/*/public_html/wp-content/plugins/wordpress-seo-premium/frontend/class-opengraph-image.php on line 151*
$image_url = trim( apply_filters( 'wpseo_opengraph_image', $attachment['url'] ) );
This message seems to be showing on pages where an image is uploaded but I could not reproduce the issue yet.
The same issue is reported in forums: https://wordpress.org/support/topic/version-7-4-breaks-site/
No error/warning message showing.
Unable to reproduce yet but customers reporting the issue said that the warning message is showing on pages with images.
Reverting to 7.3 fixed a customer's issue.
Please inform the customer of conversation # 355333 when this conversation has been closed.
Please inform the customer of conversation # 355227 when this conversation has been closed.
@tacoverdo
Per your request, uploaded code for page displaying this issue. It affects every page as far as I can see, so I'm just uploading the home page source code.
Please inform the customer of conversation # 355148 when this conversation has been closed.
Please inform the customer of conversation # 355131 when this conversation has been closed.
Please inform the customer of conversation # 355486 when this conversation has been closed.
Can confirm that I am seeing this issue as well
Please inform the customer of conversation # 355213 when this conversation has been closed.
Please inform the customer of conversation # 355215 when this conversation has been closed.
Please inform the customer of conversation # 355294 when this conversation has been closed.
Please inform the customer of conversation # 355782 when this conversation has been closed.
Please inform the customer of conversation # 355812 when this conversation has been closed.
Same problem here.
Closed in #9612.
Same Problem here!
Yoast Seo Premium Version: 7.4.2
7 days and still broken
We have discovered a situation when unexpected arguments are being passed, this error occurs.
This should be fixed in the upcoming release of 7.5 (#9667)
Most helpful comment
We have discovered a situation when unexpected arguments are being passed, this error occurs.
This should be fixed in the upcoming release of 7.5 (#9667)