View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0020212 | phpList 3 application | Campaign Management | public | 22-05-20 16:27 | 01-04-21 23:04 |
| Reporter | suela | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Product Version | 3.5.4 | ||||
| Target Version | Future developments | ||||
| Summary | 0020212: [META]: Enhancements to 'Generate Message Preview' | ||||
| Description | PR: 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. | ||||
| Tags | No tags attached. | ||||
|
|
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. |
|
|
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. |
