I created a custom content type with several Long Text fields. The field is set to use FULL HTML but when it display, Commons not formatting content as was configured when editing. For example, the following image shows how the content looks when editing:
edit

However, this is how this same content displays:
display

New lines are not being rendered and other formatting is getting lost when displaying.

CommentFileSizeAuthor
#3 commons_display_format_filtered.jpg133.97 KBAnonymous (not verified)
commons_display_format.jpg217.3 KBAnonymous (not verified)
commons_edit_format.jpg165.58 KBAnonymous (not verified)

Comments

ezra-g’s picture

ezra-g commented
Component: Content usefulness » WYSIWYG
Issue tags: +Commons 7.x-3.3 radar

Thanks for the thorough bug report!

Updating issue properties and tagging for triage before the 3.3 release.

ezra-g’s picture

ezra-g commented
Status: Active » Postponed (maintainer needs more info)

Could you clarify whether this happens with the "Filtered HTML" format?

Anonymous’s picture

Anonymous (not verified) commented
StatusFileSize
new commons_display_format_filtered.jpg133.97 KB

It seems to work OK in the Filtered format:

filtered

Anonymous’s picture

Anonymous (not verified) commented
Status: Postponed (maintainer needs more info) » Active
devin carlson’s picture

devin carlson commented
Version: 7.x-3.2 »
Status: Active » Postponed (maintainer needs more info)

I'm not able to duplicate this with a fresh install of Commons 7.x-3.x-dev and a combination of custom content types, long text fields, text formats and HTML content.

Can you upload a text file (.txt) containing the raw HTML that's being used inside of the long text fields?

Anonymous’s picture

Anonymous (not verified) commented

It appears that the person who made this node has since deleted it. I'm going to have her re-create the node so I can get you the HTML.

ezra-g’s picture

ezra-g commented
Version: » 7.x-3.x-dev
Category: bug » support
Status: Postponed (maintainer needs more info) » Fixed

It's been a few weeks since this issue was updated, so I'm marking as fixed.

Feel free to re-open with steps to reproduce.

Automatically closed -- issue fixed for 2 weeks with no activity.