we've got some fabulous results out of this amazing package (thanks again Darren!) so far, but now I've come across a small problem. Hoping for some insights on any possible solutions.
One of the pages generated exception errors while parsing. Looking into it, the client had added some text to their content which resembles a tag. Of course there is no closing 'tag' to speak of, so the parser flips out. Basically the client is writing out a set of instructions on how to track order status with your mobile: "send X <space> ordernumber to..."
Obviously we can/will inform the client to just rephrase these sorts of statements as to not include <space>. But I'm just wondering if there would be any way around this from a technical POV? (as in: prevent this from happening in the future; just put out unknown tag elements as proper text)
Hi Bjorn, are they adding this text to a rich text area and if so are you parsing it using the toXML helper method?
The solution would be for the users to input the entity & lt ; instead of the bracket but I understand this is probably complicated to explain to them.
That's the option we're going with now (advising them to use a different phrasing or notation). Was just curious to find a possible solution to prevent it from happening in future projects, but I think this is one of those cases when it's not worth investing too much time just to get it "right" and go for the simple solution instead.
Taglike text in content
Hi all,
we've got some fabulous results out of this amazing package (thanks again Darren!) so far, but now I've come across a small problem. Hoping for some insights on any possible solutions.
One of the pages generated exception errors while parsing. Looking into it, the client had added some text to their content which resembles a tag. Of course there is no closing 'tag' to speak of, so the parser flips out. Basically the client is writing out a set of instructions on how to track order status with your mobile: "send X <space> ordernumber to..."
Obviously we can/will inform the client to just rephrase these sorts of statements as to not include <space>. But I'm just wondering if there would be any way around this from a technical POV? (as in: prevent this from happening in the future; just put out unknown tag elements as proper text)
Thanks!
Bjorn
Hi Bjorn, are they adding this text to a rich text area and if so are you parsing it using the toXML helper method?
The solution would be for the users to input the entity & lt ; instead of the bracket but I understand this is probably complicated to explain to them.
Thanks.
Hi Darren, they are indeed adding this to a rich text area and we are using the PDF:RteToHtml helper method on this field to parse the content.
Thanks for your swift reply.
I think you can set up TinyMCE to enforce XHTML on save maybe get your users to use some other typr of bracket to denote <space> e.g. [space]
:)
That's the option we're going with now (advising them to use a different phrasing or notation). Was just curious to find a possible solution to prevent it from happening in future projects, but I think this is one of those cases when it's not worth investing too much time just to get it "right" and go for the simple solution instead.
is working on a reply...