Is there a way to stop the Deprecated: tep_ errors and only the Deprecated: tep_ errors from showing in the error files
they are becoming a pain to wade through and have no real function simply because they don't point the file that the tep_ is being used on to cause the error to be listed
Deprecated: tep_ errors
-
ecartz
- Core Team
- Posts: 3084
- Joined: Tue Nov 05, 2019 6:02 pm
- Phoenix Version:
- Has thanked: 4 times
- Been thanked: 208 times
Re: Deprecated: tep_ errors
On your test site, simply delete the hook (from the database) that loads the file in which the deprecation notice appears. That will convert the deprecation notice to a fatal error on the caller. Those hooks use the function_surface class.
On your live site change your error reporting to E_ALL^E_USER_DEPRECATION -- since the tep_ deprecation notices are the only kind of deprecation notices we produce, that's all that it will shut off. PHP doesn't produce E_USER_DEPRECATION messages; its messages are E_DEPRECATION. Or go through and delete all the trigger_error lines. That's a legacy file now. It's not like we'll be changing it after deleting it.
On your live site change your error reporting to E_ALL^E_USER_DEPRECATION -- since the tep_ deprecation notices are the only kind of deprecation notices we produce, that's all that it will shut off. PHP doesn't produce E_USER_DEPRECATION messages; its messages are E_DEPRECATION. Or go through and delete all the trigger_error lines. That's a legacy file now. It's not like we'll be changing it after deleting it.
-
14Steve14
- Senior Contributor
- Posts: 923
- Joined: Fri Oct 25, 2019 7:01 pm
- Phoenix Version: v1.0.9.1
- Has thanked: 17 times
- Been thanked: 103 times
Re: Deprecated: tep_ errors
We have gone through all of our older code and removed what ever is causing those types of warnings and errors. Its not that hard to do as Rainer has a link to a file which lists most of them in his signature, and what to replace them with. If that doesn't find them then ask on the forums as no doubt others have had the same problem.
-
Xpajun
- Contributor
- Posts: 187
- Joined: Thu Mar 04, 2021 1:18 pm
- Phoenix Version: v1.0.9.0
- Has thanked: 3 times
- Been thanked: 6 times
Re: Deprecated: tep_ errors
That is my ultimate intention @14Steve14 - I'm just trying to ge a stable 1.0.8.21/9 live at the moment getting 5000 errors with only 28 of which are non tep_ errors really is a pain14Steve14 wrote: ↑Thu May 09, 2024 3:03 pm We have gone through all of our older code and removed what ever is causing those types of warnings and errors. Its not that hard to do as Rainer has a link to a file which lists most of them in his signature, and what to replace them with. If that doesn't find them then ask on the forums as no doubt others have had the same problem.
Current Store is now running 1.0.9.0 - php 8.2.18
Now working on taking a short rest
- php 8.2.18
Now working on taking a short rest
-
Xpajun
- Contributor
- Posts: 187
- Joined: Thu Mar 04, 2021 1:18 pm
- Phoenix Version: v1.0.9.0
- Has thanked: 3 times
- Been thanked: 6 times
Re: Deprecated: tep_ errors
ecartz wrote: ↑Thu May 09, 2024 9:40 am On your test site, simply delete the hook (from the database) that loads the file in which the deprecation notice appears. That will convert the deprecation notice to a fatal error on the caller. Those hooks use the function_surface class.
This will be handy for when I start updating the files with tep_s in them
Meanwhile the following is what I need at the moment:I deleted all the trigger_error lines - now I can see the real errors to be addressedecartz wrote: ↑Thu May 09, 2024 9:40 am On your live site change your error reporting to E_ALL^E_USER_DEPRECATION -- since the tep_ deprecation notices are the only kind of deprecation notices we produce, that's all that it will shut off. PHP doesn't produce E_USER_DEPRECATION messages; its messages are E_DEPRECATION. Or go through and delete all the trigger_error lines. That's a legacy file now. It's not like we'll be changing it after deleting it.
Thank you Matt
Current Store is now running 1.0.9.0 - php 8.2.18
Now working on taking a short rest
- php 8.2.18
Now working on taking a short rest