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?
Hi Guys,
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.
Mike
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.
Mike
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!)
Would be nice to get this thing up to speed.
Hey Mark, We found the problem that was causing the extension to not work properly. Follow this post in the bug forum here. I am going to go through the module and make some updates and I will post it when I am done, but it works as it is.
Hope this helps
Mike
Hi Mike,
Thanks for the reply, will check this out later today. Sorry for implying that there was something wrong with your code, it wasn’t meant to sound like that if it did. You have an absolutely fantastic little extension there which has a multitude of uses and I am ever grateful for the time you have put into it.
Will check that post out and let you know what joy I have 😉
Thanks again.
Best wishes,
Mark
Hi Mike,
Checked out that post and as it is possibly a bug in one of the core files I think I am going to leave this until the developers confirm the bug or fix it or whatever. It wasn’t really anything mission critical but I will definitely keep an eye out on the progress of your extension as it is a great addition to ExpressionEngine.
Thanks again for the information and link. Hope you have a great weekend, well what’s left of it anyway 😉
Best wishes,
Mark
Just to clarify - This is not my extension and I am not going to be taking over support for it. It was created by “drivingmenuts” and all credit should go to him.
I am just a user that needed it’s functionality and took the time to make it 1.6 capable. After reviewing the extension, we didn’t find any major errors that would keep it from working. We did find the bug that we submitted in the bug forum and after making the change everything worked properly.
I think it is wise to wait till Monday to see what the developers have to say. They may have written the core file that way on purpose and require the script to handle the function differently. I am curious to hear from them as well.
Mike
Hi Mike,
Shows that I need more sleep. Yep you are quite right (obviously) that this was created by someone else. Sorry about that. Had been away from the thread for a while and just read what you had posted and put the wrong name to the wrong thing so sorry for that.
Best wishes,
Mark
Hey Seth, I haven’t uploaded the final version of the extension yet so you will need to change the following line of code in the extension if you have error reporting turned on with your server.
Line 173: change the existing code to
if (isset($_POST['update_mail_send']) && $_POST['update_mail_send']=='y') {
This will prevent errors when you decide to enter or edit a post with the “Send notification” checkbox deselected.
Mike
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.