No, it does not support multiple weblogs and single entry comment pages. At least not yet and probably not until I understand more about how the whole system works.
I will have some time to look at it this weekend, I think.
This one fulfills most of the requests I have received:
1. a checkbox so you can turn it off on a post-by-post basis.
2. a text box for adding some additional flavor if necessary
3. inclusion of the post title in the subject line
4. better support for internationalization (I moved some hardwired prompts and messages into the language file).
You will need to deactivate your old extension and activate this one after you upload. It has a new hook that won’t be registered otherwise and then the whole flaming thing just won’t work.
I’m writing some new features for this kind of thing (it’s actually a separate EXT that I started writing a few days ago),
will let you now once they are ready if you want to have a look.
You will need to deactivate your old extension and activate this one after you upload. It has a new hook that won’t be registered otherwise and then the whole flaming thing just won’t work.
You can use the update function, which will allow you to add new or modify existing hooks based on what version the person is migrating from and to. After replacing the extension file, the first time the extension is called, the update will automatically run.
You will need to deactivate your old extension and activate this one after you upload. It has a new hook that won’t be registered otherwise and then the whole flaming thing just won’t work.
You can use the update function, which will allow you to add new or modify existing hooks based on what version the person is migrating from and to. After replacing the extension file, the first time the extension is called, the update will automatically run.
Didn’t even think about that while I was working on it. Next version, definitely - if it needs to go to a next version.
After I edited a post today and sent out 6 emails.. I made another edit and unchecked the “Send notification to mailing list(s)?” box.
I got the following error (I removed the full paths):
Notice: Undefined index: update_mail_send in (path removed).../extensions/ext.updatemail.php on line 173
Warning: Cannot modify header information - headers already sent by (output started at (path removed).../extensions/ext.updatemail.php:173) in (path removed).../core/core.functions.php on line 293
I have a question about multi-weblog support. What I’d like to have is a separate notification mailing list for each weblog. Is this what multi-weblog support means, and if so, how do I set that up? It isn’t clear to me from the documentation.
Thanks in advance for any help anyone can offer - I really appreciate it.
FWIW Frank I’ve since disabled this extension - between the error, the sending of email with every edit and the apparent lack of support it wasn’t worth it.
Thanks Mike. I saw the part about updates causing the alerts, but I glossed over the error.
Can you think of any other way to have email alerts sent to people who subscribe to a mailing list? The site I’m working on has about 230 separate weblogs, so I would need a separate mailing list for each. It will also have authors using the SAEF so I don’t have immediate control over what appears on the site (and would presumably trigger an email alert) - unless perhaps I set the default status to closed, but I’m not enthusiastic about doing that.
Question, I configured EE such that it has some kind of workflow, our articles for from draft -> proposal -> reviewed -> open, our editors use the SAEF and a special page to go through these states. the extension should only send messages to members when status is ‘open’. Can this be configured?
I just tried running this extension with 1.6.2 and after I edit a post it returns a header error
Notice: Undefined variable: temp in /home/xxxx/public_html/client/xxx/xxxxxx/cp/cp.communicate.php on line 1058
Warning: Cannot modify header information - headers already sent by (output started at /home/xxx/public_html/client/xxx/xxxxx/cp/cp.communicate.php:1058) in /home/xxxx/public_html/client/xxx/xxxxxx/core/core.functions.php on line 296
The email gets sent but there is no body in the email. Has any one modified this extension to run on the current EE builds or know what needs to be updated to get it to work? This is exactly what I need for my current project.
Thanks, any help would be appreciated, I am not very educated in the EXTENSION/MODULE department.
Just wondering about the last comment too. I installed it and all seems to work fine, the e-mail gets sent but all I get is a subject line in the e-mail and absolutely no subject or links to the post in question.
Hey Mark, you didn’t mention if you get header errors after updating a post? And are you using 1.0.0 or 1.0.1? I am using 1.0.1 which adds multiple mailing lists.
I have been looking at the extension and everything is correct to current standards (almost). The problem seems to be in the last section where it is actually sending the mail through the communication module. The code needs to be rewritten to properly format and send the email out. It is able to read the available mailing lists and gather the subscribers, but fails when it goes to actually send the email.
I think it has to do with changes in the cp.communicate.php file and how it handles the unsubscribe link, but thats where my knowledge falls short.
Sorry I am using V1.1.0. I’m not sure what you mean by header errors though? Do you mean in the control panel or the e-mail? The e-mail comes through (I am using Mail on OSX) but there is just no body to it.
After I update a post with or without the “send notification to mailing list(s)” check box selected, the return page is white with a couple of error messages on it ( check my previous entry ). If not it might be something with my site which has a lot of custom fields etc.. I have tried disabling all of the other extensions with no change, but I have not had time to test on a clean install.
One thing that I haven’t had time to change and test is setting the priority level in the ext. to something like 10 or adding
$EXT->last_call
which is one thing the extension is missing.
Even with that, there still needs to be some rewrite done with the way it works with the communication mod. (I think!)