| Anonymous | Login | Signup for a new account | 02-09-10 22:06 GMT |  |
| Main | My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
| 0005163 | phplist | Configuration | public | 31-12-05 23:09 | 18-02-08 14:19 | ||||||
| Reporter | frigginbone | ||||||||||
| Priority | normal | Severity | feature | Reproducibility | always | ||||||
| Status | new | Resolution | open | ||||||||
| Platform | OS | OS Version | |||||||||
| Product Version | 2.10.2 | ||||||||||
| Target Version | 2.11.X | Fixed in Version | |||||||||
| Summary | 0005163: Using [FORWARD] Link 2nd Time Fails | ||||||||||
| Description | I've included the [FORWARD] tag in the HTML newsletter template. Using the [FORWARD] link the first time, all is well. I go to the PHPList page, fill in the address and the newsletter is forwarded. The forwarded-once newsletter includes the "This message has been forwarded to you..." footer, very nice. If with the forwarded-once newsletter I use the [FORWARD] link (again), the process breaks. I go to the PHPList page, and get the message "Forwarding the message failed". | ||||||||||
| Additional Information | Shared system: Linux infong 2.4 #1 SMP Thu Jan 13 08:59:31 CET 2005 i686 unknown PHP ver: 4.4.1 PHP Configure Command: '../configure' '--with-mysql=/usr' '--with-zlib' '--enable-debug=no' '--enable-safe-mode=no' '--enable-discard-path=no' '--with-gd=/usr' '--with-png-dir=/usr/lib' '--enable-track-vars' '--with-db' '--with-gdbm' '--enable-force-cgi-redirect' '--with-ttf=/usr/' '--enable-ftp' '--with-mcrypt' '--enable-dbase' '--enable-memory-limit' '--enable-calendar' '--enable-wddx' '--with-jpeg-dir=/usr/src/kundenserver/jpeg-6b' '--enable-bcmath' '--enable-gd-imgstrttf' '--enable-shmop' '--enable-mhash' '--with-mhash=/usr/src/kundenserver/mhash-0.8.9/' '--with-openssl' '--enable-xslt' '--with-xslt-sablot' '--with-dom' '--with-dom-xslt' '--with-dom-exslt' '--with-imap' '--with-curl' '--with-iconv=/usr/local' '--with-freetype-dir=/usr/include/freetype2' '--with-bz2' '--with-gettext' '--enable-exif' '--with-idn' '--enable-mbstring=all' | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files | |||||||||||
 Relationships |
||||||
|
||||||
 Relationships |
|
Notes |
|
|
(0013089) michiel (administrator) 26-04-06 20:57 |
The issue is that forwarding requires that the user who forwards is a valid user in the system. I have a hunch that the second forward fails, because the user who tries to forward doesn't exist. But it might be something else. Apart from anything, I would want to discourage this, but I'm not sure. Is there a good reason to make this work? |
|
(0013112) frigginbone (reporter) 27-04-06 15:16 |
Addressing the question, "Is there a good reason to make this work?" One of the best ways to market something is to develop word-of-mouth promotion; it adds instant credibility. If my newsletter is of good quality and someone forwards it to a friend then that's word-of-mouth promotion (and no spam.) If that friend wants to forward the newsletter, using the phpList method breaks and the letter isn't forwarded. And worse, I look unprofessional. The mechanism could simply be typing the "from" address if it's the second forward, and forwarding to the typed address/addresses with no database check. The reason for using your present method is to insure the html integrity. As the feature stands, it's too dangerous to use. |
|
(0013120) michiel (administrator) 27-04-06 16:07 |
fair enough, good point. I'll look into it when I get to the 2.11 stuff. |
|
Notes |
