Sep 2, 2009
  4299
(0 votes)

Odd behavoiur in the Longstring property

An oddity I just found is that the LongString property renders differently with the <episerver:property tag when the user is logged in or not. The evidence that made me react was some embedded &nbsp; in the text. these were encoded and thus invisible when the user was logged in.

I havn’t looked into the reasons for this but the solution for situations where it´s just a string to print is to use the xhtml-property with disabled editor controls.

This problem was tricky to notice because it´s common to require login for staging servers.

Sep 02, 2009

Comments

Sep 21, 2010 10:32 AM

Hi!

This is probably related to the EPiServer "Permisson for functions"-feature that can give any user or group all tools in the editor.

This changes the behaivor of Long String and XHtml string is rendered when you uncheck all editor tools for a property (when you want a clean text box and not rich text).

I have reported this as a defect a some time ago but I think it slipped...

/Fredrik

Sep 21, 2010 10:32 AM

Hjalmar, check your profile: Anual = annual, developper = developer ;-)
/ Mr Picky

Sep 21, 2010 10:32 AM

Seems I was a bit too quick creating the profile.... Thanks for the heads up.

Please login to comment.
Latest blogs
Jhoose Security Module V3.0.0 – Site-Level Security Configuration for Optimizely

Jhoose Security Module updated for Optimizely CMS 13, introducing separate packages for CMS 12 and 13 with ongoing support and enhancements.

Andrew Markham | Apr 6, 2026 |

Searchable settings page

In my current project which has been actively developed for quite some time we have a big classic settings page. Unfortunately the placement and...

Per Nergård (MVP) | Apr 6, 2026

Using Azure Devops Pipelines in Optimizely SAAS (Configured) Commerce

Introduction When working with SAAS Commerce build service v2 your currently need to use a github repo with configured branches to start deployment...

Mark Hall | Apr 4, 2026 |

Forcing Lowercase URLs in Optimizely CMS During Auto-Translation

Learn how to fix uppercase and punctuation issues in Optimizely CMS 12 URL segments caused by LanguageManager auto-translation using a custom...

Stuart | Apr 2, 2026 |