Notice: Trying to get property of non-object...

I am also getting this, for mini panels that are included as part of a Features module.

Same here, also with mini panels activated via Features. The mini panels packaged with the Feature don't show up in the ui, even though they're in code.

Actually for us it must have been some sort of weird interaction with something, not a general problem. A reinstallation of a new site followed by activating our Features resulted in clean minipanels. I think this needs more info from people who still have this problem.

For me, this happens because of a reference to a non-existing mini panel.

With the Devel module installed, visit /devel/php and execute:

panels_mini_load('nonexistent');
panels_mini_block_info();

The error will appear.

This occurs because panels_mini_load() will enter NULL into the $cache array and panels_mini_load_all() doesn't remove it.

I suggest adding array_filter() in panels_mini_load_all() to remove NULLs.

Here is a patch.

I got exactly the same issue. I just applied the patch from Jorrit #5 and guess what, it works perfectly.
I had effectively a reference to a non-existing mini-panel.
Thank you very much Jorrit for this efficient help.

Had the same issue, 'Jorrit' 's patch fixed it. Thanks

In my case this happened because I had deleted some mini panels blocks but the entries had not been removed from the 'block' table.

Similar to @mh86. Found them by running:

select * from block where module='panels_mini';

They had an empty delta. This will also find them.

select * from block where delta = '';

And this will fix it:

delete from block where delta='';

If you ever try panels_mini_load('nonexistent'); again, you will end up with another broken entry in the block table.

Could someone kindly tell me or direct me to an instruction how to apply Jorrit #5 patch?

Thanks!

#9 (mrfelton), I deleted the offending records from the database.
But when I clear the cache, a new panels_mini block record is created with an empty delta for my theme and the error re-appears. Can you explain why this happens?

That's really interesting. I don't really understand how this happens, but the patch makes sense. One downside is that it's going to obscure the fact that there's incorrect data in the blocks table, I think, but ultimately that is harmless.

I committed and pushed this patch.