covertformula

This issue has now been fixed in version 7.5.1 – Thanks!

This issue has now been fixed in version 7.5.1 – Thanks!

@mazedulislamkhan try using a larger feature image in the region of say 1920×1000 pixels and then you will see the issue I think.

@benvaassen I’ve downgraded back to 7.2 now as this is a live site which needs to work when shared with social media.

Based upon what others are saying about this issue it seems like the problem is all round the image size… if your feature image size is larger than a ? then the og:image tag is omitted.

This needs to be fixed ASAP.

I’ve gone back to version 7.2 until you get your act together regarding the og:image tag. There is enough people now reporting issues around this for you to get it sorted.

Same issue here and its still not fixed in 7.4.2

It was all working in version 7.2

Just upgraded to 7.4.2 from 7.4.1 and this tag og:image still does not output. It was all working at 7.2 its really annoying!

Is it possible to downgrade back to 7.2 ?

@dwinden

Disabling the Schedule Database Backup was good enough as all backups are done via WHM and I needed this site up and running ASAP. It’s not the first time I’ve seen this either both on my own sites which all have iThemes Security installed but other WP sites as well.

I really hope the guys over at iThemes Security look into this problem and if nothing else hope that this post will help others save a whole lot of time trying to figure out what is causing this allowed memory exhausted error!

@dwinden

No its still disabled… and if I take all of the tables the rows do not even add up to 3000 with the largest one being 958 rows.

My initial problem is all sorted now by disablling iThemes Scheduled backups…

The memory leak was a bit of an issue to track down to iThemes, so I do hope they take this report seriously and investigate further.

To help iThemes further this is one of the call stacks:

Call Stack
# Time	Memory	Function	Location
1 0.0003 296952	{main}( )	.../admin.php:0
2 0.0004 313728	require_once( '/public_html/wp-load.php' )	.../admin.php:31
3 0.0005 323944	require_once( '/public_html/wp-config.php' )	.../wp-load.php:37
4 0.0008 426560	require_once( '/public_html/wp-settings.php' )	.../wp-config.php:83
5 0.1723 31900464	do_action( )	.../wp-settings.php:393
6 0.1903 33137640	call_user_func_array:{/public_html/wp-includes/plugin.php:525} ( )	.../plugin.php:525
7 0.1903 33137888	ITSEC_Backup->do_backup( )	.../plugin.php:525
8 0.1905 33138928	ITSEC_Backup->execute_backup( )	.../class-itsec-backup.php:99
9 1.1578 49792552	wpdb->get_results( )	.../class-itsec-backup.php:202
10 2.2055 536575800	array_values ( )	.../wp-db.php:2341

Thanks @dwinden

That’s exactly what we did (turned off scheduled backups) and it all works now!

But there is clearly a problem as looking at the total size of the tablets it only adds up to just over 3MB…

So not going to be using scheduled backups using iThemes Security as they do not work and cause memory leaks as indicated by xdebug!

Thanks