Page 1 of 1
PHP Webtag Processing Error
Posted: Tue 20 Aug 2024 5:08 pm
by forestedge
My website uses the cutags php webtags in Wordpress tables on the home page. There are issues with loading this page at times and it could be related to the php error message in the attached files - difficult to work out where the problem is.
Seems to relate a pressure reading which is outside the normal parameters, but no idea where that processed info is coming from.
Any ideas?
Re: PHP Webtag Processing Error
Posted: Tue 20 Aug 2024 6:45 pm
by water01
These two elements do not match.
The first is an error generated by Windy about pressure at line 492 in their PHP script.
The second seems to a cutags file after it has been processed and uploaded by MX. The wierd thing is it says it is a cumuluswebtags.php file processed by MX, but all the pressure fields are correct, but it is not the latest cumuluswebtags.php file as I updated that on June 15th for CumulusMx 4, Version 4.1.0 Build 4024 and this one is way out of date.
Over to whomever maintains the cutags file?!!
Re: PHP Webtag Processing Error
Posted: Tue 20 Aug 2024 7:11 pm
by forestedge
Hi David
Thanks for the prompt reply. I have disabled Windy and will update the cutags file and see what happens!
Re: PHP Webtag Processing Error
Posted: Tue 20 Aug 2024 8:00 pm
by PaulMy
forestedge wrote:
My website uses the cutags php webtags in Wordpress tables on the home page.
water01 wrote:
Over to whomever maintains the cutags file?!!
A CUtags file is included in the Saratoga template CU-plugin as a file with webtags to be added in CU Extra web files for processing and uploaded as CUtags.php
A CUtags.php file is included in the MXUI template as a file with webtags to be added in CU Extra web files for processing and uploaded as CUtags.php
These files are different as each is for their own template, and are periodically updated by the template's author but not each time that David (water01) updates the cumuluswebtags.php.
Enjoy,
Paul
Re: PHP Webtag Processing Error
Posted: Tue 20 Aug 2024 8:07 pm
by mcrossley
You need to post the MXdiags file for when the error occurred. I expect that debug and data logging would need to be enabled to track the source of the problem down.