[Snippet] Newsletter (Improved version from Luca Allulli)

No, the content would be from a page on site - but not a modX page

Featurewise, I think to make it ’even’ better having the ability to import csv email lists (most client’s are Excel obsessive compulsives about their mail lists) would give it the polishing it needs to be ’up there’ with alternatives like phpList.

ummm, bounce notifications ? That’s another prerequisite which springs to mind.

But yeah, the URL’s will be complete - it’s a shame there’s so many client’s to second guess, it’s the way newsletters ’must’ be coded that’s our biggest foe otherwise sending tableless xhtml css modX pages wouldn’t be an issue.

Thanks again for the great work !

You can build whatever page that you want with MODx Tablleless, too much table, no table, liquid layout, fixed layout, and etc, basically everything can be done using MODx. But if you insist on creating the html by hand, you can copy paste the code using the message view, instead of document view of sending MODx document.

About CSV importing, that’s a good idea. I’ll look into it again. For now, I’ll add them to my todo list Remember, this system is not well tested for huge amount of users. Wait until I implement message queueing, but it won’t be added for the next few months, sorry

I only have two words to say "PHPLIST" this is the best solution for any mail list or newsletter, I am very familiar with intergrating phplist into a website if anyone’s interested, not sure if modx soultion is better haven’t tried it.

any thoughts ?

phpList is infiinitely more robust for handling delivery, bounces, subscriptions, opt-ins, etc. However, the MODx solution here simply let’s you build a page in MODx and send it from there. A combination of the two would be ideal.

I’ve tried phplist, and it works great except for the fact that it’s way too much for average users, even end user like me. I would definetely say that this snippet is not the right solution for bigger site, considering this haven’t passed beta version yet. The reason why I release beta version snippets is just to encourage users on what we can do with MODx, as well as getting some programmers out there to either help me improve the system, or they can have a prototype of the sytem and able to build it something on top of this.

With that regards, use this snippets with cautious, unless you know what you are doing.

Sincerely,

Yes, a union would be ideal. I ended up skinning phpList so it’s layout is the same but with static navigation - the style sheets are shared and it isn’t a problem editing the layout markup if necessary within phpList. The user experience is seemless between content and subscribe/unsubscribe - but for sysops there’s two options, manager and newsletter admin. phpList also has "powered by" png’s linked back to tincan from the core which is more soup than source generating markup with errors and more unwanted ’tables’.

phpList could use an overhaul, but for now I agree it’s the very best option not to dismiss the work you’ve done which is terrific for the application it was intended

Quote from: Starbuck at Mar 18, 2006, 12:25 PM

Yes, a union would be ideal. I ended up skinning phpList so it’s layout is the same but with static navigation - the style sheets are shared and it isn’t a problem editing the layout markup if necessary within phpList. The user experience is seemless between content and subscribe/unsubscribe - but for sysops there’s two options, manager and newsletter admin. phpList also has "powered by" png’s linked back to tincan from the core which is more soup than source generating markup with errors and more unwanted ’tables’.

What version of PHPList did you skin? Would you be willing to share it skinned for those of us that could use it too? Also, how difficult do you think it would be to "MODXify" PHPList? I use PHPList for my websites and like the full featured functionality.

Can someone tell me if this is possible with the current version of this snippet (v.0.2b)

I would like to have 3 different mailing lists. And during a new user site registration I would like to have check boxes for each newsletter to subscribe to. Then after they are registered, it would be nice to have a page where those check boxes are listed again to check or uncheck and update their mailing list profile. If not, this seems like a good feature to add.

I’m not sure how such a thing would be integrated into the current registration form without some hacking.

if a visitor does not have an account can they still subscribe or is this only for registered group users

Quote from: jbjones at May 03, 2006, 02:22 AM

I would like to have 3 different mailing lists. And a new user registration process I would like to have check boxes for each newsletter to subscribe to. Then after they are registered, it would be nice to have a page where those check boxes are listed again to check or uncheck and update their mailing list profile. If not, this seems like a good feature to add.

I can’t answer this, but I most certainly second that request, this would be invaluable addition to the current snippet (if it does not do this already, I didn’t check new release for quite some time now...)