Hi,

here is what is new around me and phplist: (news + questions)

1. I am almost done with the part of the code that can sync INITIALLY all attributes supplied by the core user module, the core optional profile module and the content_profile module (last one is the new one...) (later we should hook into some drupal hooks to update CONTINUALLY the attribute names and values in PHPLIST on their drupal changes ) This goes for all types of PHPLIST attributes (the simple checkbox+textline and the needing a separate table several others)

2. I found out the [URL:http://example.com/?email=[email]] magic placeholder that retrieves an arbitrary url providing a dynamic email get variable. This means that the drupal site owner can create the Web issue of his newsletter via drupal (node e.g.) and make it dynamically output code based on the user email supplied by phplist... Thus removing the need to sync most of the attributes. Only the attributes that are needed to filter which message goes to which groups of subscribers would still be present as attributes in PHPLIST ... Meaning that First Name , Last Name would become optionally sync-able for example ...

I attach a screenshot below to clarify for those that have not read the PHPLIST docs.

Note: In order for this [URL:] tag to work one needs to install a pear extension with "apt-get install php-pear" to install pear itself on Debian and then "pear install HTTP_Request" .

Note2: Outputting a newsletter message this way is awesome cause the theming is done by Drupal and integrates nicely with your site's corporate identity. Out of the box. 2nd it is nice to manage your messages from within the drupal node system...

3. Do you accept the following naming convention for the .module code? :

/**
* Convention:
* PHPLIST - the package from http://www.phplist.com/
* phplist - the Drupal module
*
*/

4. This is basically what I am upto - I need a day or two to make it suitable for public eyes and reviewers.

CommentFileSizeAuthor
phplist_url_placeholder.png88.91 KBrsvelko

Comments

paulbeaney’s picture

Hi rsvelko,

Looking forward to seeing these changes, especially the content_profile integration (and I know of at least one other person who has been asking for this for a looong time!) One thing to note, however - beware of the URL magic placeholder - it potentially opens up a (limited) security hole for leaking private data. It might be better to add an IP field in the admin settings to restrict access to the URL so that only the PHPlist installation can access it? It's either that or add some sort of token to the URL that gets pasted into PHPlist. In this security-conscious age, I don't think we can leave it without some sort of protection.

Regards,

- Paul

rsvelko’s picture

" Only the attributes that are needed to filter which message goes to which groups of subscribers would still be present as attributes in PHPLIST " - forget that - see here why: #716898: idea: Use drupal for mail audience filtering - every mail mesage is a drupal node and we use views to filter

What do you think about 3. above?

paulbeaney’s picture

What do you think about 3. above?

Sorry, not sure what you're getting at talking about "naming convention" ? How does it differ from what is currently there?

paulbeaney’s picture

Hi rsvelko,

Any news on all your developments ??

Regards,

- Paul

liliplanet’s picture

subscribe thx!