I mean for "Drupal role - *" isn't it better to make those one "Drupal Role" attribute with many values?
I guess it was easier to write the sync procedure without having to care for a separate sql table that would hold the values for the attributes...
In PHPLIST each attribute with finite amount of possible values that is suitable for subscriber filtering has its own table ...
The one this message is aimed at (paul) knows these things anyway. Anyone else - go and inspect the user_attributes table in phplist after creating a new attribute...
Cheers.
Comments
Comment #1
paulbeaney commentedHi rsvelko,
You guessed correctly! Would it still be possible to select multiple roles for sending emails if we went with your idea of a single field? I didn't think PHPlist allowed multiple values for a single attribute field...
Regards,
- Paul
Comment #2
rsvelko commentedI checked - attributes of type "select" in the filter area allow multiple values - here is a shot attached.
I have not made any settings for this - it comes by default so.
Would you verify once more this with your phplist inmstall?
Comment #3
paulbeaney commentedI think you have misunderstood me - I know PHPlist allows you to select multiple values for attributes when creating criteria for lists, but I don't think it allows you store multiple values in one attribute field., thus you could only ever store a single Drupal role, which is not very useful.
Comment #4
rsvelko commentedOne more thing:
I think that this idea of mine will make the above attribute stuff obsolete: #716898: idea: Use drupal for mail audience filtering - every mail mesage is a drupal node and we use views to filter
Comment #5
paulbeaney commentedNo longer relevant according to post #4