XML module: "The content that belongs here is too complex to display securely."

This is an open forum for any mojoPortal topics that don't fall into the other categories.

This thread is closed to new posts. You must sign in to post in the forums.
1/30/2013 1:31:22 PM
Gravatar
Total Posts 2

XML module: "The content that belongs here is too complex to display securely."

This morning we upgraded to the following version:
mojoPortal Version 2.3.9.4 MSSQL, running on Operating System Microsoft Windows NT 5.2.3790 Service Pack 2,
ASP.NET Info v4.0.30319 Running in Full Trust.
We use xml modules to display some tables on our intranet. The smaller tables work fine. But the larger one (our company phone directory) will not display and gives the following error:  "The content that belongs here is too complex to display securely." It worked fine on older versions of mojoPortal.

Any ideas?
 

1/30/2013 2:57:22 PM
Gravatar
Total Posts 2209

Re: XML module: "The content that belongs here is too complex to display securely."

That error is generated by NeatHtml.

The XML Module wraps the content from the XML files in the NeatHtml control to help prevent malicious code from being executed on your site. Possibly the version you were running on had a less restrictive filter applied to NeatHtml. If you have image references in your XML/XSL, you will want to enable the "Allow External Images" option in the settings for the module. If you trust the content completely, you can enable the "Trust Content Completely" option in the settings for the module and see if that helps.

HTH,
Joe D.

1/31/2013 5:40:52 AM
Gravatar
Total Posts 2

Re: XML module: "The content that belongs here is too complex to display securely."

I adjusted both settings, but it didn't help. Do you know if there is a way to edit the filter settings that are applied to NeatHtml?

1/31/2013 7:22:19 AM
Gravatar
Total Posts 18439

Re: XML module: "The content that belongs here is too complex to display securely."

If you set it to trust the content then it isn't even using NeatHtml so something else must be causing the error when it tries to process the xml with the xsl.

Nothing has changed in a very long time in the xml/xsl feature so I'm not convinced it is an upgrade problem. It could be something fixed or changed in an update to the .NET framework or it could be a problem with the xml or xsl file.

I would try to get the error detail and google it.

You might also check if caching is enabled in the settings. Even though you changed it to trust content it could be showing a cached version of the output from before that setting changed.

You must sign in to post in the forums. This thread is closed to new posts.