shanemac10

@kimmyx Just to let you know, I will not be creating a support ticket. Everything you need is above.

@kimmyx

Currently using 1.20.4 of your plugin, which is the most current version. If you’re not seeing it then can you confirm you have debugging turn on in your wp-config.php file? Like this…

// if ( ! defined( 'WP_DEBUG' ) ) {
// 	define( 'WP_DEBUG', false );
// }
if ( ! defined( 'WP_DEBUG' ) ) {
	define( 'WP_DEBUG', true );
	define( 'WP_DEBUG_LOG', true );
	define( 'WP_DEBUG_DISPLAY', true );

	error_reporting(E_NOTICE);
}

It looks like the problem is on line 393 in popup-maker/classes/Utils/Array.php. The error message is pretty clear what the problem is:

Deprecated: uasort(): Returning bool from comparison function is deprecated, return an integer less than, equal to, or greater than zero

public static function sort_by_sort( $a, $b ) {
    return $a['sort'] > $b['sort'];
}

Looks like you should change it to the PHP Spaceship operator like this…

public static function sort_by_sort( $a, $b ) {
    return $a['sort'] <=> $b['sort'];
}

• This reply was modified 1 month ago by shanemac10.

I think I found the bug. It looks like this plugin calls update_post_meta, even if there had been no change. WordPress seems to have a bug where it returns false if there was an error OR if the value was the same and therefore not updated, and the AJAX function WP_REST_Meta_Fields::update_meta_value that calls the update_metadata function that treats any false as an error, and then throws an actual error as a result. This “Safe SVG” plugin should update to check if there is a difference in meta value before calling the update_post_meta, so to not trigger the WordPress bug.

/**
 * Save featured image meta data when saved
 */

function bodhi_svgs_save_featured_image_meta( $post_id, $post, $update ) {

	// if gutenberg is active, disable the classic editor checkbox
	if( isset($_REQUEST['hidden_post_status']) ){

		$value = 0;
		if ( isset( $_REQUEST['inline_featured_image'] ) ) {
			$value = 1;
		}

		// Check if post type supports 'thumbnail' (Featured Image)
		if ( post_type_supports( get_post_type( $post_id ), 'thumbnail' ) ) {

			// set meta value to either 1 or 0
			update_post_meta( $post_id, 'inline_featured_image', $value );
                        // ^^^ I believe this is the culprit

		}

	}

}


add_action( 'save_post', 'bodhi_svgs_save_featured_image_meta', 10, 3 );

• This reply was modified 9 months, 3 weeks ago by shanemac10.

@shayleehansen30 Please see above fix, and communicate the bug with the developers so they can fix accordingly. This is an issue with the NF code calling a function that may not exist, without checking first.

@haslien Thank you for doing the legwork on that. I can confirm that this works, and looks to be an appropriate solution.

Go to: wp-content/plugins/ninja-forms/assets/js/min/front-end.js
Find: currentValue.trim()||(t=!1);
Replace with: currentValue&&currentValue.trim?currentValue.trim():(t=!1);
Save the updated front-end.js file, and then clear any site caching you may have in place, then clear your browser cache to re-test the form.

@cookieyesteam

Just wanted to let you know that I have not seen a response from my support ticket. The client reached out through our client manager, and they received an email about a new account with Mozillor Limited/ CookieYes Limited, but there has not been communication about what is going on.

If it were just an issue with CookieYes settings, it sure would have been nice if you could communicate which ones to look at here, because I sure didn’t see any that looked off, (and it’s not like there are a lot of them).

We have already purchased a Mandatly subscription to replace CookieYes.

You all can consider this ball dropped!

@cookieyesteam

Thank you. I have submitted a ticket through the Troubleshoot > Integrations form. I attached the audit file as well. Let’s hope we can get this sorted!

“Your ticket number is 15906“

I was experiencing this and thought it was a bug, but apparently I guess it’s a “feature”… with really bad UI/UX. The meta key field should be disabled if it is going to be rejected, but it’s not. At the time of this post, you can edit the meta key field, but when you save and refresh the field reverts back to the old value. This is effectively a bug.

The work around
Luckily it is easy to work around this…
1 – Copy the field that you want to re-name the meta key
2 – Edit the new *_copy field with your desired updated settings
3 – Delete the unwanted old field
4 – Save

I would love to be able to do this too! I’ve spent a couple hours trying to figure this one out. Because of how our multi-sites are setup with child themes, we need to add brand specific colors of varying numbers and with varying nomenclatures and use cases to most of them. Sure would be nice if we could just add them on like it supposed to do! I though WP6+ was supposed to be legacy code friendly?

Thank you @andimorton, that works pretty well! ^

I just ran into this same issue again when I had to spin up a fresh instance because of a root kit attack from a vulnerability in a plugin we were using. As we were getting the new instance prepared the migration tools changed links to the new instance’s IPv4 because we hadn’t re-setup the DNS yet… uhg, it never ends!

Okay, I got it to work by renaming the plugins folder to plugins.hold, refreshing the page, going to the plugins page, and renaming the folder back to plugins. Then I reactivated the non problematic plugins, and then they had a bunch of updates to download, so I did all that.

Then I reactivated the problematic plugin from the warnings and the warnings came back, but after a minute the plugin showed an update was available, so I downloaded it and refreshed the page and the error was gone.

It looks to be back to normal so far, except for this buggy bar over the top of the side menu that scrolls up with the content section.

Try this… https://www.ads-software.com/support/article/faq-troubleshooting/#how-to-deactivate-all-plugins-when-not-able-to-access-the-administrative-menus

From this thread… https://www.ads-software.com/support/topic/unable-to-access-admin-dashboard-4/

• This reply was modified 4 years, 7 months ago by shanemac10.

Me three. I just upgraded to WP 5.5 and bam, the admin menu is gone and I have a bunch of errors. Well, my day is ruined.

Warning: Declaration of Sbi\Helpers\PluginSilentUpgrader::download_package($package, $check_signatures = false) should be compatible with WP_Upgrader::download_package($package, $check_signatures = false, $hook_extra = Array) in /Users/shanemccurdy/Desktop/Lake-County/lake-county/htdocs/wp-content/plugins/instagram-feed-pro/inc/admin/PluginSilentUpgrader.php on line 24

Warning: Cannot modify header information - headers already sent by (output started at /Users/shanemccurdy/Desktop/Lake-County/lake-county/htdocs/wp-content/plugins/instagram-feed-pro/inc/admin/PluginSilentUpgrader.php:24) in /Users/shanemccurdy/Desktop/Lake-County/lake-county/htdocs/wp-includes/functions.php on line 6270

Warning: Cannot modify header information - headers already sent by (output started at /Users/shanemccurdy/Desktop/Lake-County/lake-county/htdocs/wp-content/plugins/instagram-feed-pro/inc/admin/PluginSilentUpgrader.php:24) in /Users/shanemccurdy/Desktop/Lake-County/lake-county/htdocs/wp-admin/includes/misc.php on line 1310

Warning: Cannot modify header information - headers already sent by (output started at /Users/shanemccurdy/Desktop/Lake-County/lake-county/htdocs/wp-content/plugins/instagram-feed-pro/inc/admin/PluginSilentUpgrader.php:24) in /Users/shanemccurdy/Desktop/Lake-County/lake-county/htdocs/wp-admin/admin-header.php on line 9

Warning: Cannot modify header information - headers already sent by (output started at /Users/shanemccurdy/Desktop/Lake-County/lake-county/htdocs/wp-content/plugins/instagram-feed-pro/inc/admin/PluginSilentUpgrader.php:24) in /Users/shanemccurdy/Desktop/Lake-County/lake-county/htdocs/wp-includes/option.php on line 1050

Warning: Cannot modify header information - headers already sent by (output started at /Users/shanemccurdy/Desktop/Lake-County/lake-county/htdocs/wp-content/plugins/instagram-feed-pro/inc/admin/PluginSilentUpgrader.php:24) in /Users/shanemccurdy/Desktop/Lake-County/lake-county/htdocs/wp-includes/option.php on line 1051