Rich text

The Rich Text field in Participants Database uses the old “TinyMCE” editor with pretty limited configuration options.

You can adjust the size of the fullscreen using some CSS. For example, to add 10em of space at the top (thus revealing the top part of the web page, which is under the fullscreen editor, you can use a CSS rule like this:

div.mce-fullscreen {
   top: 10em;
}

You can try different things there, this rule controls the element that holds the fullscreen display that is superimposed over the web page, so you have other attributes that you can set like left, right, bottom, etc. Normally, this is set to top:0 and left:0 to completely cover the screen.

The width of the rich text field (when not in fullscreen mode) is mostly controlled by the formatting of your web page. It will expand (to a point) to fill the horizontal space that is available to it. You can try to make it wider by changing the formatting of the page it is on, but there will be a limit to what you can do with that…and it can be quite complex to get this to do what you want. You can’t simply make the element wider, it will be restricted by the page layout, which is determined by your theme.

The line spacing is controlled by the CSS stylesheet. When you type “return” it makes a new paragraph, and follows the spacing rules for a paragraph. You can adjust the CSS for this with something like:

#tinymce p {
   margin: 0;
}

Which will remove the paragraph margins in the editor window.

If you want a line break without making a new paragraph, use shift+return.

• This reply was modified 3 months, 2 weeks ago by rolandbarker. Reason: code display

The only thing you can do to make sure that a URL is displayed as a clickable link is to put it in an “a” HTML element, which is accomplished by using the 🔗 icon in the rich text editor. That is probably what you are doing, but I just want to make that clear.

This does not guarantee the URL will be displayed as a clickable link by the email client, and there is no way to force it to do so.

The header is already correct for that, so changing the header won’t help.

If you use plugin debugging or an email logging plugin, you will be able to verify that the header and HTML in the sent email is correct.