Skip Navigation

[Resolved] Error log entry: PHP Warning: Creating default object from empty value

This support ticket is created 5 years, 10 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 -
- 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 -

Supporter timezone: Europe/London (GMT+00:00)

Tagged: 

This topic contains 4 replies, has 2 voices.

Last updated by julieP 5 years, 10 months ago.

Assisted by: Nigel.

Author
Posts
#1186576

I've got a number of these appearing in a server generated error log in /wp-admin/:-

PHP Warning:  Creating default object from empty value in /home/mydomain/wp-content/plugins/wp-views/embedded/inc/wpv-filter-query.php on line 421

What does it mean and what do I need to be checking please?

#1186680

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi Julie

I searched and can't find any reports of anything similar.

Looking at the source code where the warning is reported it looks like that part of the code is related to ajax filtering.

So, it would be helpful if we could isolate when this happens.

Do you have Views with ajax pagination on the site?

Can you check whether using this pagination triggers the warning in the debug log?

And, if so, whether switching to page refresh for pagination means the warning doesn't appear in the logs?

#1186711

Hi Nigel (happy new year by the way)

Yes, I have 2 Views using pagination. One is Pagination enabled with automatic AJAX transition, the other Pagination enabled with manual transition and AJAX. I've got Full page refresh when visitors click on the search button checked under custom search settings (although there's no custom search on either of the pages where the Views are located).

I've just visited both pages on the frontend (several times) but no error logs are being generated. I've looked at my visitor logs but struggling to tell what's triggering the errors.

#1186753

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Can you keep monitoring it?

It's not that much to go on, not knowing what triggers it or when. As I say, examining the code where the error is reported, it very much looks like it would be provoked by something to do with ajax pagination.

There are some activity logging plugins that keep a record of everything that happens on your site (I don't have a particular recommendation, I'm aware of them rather than use them), and it may be with one of those that when you see the warnings in your error logs you can match it up with something in the activity log to know that a particular page is visited, for example.

#1188769

Good idea - I'll see what info I can retrieve and ask again if I need to. Thanks Nigel