I'd like to suggest that we give ourselves a deadline of next Friday, 31 March to get all the feature requests in. If we don't do this "everything else" will take priority - work, play, family...etc

I'll take all the requests and attempt to put them in some "order" and then pass them on to Marcan for review and comment.

To assist in that sorting out of features, it would be great if feature requests came all identified by priority - for example: (A) absolutely must have with RC1, (B) would be nice in RC1, (C) consider for version 2...

Thanks!

Quote:

Time to chime in folks. Get you wants and needs for this module up here soon.

My personal starting point for the minimal list features (must haves) is phplist (but without the bugs....)

:http://tincan.co.uk/?lid=453

If anyone has experience with phplist and knows first hand of some limitations we should not repeat, speak up.

Also, there are a number of similar applications to phplist
http://tincan.co.uk/?lid=1205
If anyone has experience with any of those and there are some great features, let us know.

Quote:

There is a separate thread about another user having difficulty sending out large numbers of email messages using EvenNews.

https://xoops.org/modules/newbb/viewtopic.php?topic_id=36742&forum=20&post_id=167943#forumpost167943

There, tzvook's solution was to raise memory limit to 96MB for scripts @ php.ini (not advised on a real internet server, just on dev servers).

Let's make this happen!

Quote:

IMHO, that's the easy part - phpList already has the features we'd need.

http://tincan.co.uk/?lid=453

If you have any to add, let me know.

Then we can move on the how much it will cost to develop.

{quote]... a mailinglist (a real decent one) is the most required thing in the community for some years now, we might all unite and gather some $$$$ for this project to serve us all.

but I mean something "real and strong". not just a simple mailinglist, but also something to manage contacts and customers....[/quote]

Agreed. But since it has been on the "to do list" for many years now (see xnewsletter - pre-alpha since about 2003), how do we actually "get it done"???

Agree that php list is great.

We're exploring the possibility of improving EvenNews

But it would also be nice to port phplist over to a XOOPS module.

Quote:

To ask the obvious, do you have any subscribers?

IF yes, check your XOOPs system admin > preferences > mail setup

Quote:

So, we have the EvenNews mod which is ok, but we could sure could use something much more powerful.

There's a thread started here
https://xoops.org/modules/repository/singlefile.php?cid=41&lid=1147&com_id=26836&com_rootid=22484&com_mode=flat&com_order=0#comment26836

in the evennew mod page that is better continued here.

Do we work on improving EvenNews or do we try to port phplist or simplenews to XOOPS?

Thinking of having some work done on the EvenNews module for XOOPS 2.0.x (not necessarily for 2.2)

Below are the "hacks" I'd like to see to make EvenNews EvenBetter.

Anybody got additional ideas?
Anybody up for sharing the development costs?

Admin Area
===============
Module button rollover pop up only displays "preferences" link, all other functions are not displayed. All the other function - config, subscribers, add newsletter etc, are available only if you click the mod button. Took me awhile to find them. This is not standard XOOPS UI. Should be fixed.

Text/HTML Format
===============
Subscribers can choose text or html format as a preference. However it's not clear if this really does anything. I composed an HTML message, but indicated as a subscriber that I wanted TEXT. The message was received as text. There's no way when sending a message to indicate sending it to "Text only" or HTML only subscribers

So either we could do the easy thing and simply eliminate the subscriber's choice. Most all current email clients can read HTML message.

Or the more complicated method - which I don't know has much value - when composing a message, there should be a "plain text version" and an "HTML version" and the message goes out as a multipart-MIME. Seems like too much work for little gain.

Bulk import of email addresses
===============
One can "import users" from the registered users list (respecting their "email" preferences which is nice), but should also be able to add a bulk list of emails via text file upload or cut/paste.

Misc.
===============
"Main Config Page" is blank. Not sure what should be there.

Bounce Control
===============
A way to manage bounced emails would be cool.
A way to know how may message "opens" you get would be cool too.

Blocks
===============
Need to create a "Recent/Current Issue" block for the module. At the moment the mod only has a "subscription block" and a its "main content block." A current issue block would have an admin configurable number of "recent messages" (1 thru 5?) - with some controls for truncation of titles and message content. Probably do not need the "from" in the blcok. This new block would be useful for a home page summary, where we don't need the "description" or "membership" sections that are in the "main content block"