This is confusing and looks like a bug for me: When I set "plain text" in the field settings of an textarea, web page addresses and e-mail addresses are NOT turned into links automatically and lines and paragraphs are NOT breaked automatically.
BUT: When I set "Filtered text (user selects text format)" in the field settings of an textarea and select "plain text" while writing the content, web page addresses and e-mail addresses are turned into links automatically and lines and paragraphs are breaked automatically.
Is it not possible to have a plain text with these two automatic functions without setting the format each time?

Comments

droplet’s picture

Priority: Major » Normal

Plain text in Field (Text processing)
Plain text in Text format

There are different things in my mind and there has a bug : #1015510: Specify a default format for text fields (not long text)

montesq’s picture

Status: Active » Closed (duplicate)

So we can consider this one as a duplication of #1015510: Specify a default format for text fields (not long text)

AndrzejG’s picture

Please don't close this issue. It holds also for long text.

Here is my simple example.
I have enabled Video Filter to the plain text format, and also permitted such HTML tags as <object>, <embed>.

It is working OK when 'I set "Filtered text (user selects text format)" in the field settings of an textarea and select "plain text" while writing the content' (cite DocuAnt). Video is visible and displays OK.

However, when I set a long text field as plain text only, the filter doesn't work no matter how I set the display format. The Video Filter code [video:....] is displayed instead of video itself. The same is for 'object' or 'embed' codes.

It follows that "Plain text" option in the long text field setting doesn't work properly.

David Lesieur’s picture

Title: "plain text" is not equal to "plain text" » Different meanings for "plain text"
Version: 7.x-dev » 8.x-dev
Component: filter.module » user interface text
Status: Closed (duplicate) » Active
Issue tags: +Usability

This is purely a naming issue.

David_Rothstein’s picture

Title: Different meanings for "plain text" » Different meanings for "plain text" (Field UI text processing vs. default Filter module text formats)

#1095838: Plain text format does not honour filter processing also has a lot of discussion and examples of people being confused by this usability problem.

BChandran’s picture

Version: 8.x-dev » 7.22

I have the same issue. Could someone explain how to set Plain Text format and have line break working? I want the user to input only plain text and the line break and para break should show as such. Thank you.

David_Rothstein’s picture

Version: 7.22 » 8.x-dev

@BChandran, if you're talking about the text format that can be done on the text format administration pages (admin/config/content/formats); if you're talking about the plain text option on text fields in the Field UI, there's a patch at #1152216: (Long) text field (textarea) with "Default" formatter does not retain newlines which would allow that and which needs review.

This issue is just about the UI confusion arising from the two things having the same name...

BChandran’s picture

@David_Rothstein. Thank you for your reply but I am a newbie and couldn't figure out where and how to apply the patch. Please forgive my ignorance.

David_Rothstein’s picture

@BChandran, check out http://drupal.org/patch and in particular the section on "applying patches" underneath it. Hope it helps!

BChandran’s picture

Thank you. Trying to learn now.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

pameeela’s picture

Issue summary: View changes
Status: Active » Closed (outdated)
Issue tags: +Bug Smash Initiative
StatusFileSize
new18.19 KB
new24.43 KB
new24.28 KB
new24.31 KB

I think this is no longer relevant. I'm not sure what the situation was when this was filed but currently:

  • Line breaks are respected in Text (plain, long) fields
  • 'Plain text' is only a fallback text format by default, so it's not available as an option on a formatted text field, unless it's reordered to be weighted first
  • The format can be configured, so you can choose whether to convert URLs into links or not
  • The configuration is displayed below the field

So I'm going to close this because I don't see any way to progress it. If someone feels this is still an issue, please feel free to re-open with an updated issue summary outlining what changes should be made.