I'm working on adding PHPlist as a phpNuke module.
I hope I can get your suggestions and comments as I work on its development.
Currently I have
- database changes done - it uses its own database layer. Basically I read the Nuke config variables to create its own database connection... it had conflicts with Nuke old SQL layer in the normal scripts (same function names). In the admin part, I did like the Forums admin and let it run its own db connection. So basically it does two seperate database schemes, requiring two database files. The tables it reads should be something like nuke_phplist_* - reading from both $prefix and $user_prefix as needed
- modules front - for the most part, this is done. It will appear as a standard Module and call the correct header and footer. One minor glitch I've yet to fix, but I'm working on it. Certain URLs seem to coded into the database, so it will require some user edits to change to modules.php? format.
- Administration - currently works like the Forums admin, a link to a seperate area to control the it, and requires the Nuke admin account in order to get access. I don't know if I should connect the admins table of Nuke directly, because it would require some rewriting of the admin system in Nuke. And I'd still have to replace its own login checking with the admin login. Any ideas how I can accomplish this without shooting myself in the foot? Will the PHPlist extra login be a hassle?
- Users, currently users are tracked only by email address. They can subscribe and unsubscribe to multiple lists - even unsubscribe from all lists (I believe removing from the system entirely). Trying to integrate this with the current users table, should I add fields to it? Keep it as a seperate table and read the data from the main users table?
I guess that's where I'm at now. The database and feature integration.
I'm thinking one way would have the Nuke account control the email account for the PHPlist, but obviously when you change emails the whole system will need to be updated. Then some sites may not want this at all, just have the PHPlist run as a seperate email list for lots of other emails. If I do the user integration, it will be harder for people to convert their databases into this system.
Give me your thoughts where I should proceed with this.
"- Users, currently users are tracked only by email address. They can subscribe and unsubscribe to multiple lists - even unsubscribe from all lists (I believe removing from the system entirely). Trying to integrate this with the current users table, should I add fields to it? Keep it as a seperate table and read the data from the main users table?"
I would suggest creating a table for PHP list that matches user IDs with mailing list codes. For example, each time you create a 'mailing list' one could subscribe to -- it could add a column to Nuke Users table --- When a user elects to subscribe to a specific mailing list it adds a "1" value in the column for the mail list. This way, you maintain email addresses, contact information etc all in one place.
I don't know much about PHP List -- but it would be really neat if the mailing lists were capable of handling 'mail merge' capability where I could create a letter to go to:
Thanks for joining our parent's mailing list. We'll keep you up to date on regatta schedules, etc.
So basically, rather than trying to find a way to add email addresses to different lists -- I'd have the email addresses in ONE place, and codes identifying which list to join.
I'm new to this so I'm not much help, but another option might be is you know how the "Reccomend to a Friend" module shows the current username and email of the registered user? Couldn't you do the same thing, create a form that "posts" it into a table?
Lastly, I think a good email marketing campaign type module for nuke is needed, badly. Important features:
- easy to use (it needs to be simple)
- needs a wysiwyg editor so that even non computer savy folk can create a blast email to list members
- ability to add attachments to the email
- abiliy to save and resend certain types of emails.
I can't think of anything else. Sorry I'm not really any help...I wish I knew more -- I am glad to see someone pursuing it. Is there ANYTHING I can do to help it along? Any peice?
Joined: Mar 25, 2004
Thu Oct 21, 2004 6:35 pm
holly cow.. you can make an email list based on an RSS feed?
so does this mean, you could add the RSS feed to teh FORUMS, and allow members to receive via email a listing of a specific forum or topic? cool.... if it can
Joined: Mar 25, 2004
Thu Oct 21, 2004 6:37 pm
okay, clearly in looking at this PHP List thing -- it has GOT to be a nuke module.
what do you need to make it happen?
that would be so cool. is there any way i can help?
Evaders99 Site Admin
Joined: Aug 17, 2003
Thu Oct 21, 2004 8:26 pm
Thanxs for the reply - I hope I get more response from people who are interested. PHPlist is quite powerful. I've not done going through all the features myself.
I think it'll be relatively easy to have your email tracked to your Nuke email. All the subscriptions would automatically change based on your current Nuke email. I could probably make it auto-register into the PHPlist when you create your Nuke account.
* I'm not sure about this "mail merge" you wanted. But I'm guess perhaps PHPlist does do this for you.
* On the form that "posts" into a table, I'm not sure what you want here. I don't believe that's what PHPlist does.
* PHPlist is a bit big on the configuration (soo many options), but it is powerful and once set up, it is quite easy to use. It does have a WYSIWYG editor as well. I don't know about the other features, but explore it and tell me.
Mostly, I'm asking how integrated do people want this?
I'm at the stage where I'm pretty ready to release as a half-integrated product. It will appear inside your Nuke site as a module, but have a seperate admin (possibly protected by the Nuke admin system) and a seperate user database (of emails). Databasing and code changes would be a minimum.
If I did the full integrated thing, it would require rewriting parts of Nuke, much like integrating phpBB did. Something I'll work on given more time and more interest. But as it stands now, I don't have time and I don't know people's interest in this project.
Well... to answer the question "how integrated do people want it to be"
let me ask, how integrated does it NEED to be, in order to function well-- and be a great resource?
If you have partial integration, with bult of the administration outside of nuke-- that's cool I think. What I think is important is that there be a module page...or better yet... "Join a mailing list" block where it reads current email and name of the logged in user (like the refer to a friend page) -- then the person checks off which ones to join or unchecks which ones to leave -- and ------then the mailing list is updated.
That seems most practical? Making it easy for people to subscribe and unsubscribe from a variety of lists.
I'd be interested in learning more about the partial integration one you have so far -- have you tested it out?
HalJordan Support Staff
Joined: Aug 07, 2004
Location: Somewhere around Hunan, China
Sun Oct 24, 2004 11:43 am
Yeah,Evaders, how far are you? Is it in alpha or beta now?
My school is now looking into maintaining mailing lists for the alumni. If I could integrate this function even partially into our nuke site, I would be most grateful. Installation and administration of any mailing list program is going to fall on my already overworked shoulders, so I'd rather not have to administer yet another server.
Our nuke site is hosted by a service provider who can provide majordomo lists at additional cost, so if I can provide majordomo-like services at no additional cost without hosting them on one of our internal servers, I'd be one happy camper.
I am afraid I cannot help much with the coding, being a php noob, but I could be a beta tester if you need one.
My clientele is largely computer-illiterate, so the simpler the user interface the better. Ideally, the user should see a radio button list of available lists to subscribe to, and a confirmation request. Being a registered user of the nuke site first would be a plus.
My moderators would need things simple, too. I will check into phplist some more myself, as it may just fit the bill.
It's in Alpha, working on it in phpNuke 7.5. As I continue to tweak it, I'll start seeing if I can at least get a block to work work, reading data from the phpNuke users.
I will certainly test on a pre-7.5 Nuke setup before I release. Probably just get a clean 7.4 and make sure it will install correctly.
This release candidate probably won't be as bug-free as I want it, but I won't know until bugs are reported back to me. I'm glad you're interested - but I do not recommend using this in a production environment until it is in the stage for a Beta.
Okay, I cannot get a block to function correctly. When I try to load the config settings of the PHPlists, things mess up trying to read the database.
For now, it doesn't look like a block will be an option.
I will try to add a button on Your_Account area. Past that, I don't think there's too much else I will work on before release 1 (besides testing it of course)
Moved the table definitions into an include file. This will allow a block to function, at least with a simple "You are/are not on our PHPlist system" message. I don't know how to read the actual list of mailing lists at this stage.
I've got the Your_Account email changes to update the PHPlist as well. But the Forums profile still won't work... a variable gets unset somewhere, I'm trying to track it down. If I can not find this problem, I'll leave it unsettled and probably release it this way.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum