Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Here's another one - when a user accesses the view and sends out a message, if they check the box to save the settings then the next person that hits the view to generate an email sees the saved message of the last person that sent out a message. If this could be modifies to be user specific, that would be great!
Thanks,
-=Delty
Comments
Comment #1
roball CreditAttribution: roball commentedFor me, saving the message settings does not work at all. Which VBO version are you using?
Comment #2
Delty CreditAttribution: Delty commentedI'm using VBO 6.x-1.9, the release version.
-=Delty
Comment #3
roball CreditAttribution: roball commentedI am using 6.x-1.10-beta3. Would you mind testing how the message settings work for you with that updated VBO version?
Comment #4
roball CreditAttribution: roball commentedWhat are your experiences using the current stable VBO version, 6.x-1.10?
Comment #5
Delty CreditAttribution: Delty commentedWell, I've disabled Views Send because of the issue with it breaking cron, which I posted as another bug report report. At this point, it's unusable for me, but I might re-enable it for testing when I have time over the weekend.
-=Delty
Comment #6
hansfn CreditAttribution: hansfn commentedThis isn't a bug, but a feature request.
Comment #7
hansfn CreditAttribution: hansfn commentedFYI: A recent commit at least improved the situation so it's clear that the values aren't stored per user.
Comment #8
soniat CreditAttribution: soniat commentedI need the recipients fields to be Name(name) and (mail). I don't want my users to be see/or choose the other options. I want the subject and message fields to be blank and not see another users message.
I tried using css to hide the recipients field set but received error message:Field used for recipients email is required. I using this module with crew connect. I'm also using the css visibility property to hide the fieldset. Any suggestions or solutions will be greatly appreciated.
Thanks,
Sonia
Comment #9
hansfn CreditAttribution: hansfn commented@soniat: Aren't you asking for something completely different then what this issue was about? Please don't hijack issues - start a new one in stead. Anyway, the solution to your problem is to use form_alter - see for example #1440428: How do you do a form_alter on the views_send_mail_action_form?. If you do that, you can hide the fields with CSS.
Comment #10
Marko B CreditAttribution: Marko B commentedI would also like it to be user specific. Or if not, to disable the possibility to save. With this save button it is only useful to user 1.
Comment #11
hansfn CreditAttribution: hansfn commentedWhy do you think this only works for user 1?
Comment #12
Marko B CreditAttribution: Marko B commentedWell If I am user 1 and send messages to others it is ok that I have this save option and that data is saved per form. But If I have user 1 and user 2 and user 3 etc and then user 1 sends message that is private and then comes user 2 and sees that, he gets info that he shouldn't have and then says the hell with this, I don't want to use this so everyone else sees what I send. :-) This is scenario that I see right now and why this is not useful.
Comment #13
hansfn CreditAttribution: hansfn commentedSure, if you select to remember the values, it's available for all users. This is nice if several different users send more or less identical messages. You can disable the button/option by using hook_form_alter.
The problem you are describing isn't specific to user 1 which was why I aksed "Why do you think this only works for user 1?"
Comment #14
Marko B CreditAttribution: Marko B commentedWell i ment only one user, and this would probably be user 1 :-)
Comment #15
hansfn CreditAttribution: hansfn commentedFYI: This issue is fixed in the D8 version of the module - ref commit 8425193.
Comment #16
BBCAny chance that the fix mentioned above has already been ported to the D7 version in the last few months? If not, is there a hook_form_alter example of how to disable this for non-admins somewhere?
Comment #17
hansfn CreditAttribution: hansfn commentedNo, this isn't fixed in the D7 version. It's not likely that I'll find time for that ...
Here is a hook_form_alter example:
Let me know it works - the code above is untested.
Comment #18
hansfn CreditAttribution: hansfn as a volunteer commentedNo new features will be added to the D7 version unless there is a "perfect" patch provided. I'm spending my very little spare time on the D8 version.