[Resolved] Types 3.3.11 issue with imsanity plugin

[Author]

Posts

[bobA-2]

After upgrading to Types 3.3.11 I get error upon saving or updating post. Seems to be issue with the imsanity plugin https://wordpress.org/plugins/imsanity/

My guess tied to the update: Significant performance improvement when saving posts with a large number of images in custom fields perhaps? Downgrading to 3.3.10 fixes the issue.

/httpdocs/wp-content/plugins/imsanity/settings.php.
Uncaught ArgumentCountError: Too few arguments to function
imsanity_adjust_default_threshold(), 1 passed in
/httpdocs/wp-includes/class-wp-hook.php on
line 287 and exactly 3 expected in
/httpdocs/wp-content/plugins/imsanity/settings.php:537
Stack trace:
#0 /httpdocs/wp-includes/class-wp-hook.php(287):
imsanity_adjust_default_threshold(2560)
#1 /httpdocs/wp-includes/plugin.php(206):
WP_Hook->apply_filters(2560, Array)
#2 /httpdocs/wp-content/plugins/types/vendor/toolset/types/embedded/includes/fields/image.php(36):
apply_filters('big_image_size_...', 2560)
#3 /httpdocs/wp-includes/class-wp-hook.php(289):
WPCF_Fields::{closure}('')
#4 /httpdocs/wp-includes/plugin.php(206):
WP_Hook->apply_filters('', Array)
#5 /httpdocs/wp-content/plugins/types/vendor/toolset/toolset-common/toolset-forms/classes/clas

[coriP]

Similar errors when using WP Smush: https://wordpress.org/plugins/wp-smushit/

Fatal error: Uncaught ArgumentCountError: Too few arguments to function Smush\Core\Core::big_image_size_threshold(), 1 passed in /public_html/wp-includes/class-wp-hook.php on line 287 and exactly 4 expected in /public_html/wp-content/plugins/wp-smushit/core/class-core.php:662 Stack trace: #0 /public_html/wp-includes/class-wp-hook.php(287): Smush\Core\Core->big_image_size_threshold(2560) #1 /public_html/wp-includes/plugin.php(206): WP_Hook->apply_filters(2560, Array) #2 /public_html/wp-content/plugins/types/vendor/toolset/types/embedded/includes/fields/image.php(36): apply_filters('big_image_size_...', 2560) #3 /public_html/wp-includes/class-wp-hook.php(289): WPCF_Fields::{closure}('hidden link...') #4 /public_html/wp-includes/plugin.php(206): WP_Hook->apply_filters('hidden link...', Array) #5 /public_html/wp-content/plugins/types/vendor/toolset/toolset-common/toolset-forms/classes/class.types.php(359): a in /public_html/wp-content/plugins/wp-smushit/core/class-core.php on line 662

UPDATE: After further testing, I disabled WP Smush and the issue still occurred. Rolled Types back to 3.3.10 and issue was fixed.

New threads created by Jamal and linked to this one are listed below:

https://toolset.com/forums/topic/types-3-3-11-issue-with-smush-plugin/

[Jamal]

Hello and thank you for contacting the Toolset support.

I'll try both plugins locally and get back to you with my findings very soon.

[Jamal]

I confirm both plugins generate fatal errors with Toolset Types when saving a post that has image custom fields, I was trying with a simple image field and a repeatable image field.

Let me escalate these issues to our 2nd Tier and get back to you as soon as possible.

However, for support rules, we are able to handle only one issue at the time. This helps us to bring you a better service and also helps other users to find all the information here exposed. For that reason, I have created another ticket to track the resolution of the conflict with Smush plugin.

[Jamal]

This ticket is now escalated to our 2nd Tier for further analysis. I'll get back to you as soon as possible.

[Jamal]

Our developers have found a fix for this issue and an erratum containing a patch has been published here https://toolset.com/errata/fatal-error-in-image-optimisation-plugins-when-using-types-3-3-11/

I tested the patch for Imasinity plugin and it is working without issues. Please test on your site and let us know. Take a backup for security measures.