Responsed SOAP Message Doesn't Contain XStandard Namespace

By Ben Nadel

Published 2006-07-24 in XStandard WYSIWYG — Comments (1)

I was trying to add some new directory snippets (XHtml code templates that can be inserted into the generated content) when I kept getting the error:

responsed SOAP message doesn't contain xstandard namespace

It was driving me crazy because upon accessing the page directly, it worked fine and looked great. After about 45 minutes, I realized the problem was a permissions issue. And, not only was it a permissions issue, it was the same exact permissions issue that I blogged about earlier (XStandard does not use the current session information). When XStandard was going to access the .cfm pages where the template was stored, it was getting thrown over to the CMS login page which has nothing to do with XStandard (hence the lack of namespace in the returned XHtml).

I was able to fix it by sending the CFID / CFTOKEN. But now, I am realizing that I want to better integrate custom code template.

Short link: https://bennadel.com/164

Reader Comments

M7mmad Feb 21, 2008 at 6:29 PM

1 Comments

I would strongly agree with integrating custom code template.
Thanks for sharing this .

Oh my chickens, this post is old!

Hit me up on LinkedIn if you want to discuss it further.