Error message re list-widget.php

[twosixtwo]

Hi, my client’s suddenly getting this error message on sending events to their home page (please see attached screen shot).
All wordpress, templates and plugins are up todate.
I’ve checked where list-widget.php is – and it’s in 3 locations!;
/httpdocs/wp-content/plugins/events-calendar-pro/src/views/pro/widgets
/httpdocs/wp-content/themes/twentytwelve-child/trive-events/widgets
/httpdocs/wp-content/plugns/the-events-calendar/src/views/widgets
I have not turned off all pugins nor reverted to native WP theme as this error is on a live site. (Incidentally it doesn’t appear on the dev site, which is set up identically).
Thanks for any help as this is an urgent issue on a live site.
Kevin

[Nico]

Hi Kevin,

Thanks for getting in touch with us! I’ll help you here…

I see there are two different errors in your client homepage. The first one refers to the template override location. You should move the file /httpdocs/wp-content/themes/twentytwelve-child/trive-events/widgets/list-widget.php to /httpdocs/wp-content/themes/twentytwelve-child/tribe-events/pro/widgets/list-widget.php.

The second error is stating that the function tribe_get_custom_field is no longer available and you should use tribe_get_custom_fields (with final s) instead.

You are probably not seeing the issues in the staging site because errors/warnings might be off in that instance.

Please let me know if the above helps,
Best,
Nico

[twosixtwo]

Hi Nico
Thanks for your help. Before proceeding with your advice can you help me a bit more with the following questions?
Why should I have to do these steps, surely the plugin should handle any deprecated code? (This isn’t meant aggressivley, I just am worred about messing with code and folders).
In addition I have been taught since year dot not to amend core WP files yet this is telling me to amend the core wp-includes/functions.php. This seems weird, even if I did amend a core WP file, which I am not going to, it would be overwritten at the next update. So where’s the use in that?
Finally where is the variable to turn errors/warnings on or off as I would very much like to see and fix this issue in the staging site before doing so on the live site!
Thanks again, Kevin

[Nico]

Thanks for following up Kevin!

Why should I have to do these steps, surely the plugin should handle any deprecated code?

No offense taken! The deprecated code is in the template override really not in the actual plugin code. You can also go ahead and remove (or temporarily rename) the template override file, and then the error will disappear but probably the template override is there to do some custom modifications over the regular list widget.

This seems weird, even if I did amend a core WP file, which I am not going to, it would be overwritten at the next update. So where’s the use in that?

You are right core files (from WP, plugins or themes) shouldn’t be edited! In this case the core file is just outputting the deprecated notice, but this doesn’t mean the edit should be made there.

Finally where is the variable to turn errors/warnings on or off as I would very much like to see and fix this issue in the staging site before doing so on the live site!

Take a look at this article from the WordPress Codex: Debugging in WordPress. Hopefully this will give you an overview of how to set up your live and dev sites for debugging.

Have a great weekend,
Nico

[twosixtwo]

Hi Nicola
You’re a star! I was totally unaware of wp_debug and yes it was on on the live site and off on the staging (how that happened is a mystery for another day!). So I switched the settings and can now work on fixing the issue on the staging site, phew.
So l followed your instructions and created a new folder called ‘pro’ and moved list-widget.php into it. It worked fine on the staging site. The amend to the tribe_get_custom_field worked fine as well. I then carried out the fixes on the live site and they worked a treat.
You’ve not only helped me solve this issue but improved my understanding of WP and also helped me understand why the problem was caused. That’s really exceptional support, and I’m very grateful.
Respect!
Kevin

[Nico]

Stocked to hear you could work this out Kevin 🙂

Thanks so much for the kind words! I’m truly glad to help you understanding a bit more about WP while solving this.

I’ll go ahead and close out this thread, but if you need help with anything else please don’t hesitate to create a new one and we will be happy to assist you.

Cheers,
Nico

[Author]

Posts