Skip to main content

Sending plain text

phpList always generates a plain text version of your campaign, which is then included in the html campaigns as a matter of course. This is part of the normal working of email functionality. phpList also gives you two additional features:

 

  • Your subscribers can choose to receive plain text emails only 
  • You can edit the plain text version to improve it.

You can see the plain text version embedded in the source of your email by clicking View Source in your email client (exact instructions vary wildly)

IMG_20190730_140501.png

As you can see there is a plain text version in and amongst the html and other code.

Screenshot-from-2019-07-03-13-37-58.png 

Why edit the plain text version?

 

The automatically generated plain text version may not be very attractive. It is good practice to provide a quality plain text version because it:

  • displays better in some email software
  • makes your emails more accessible for people with visual impairments.

To assess the state of your default plain text version, you can click to view your emails only in plain text. In a desktop email client this is usually View > Message Body As > Plain text.

IMG_20190730_140446.png 

You can then see your email as it would be displayed to someone who is only able to receive plain text messages.

Screenshot-from-2019-07-03-13-39-21.png 

To improve this email and send a version formatted especially for these subscribers only takes a few extra moments and, as you can see, provides a much better quality of message.Screenshot-from-2019-07-03-13-37-58.png

Enabling plain text editing

Some installations do not show the Text tab, which is used to manually configure your text-only email content. If your tabs look like this, you'll need to change the configuration:

Screenshot-from-2019-07-30-14-16-28.png

To activate the Text tab in your installation, add the following lines to your config.php file:

# Manual text part, will give you an input box for the text version of the message

# instead of trying to create it by parsing the HTML version into plain text

define('USE_MANUAL_TEXT_PART',1);

An extra tab will now display in your campaign workflow. 

activate_manual_text_tab.png

Create your plain text version

Once you've created your HTML version in the Content tab (tab 1) click the Next button.manual_text_tab_actiaved.png

You should now be in the second tab, Text.

IMG_20190730_140427.png

You can manually compose the plain text version, or you can generate it automatically by using the generate from HTML buttonSome special characters in your html email may cause this automatic generation to fail. You can paste your text into this tab if you need to.

generate_plain_test_version_phpList.png

The empty Plain text version of message box will now contain a text only version of your html message.

The content should be the same as the html version. However images in the html version will automatically be removed and replaced by text descriptions and URLs are replaced by links. You can edit the message further if required, to make it as attractive and legible as possible.

Once you are happy with your plain text version, click Save and continue editing button, at the bottom of the text editing box, and carry on with testing and sending your campaign.

Screenshot-from-2019-07-30-14-27-58.png 

When you send tests, you will receive two emails, one text and one html.

The HTML version:

Screenshot-from-2019-07-30-14-30-53.png

The Plain text version

Screenshot-from-2019-07-03-13-37-58.png

 

Format tab: ONLY send plain text?

On the format tab there is a radio button for sending in either HTML or Text. Typically you will want to select the "HTML" radio button, which sends a version of the message that each subscriber specified when they joined your list.

However, if you want to send the text version of the message, select the "Text" radio button. This will override the user preferences, and send all subscribers the text version of the email.

Screenshot-from-2019-07-30-14-33-37.png

Feedback

Discuss this chapter here.