barberousse wrote: > funcptr is used if another plugin wants to add its own definition for > macros, for instance, if SuperDateTime defines %H as hour, another > plugin may want to define §C as current song playing. I use this for > DomoticzControl a plugin to control Domoticz home automation system, and > it adds macros to show values inherited from Domoticz, for instance room > temperature, with SuperDateTime/CustomClock/CustomClockHelper. > > I don't understand why commenting out this line is helping, except if > another plugin uses the same mechanism as DomoticzControl, or if you > have DomoticzControl not correctly setup. In that case, DomoticzControl > may try to reach Domoticz server and timeout, that would explain your > troubles.
Regarding this line that was added that seems to be causing an issue with one or more users: $funcptr = Slim::Control::Request::addDispatch(['sdtMacroString'], I haven't examined the code but I'm guessing there might be a case where this lookup might fail and returning something unexpected and when it's referenced it's causing an error? I did not see the actual error that the original poster was reporting, it might be buried in a log file I didn't see. Perhaps adding code that checks to make sure it's getting a valid value before setting $funcptr? Perhaps add some example code in a comment that shows how to chain sdtMacroString calls? ------------------------------------------------------------------------ cafedude's Profile: http://forums.slimdevices.com/member.php?userid=69033 View this thread: http://forums.slimdevices.com/showthread.php?t=14327
_______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
