Venkat Raj

Hi @oriver

Thanks for using our plugin.
Yes, we use following meta key to store compression data in postmeta table.
smush-complete
smush-info
smush-marked
smush-stats

Following are not used:
wp-smpro-smush-data
wp-smush-resize_sizes

Meta value for smush-info always ends with using WP-Optimize

Meta value for smush-stats will have something like a:5:{s:12:"smushed-with";s:11:"re-smush-it";s:13:"original-size";i:117556;s:12:"smushed-size";i:72925;s:15:"savings-percent";d:37.97;s:10:"sizes-info";a:6:{s:4:"full";a:2:{s:8:"original";i:117556;s:10:"compressed";i:72925;}s:6:"medium";a:2:{s:8:"original";i:9648;s:10:"compressed";i:8275;}s:5:"large";a:2:{s:8:"original";i:47706;s:10:"compressed";i:41647;}s:9:"thumbnail";a:2:{s:8:"original";i:4795;s:10:"compressed";i:4004;}s:12:"medium_large";a:2:{s:8:"original";i:32330;s:10:"compressed";i:28448;}s:9:"1536x1536";a:2:{s:8:"original";i:82451;s:10:"compressed";i:70608;}}}

Hi @oghustler

We sincerely apologies for what happened and that your site went down.

The crash happened for some sites who use caching functionality and
when updating from version 3.2.3 to 3.2.4 using auto update feature.

As soon as we are aware of the problem, we released the
fix in version 3.2.5 same day.

That said, we have reviewed our testing process to make sure releases work in
every environment to ensure it never happens again.

Hi @greghl

We sincerely apologies for what happened and that your sites went down.

The crash happened for some sites who use caching functionality and
when updating from version 3.2.3 to 3.2.4 using auto update feature.

As soon as we are aware of the problem, we released the
fix in version 3.2.5 same day.

That said, we have reviewed our testing process to make sure releases work in
every environment to ensure it never happens again.

Hi @vmaniscalco

We sincerely apologies for what happened and that your site went down.

The crash happened for some sites who use caching functionality and
when updating from version 3.2.3 to 3.2.4 using auto update feature.

As soon as we are aware of the problem, we released the
fix in version 3.2.5 same day.

That said, we have reviewed our testing process to make sure releases work in
every environment to ensure it never happens again.

Hi @verdun

We sincerely apologies for what happened and that your site went down.

The crash happened for some sites who use caching functionality and
when updating from version 3.2.3 to 3.2.4 using auto update feature.

As soon as we are aware of the problem, we released the
fix in version 3.2.5 same day.

That said, we have reviewed our testing process to make sure releases work in
every environment to ensure it never happens again.

Hi @mrromo

We sincerely apologies for what happened and that your site went down.

The crash happened for some sites who use caching functionality and
when updating from version 3.2.3 to 3.2.4 using auto update feature.

As soon as we are aware of the problem, we released the
fix in version 3.2.5 same day.

That said, we have reviewed our testing process to make sure releases work in
every environment to ensure it never happens again.

Hi @timsthailand

We sincerely apologise for what happened and that your site went down.

The crash happened for some sites who use caching functionality and
when updating from version 3.2.3 to 3.2.4 using auto update feature.

As soon as we are aware of the problem, we released the
fix in version 3.2.5 same day.

That said, we have reviewed our testing process to make sure releases work in
every environment to ensure it never happens again.

Hi @craigunett9999

We sincerely apologise for what happened and that your site went down.

The crash happened for some sites who use caching functionality and
when updating from version 3.2.3 to 3.2.4 using auto update feature.

As soon as we are aware of the problem, we released the
fix in version 3.2.5 same day.

That said, we have reviewed our testing process to make sure releases work in
every environment to ensure it never happens again.