View Issue Details

IDProjectCategoryView StatusLast Update
0020212phpList 3 applicationCampaign Managementpublic01-04-21 23:04
Reportersuela Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Product Version3.5.4 
Target VersionFuture developments 
Summary0020212: [META]: Enhancements to 'Generate Message Preview'
DescriptionPR: https://github.com/phpList/phplist3/pull/654

This PR adds a message preview to the html campaign composer page (content tab). It has simple logic, using the existing backend functions for retrieving saved message content and turning into plaintext. It also removes newlines and other problematic characters. Via a new ajax file and call it loads the saved html campaign content and turns into plaintext, abbreviated to 90 chars. This is then shown to the admin in a non-editable input text field.
TagsNo tags attached.

Activities

lwc

28-03-21 11:06

updater   ~0063866

Also, it's not documented anywhere except that Github link (which is mentioned only in https://www.phplist.org/newslist/phplist-3-5-4-release-notes/).
Can you document it somewhere AND add it to https://www.phplist.org/demo/ ?

Even though it's beta, it's one of the most important features and "selling points".

Last but not least, like you stated "it has a simple logic". Keep in mind e-mail clients use very differentiated logic.
For example, while Gmail *shows* most images by default, Outlook *blocks all* images by default.

michiel

01-04-21 23:04

administrator   ~0063873

Yes, it needs documenting. Also I made it default to off a few months ago, because I wasn't impressed with the way it had been implemented

https://github.com/phpList/phplist3/commit/d5afacdfddeac717f63bfa6d0c31def1b2d7e1e7

If you want to promote this feature, we should work on a process for that. Something like

1. define the requirements (including differences in providers)
2. find a sponsor
3. get a developer to fix it (I've been using upwork.com recently)
4. verify and peer review changes
5. send merge request
6. update documentation
7. include it in release announcements
8. merge PR and release

I imagine, you'd be mostly involved in step 1 and 2. In fact, if convincing phpList Ltd could be considered in step 2.