Forum Replies Created
-
Posts
-
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!
KevinHi 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
