I had a need for popups on a site informing users of any new notifications. I know this is already in the works for version 2, but I didn't want to use the unstable code on a live site, so I put together the little module I'm attaching to this page.
The module is fairly lightweight, it doesn't add any new DB tables or anything. It adds an extra DB call for each page load however. It will popup on any page load, not just when users log in or out.
I don't think it's a worthwhile enough module to put on drupal.org as a full module, but I thought I would upload it here as-is for anyone who wants to use it, or not.
After enabling the module, you will have to go to the private message settings page and change the setting to display popups.
Comment | File | Size | Author |
---|---|---|---|
private_message_popup.zip | 3.2 KB | Jaypan |
Comments
Comment #1
BerdirDo you know http://drupal.org/project/pmgrowl?
It doesn't require 6.x-2.x AFAIK and doesn't only check on each request but all 30s.
Comment #2
Jaypan CreditAttribution: Jaypan commentedI didn't know about that actually. Thanks for letting me know - I'll check it out.
But, I actually want it to check on each page request, one DB check every page load is fairly minimal. I just put that comment there for anyone else who may consider using this module.
Comment #3
apoc1 CreditAttribution: apoc1 commentedI suggest you contact the owner of the privatemsg module and let him obtain it in the standard module. I think this should be some kind of default option in a messaging system
Comment #4
Jaypan CreditAttribution: Jaypan commentedThis is already in the issue queue for the module, so if he wants to integrate it, it's here for him to see. I'm assuming that it's not a very high priority for him.
I've been using the module I added on a couple of sites myself. It works good.
Comment #5
BerdirNothing will be added to 6.x-1.x anymore.
So if at all, it would be added to 6.x-2.x. Also, I can't just add whatever is uploaded to the issue queue to the project. There are already tons of modules in the 2.x branches, which I need to make sure that they continue to work, am responsible for fixing security issues, bugs and so on. Especially if I don't use those modules somewhere myself.
Which means that the minimal requirements for it to be considered to be added would a) provide this as a patch, so that I can review it. b) Fix the things I point out in my reviews (I'm sure there will be some things and multiple iterations, it will take some time both for me and you) and c) automated tests, if in any way possible. This project is getting larger and larger, I can't test every single module for every change so I *need* tests.
That said, I haven't looked at this module yet so I'm not sure if I'd consider to add it to this project, given that there is already pmgrowl. So, you could also create a separate project for this, maybe as a sandbox...
Comment #6
apoc1 CreditAttribution: apoc1 commentedWell, all I know is that this is very lightweight and easy themeable to your preferences. I'm using it for a while now and no complaints at all :)
Comment #7
v8powerage CreditAttribution: v8powerage commentedI just tried using it but it showed only once and then wouldn't appear anymore
Comment #8
Jaypan CreditAttribution: Jaypan commentedIt's really old, and the private message module has been changed in the meantime.
Edit (to match edit) - I believe I made it so that users are only notified a single time of a private message. Try sending another private message and seeing if the popup comes up again.
Comment #9
v8powerage CreditAttribution: v8powerage commentedit works now, it checks for messages on page reload, it would be cool if it checked without page reload and stayed until I close it though, wonder if that's possible
Comment #10
Jaypan CreditAttribution: Jaypan commentedNot without some additional custom development.
Comment #11
oadaeh CreditAttribution: oadaeh as a volunteer commentedThis issue is being closed because it is against a branch for a version of Drupal that is no longer supported.
If you feel that this issue is still valid, feel free to re-open and update it (and any possible patch) to work with the 7.x-1.x branch (bug fixes only) or the 7.x-2.x branch.
Thank you.