&param bug on rules

Moderators: grovkillen, Stuntteam, TD-er

Post Reply
Message
Author
fabix68
New user
Posts: 7
Joined: 14 Nov 2015, 14:04

&param bug on rules

#1 Post by fabix68 » 15 Jan 2017, 16:10

:(
Even with the latest firmware remains the bug with the word "&param" which is converted to ¶m.
You may not be able to correct it?

aprex
New user
Posts: 3
Joined: 15 Jan 2017, 21:07

Re: &param bug on rules

#2 Post by aprex » 15 Jan 2017, 21:10

Yes, please, it will be fine to send alerts to Domoticz, instead of waiting 5 minutes for a device refresh...

Martinus

Re: &param bug on rules

#3 Post by Martinus » 16 Jan 2017, 09:34

It seems that if &para is shown somewhere in a webform, the &para is interpreted as the HTML escape sequence for a paragraph sign, looking like a backwards P.

I don't know where it should be fixed and it's possible that it does not occur on all browsers.

But there's a workaround for this particular bug: Use the &param as the first name-value pair in the URL so it becomes ?param and it will no longer be misinterpreted.

Example:

change this:
sendtohttp 192.168.0.8,8080,/json.htm?type=command&param=udevice&idx=286&svalue=%eventvalue%
into:
sendtohttp 192.168.0.8,8080,/json.htm?param=udevice&type=command&idx=286&svalue=%eventvalue%

So we've just changed the order in which the url is build up.

aprex
New user
Posts: 3
Joined: 15 Jan 2017, 21:07

Re: &param bug on rules

#4 Post by aprex » 16 Jan 2017, 15:57

Thanks Martinus, no more bad characters!

fabix68
New user
Posts: 7
Joined: 14 Nov 2015, 14:04

Re: &param bug on rules

#5 Post by fabix68 » 16 Jan 2017, 22:14

Thanks Martinus

Jeff
Normal user
Posts: 26
Joined: 18 Nov 2016, 18:35

Re: &param bug on rules

#6 Post by Jeff » 16 Jan 2017, 22:33

Thanks Martinus, cool :D

ayasystems
Normal user
Posts: 39
Joined: 09 Aug 2016, 09:45

Re: &param bug on rules

#7 Post by ayasystems » 18 Jan 2017, 12:53

COOL!

Post Reply

Who is online

Users browsing this forum: Ahrefs [Bot] and 14 guests