On 19/09/2011 16:48, Nick Kew wrote:
On Thu, 15 Sep 2011 11:52:38 +0100
Martin Townsendmartin.towns...@power-oasis.com wrote:
Should this new filter also
inherit the output filters context? Am I doing something wrong with my
use of mod_include? I've tried moving my filter so it's
On Thu, 15 Sep 2011 11:52:38 +0100
Martin Townsend martin.towns...@power-oasis.com wrote:
Should this new filter also
inherit the output filters context? Am I doing something wrong with my
use of mod_include? I've tried moving my filter so it's after
mod_include but still the same
On Thu, Sep 15, 2011 at 12:52, Martin Townsend
martin.towns...@power-oasis.com wrote:
Hi,
I have an output filter that parses custom tags to retrieve data from an
application running on the same device.
Everything was working well until I tried to move some HTML into Server Side
Include
On Thu, 2011-09-15 at 11:52 +0100, Martin Townsend wrote:
Having stepped through with the debugger I can see that the pointer
to
the output filter when processing the main HTML page is different to
the
one when parsing custom tags in SSI pages.
This is IMHO expected behavior. Different
Hi,
I have an output filter that parses custom tags to retrieve data from an
application running on the same device.
Everything was working well until I tried to move some HTML into Server
Side Include pages. Snippet below:
?smu smu extio_sensor_read mappings ?
?smu smu extio_read
