&#f6;
(lowercase o umlaut), the affected PHP code would formerly convert the hex value to int with no need to extract the hex digits first. Since it's PHP, no-one can tell what attempting to convert the equivalent HTML5 entity ö
would do, error or 0 or .... In 7.4 or later, if you previously got an int, you get the warning as well. Presumably some later version will raise an error.Nope, that's just the landing page. Still happening here.Were you trying to schedule something with a weird name?
It also works for me on an Android phone though I thought they were server generated error messages rather than browser error messages so device likely to be irrelevant.It works OK for me, on a real computer.
Do other RS pages work?Nope, that's just the landing page. Still happening here.
They are.I thought they were server generated error messages
Possibly, given we have no idea what the code is actually doing.rather than browser error messages so device likely to be irrelevant.
I get the same thing whether on my iPad (with out of date software) or on Firefox (Linux Mint). However, as the deprecated warnings are being inserted at the server, and the browser is not sending anything for the server to react to (except URL query strings), it has to be a result of data being retrieved from the HD/HDR and then processed by the server to generate the web page, and nothing to do with the browser or device the browser is running on.It works OK for me, on a real computer.
See above.Have you tried from another device?
Same, with variations which might be indicative: all three HDRs give the same two deprecated lines under the banner and then two in the Active list, whereas the HD-FOX produces three lines in each case.Does it fail with your other Humax boxes?
It's difficult to understand why all four of my RS-connected units are producing this but nobody else is seeing it. They have some duplication of schedule entries, but not duplicated across all four. Two of the units are on WiFi and two on HomePlug, so there's not even commonality there. The only thing left common to my units but nobody else's is my broadband connection!What recordings do you have scheduled?
The Auto and Settings pages work, EPG and Visual show similar effects.Do other RS pages work?
And stuff like the User-Agent header, which can have a significant bearing. It probably doesn't in this case as you get the same result from a real computer.the browser is not sending anything for the server to react to (except URL query strings),
Probably correct.it has to be a result of data being retrieved from the HD/HDR and then processed by the server to generate the web page
Or your tuning database - I can't think network is significant to anything.The only thing left common to my units but nobody else's is my broadband connection!
Another way to test via the epg page would be to set up favourites lists which contain a subset of channels and see which channels cause problems on the epg pages and which don'tOr your tuning database - I can't think network is significant to anything.
Are these on English, Welsh or a mixture of transmitters? As a test, you could just try the Mendip services, like my one which doesn't exhibit the fault. I could try a spare on Wenvoe too.
Perhaps we don't! Why isn't this working?:
View attachment 6664
The first rule works (although I recently tweaked it to pick up the Monday broadcast specifically), and I added the second rule to try to catch the Sunday repeats even though they have the same S- and P-CRIDs. Here are the "matching events":
View attachment 6666
There is no sign of these being pushed as schedule events in rs.log, and I'm not getting emails to say they have triggered a schedule operation. Is that because they are being filtered by CRID? Yes, I have tried resetting the rule.
I have successfully scheduled these events through the WebIF EPG, so why not RS?