Skeku

Hey Paul, I’m not developer so you can’t expect a good explanation, sorry. I tried everything I could (deactivate every single plugin, switch to default theme,…) I knew that it could be something related to variables and different type of arguments so I started to search on the all mighty Google. So in our case:

– Open core.php from the “inc” folder created by the speed booster plugin. Do it with notepad, Sublime text, whatever…

I’ve changed every – foreach ($stuff....)– to foreach ((array)$stuff...). I had to do it a couple of times. The warning just disappeared and everything’s fine now.

It’s not something that changes your theme’s files, only the plugin so don’t worry and try it for yourself ?? Just keep in mind that changes will be lost when the plugin will be updated as we are changing one of its files.

Maybe tiguan could shed some light on it.

Ok, it’s fixed for me following this:

https://www.ads-software.com/support/topic/invalid-argument-supplied-for-foreach-in-wp-settingsphp

Hope it helps!

Same error, same line here! I want to still using Speed Booster. It’s a really great plugin.

I know it’s something related to the theme I’m using because I get 0 warnings when I switch to default theme on one of my sites: https://thestarterkit.info/

I have no idea what can I do to get rid of this :S

@shareaholic, I’ve finally understood it’s a problem related to my site, not with your plugin so I’m trying to figure it out how to fix it. If I unload functions.js, pinterest button works fine.

I think there is some conflict with some code inside (https://www.criteriondg.info/wordpress/wp-content/themes/outspoken/js/functions.js) and pinmarklet.js. I’ll try to make some changes using “jQuery no conflict” or whatever because as I said before, I’m not an expert. In fact I don’t know what I’m talking about!

Thanks for your time!

Thx a lot doctorvee! It works!!! It seems there’s an incompatibility between popularity contest and wp-cache (I’ve been using both of them :S)

same thing here and i don’t know why…pubDate error is fixed, i think…

Modified version works fine for me ??