Receiving Warnings: Invalid argument supplied for foreach()

Hi there,

It looks like your site is displaying warnings and notices. You can set WP_DEBUG to false so it doesn’t display those. Warnings and notices are not fatal errors and so can be ignored for the most part. We will look into the cause of the warnings as well, and see if there’s an issue we can address.

With menus, it is often another plugin that supplies arguments, some invalid, about their admin menu that can cause warnings when plugins try adding to the common admin menu.

Rob

that’s all very nice ?? but apparently this escalated to FATAL + e.g. crashed my prototype thus:

[18-Jan-2019 15:54:06 UTC] PHP Fatal error: Uncaught TypeError: Argument 1 passed to Freemius::get_api_user_scope_by_user() must be an instance of FS_User, boolean given, called in /wp-content/plugins/featured-images-for-rss-feeds/includes/freemius/includes/class-freemius.php on line 19043 and defined in /wp-content/plugins/featured-images-for-rss-feeds/includes/freemius/includes/class-freemius.php:19057
Stack trace:
#0 /wp-content/plugins/featured-images-for-rss-feeds/includes/freemius/includes/class-freemius.php(19043): Freemius->get_api_user_scope_by_user(false)
#1 /wp-content/plugins/featured-images-for-rss-feeds/includes/freemius/includes/class-freemius.php(19081): Freemius->get_api_user_scope(false)
#2 /wp-content/plugins/featured-images-for-rss-feeds/includes/freemius/includes/class-freemius.php(16371): Freemius->get_current_or_network_user_api_scope()
#3 /wp-content/plugins/featured-images-f in /wp-content/plugins/featured-images-for-rss-feeds/includes/freemius/includes/class-freemius.php on line 19057

It would seem that this might benefit from some further attention (cc @freemius) , would it not?

Best – LX

• This reply was modified 6 years, 2 months ago by eLeXeM. Reason: cc'd @freemius
• This reply was modified 6 years, 2 months ago by eLeXeM. Reason: completed stacktrace

Hi LX,

That’s a different error, and probably warrants a separate support thread, but we’ll definitely need to resolve any Fatal errors right away.

@freemius can definitely chime in here as well, as we are using the latest version of their SDK, as far as I am aware.

I will look into this more and update you as we dig into it.

Thanks,
Rob

Hey Rob + thanks for getting back to me re this.
As I had the same issue affecting another plugin as well, I have in the meantime received the tip from @freemius in that other thread to run their dedicated fixer pluggie. Ran that and the other plugin could be reactivated without crashing the site anymore.

To see if the cleanup also healed yours from throwing fatals, I have re-activated that, too, and loaded the front page a few times. It seems that cleaning up Freemius did the trick here as well, as the site didn’t crash so far.
Will keep you posted if it breaks any of yours again, but for now I think we look ok.

Cheers – LX

Hi folks, just checking in.

In my case, a new version of the plugin I was using, “Subscribe to Comments Reloaded” became available. I updated the plugin and I’m no longer receiving the warnings.

If this was coincidental, I’ll re-post here to indicate it was a false positive. Otherwise, we can assume this fixed the warning/issue/

Cheers!

It’s you we thank Rob for developing this nifty plugin and making it available for free.
Keep up the good work.

In appreciation,
G

+1 to what @gillesgagnon said ?? + goes both ways (y) Cheers – LX