|
Fakta Kurser
|
April 11, 2024 at 4:34 am
Hello there
I have a problem sending out messages.
They’ve queued for sending but fail to do so – even when I try to Send Now.
I get a read ERROR box with this text:
An error has occurred:
No message was sent because of problems with sending. Either all the messages you selected were not a sendable message, they were already sent on a different scheduled task, or there is an error.If there was an error, you can look at the messages in the message activity list table for any error messages
Looking forward to getting your help here!!
Thank you
Lotte
|
|
Sam
|
April 11, 2024 at 5:39 am
Hi Lotte,
When you view the messages in the Message Activity table, what colour ‘status bar’ do they have?
Event Espresso -> Messages -> Message Activity.
The coloured bar to the left of each message indicates its ‘status’ and there is a legend at the bottom of the table to show the meaning of each colour.
|
|
Rio
|
April 11, 2024 at 6:59 am
If there was an error, you can look at the messages in the message activity list table for any error messages
You can go to EE dashboard -> Messages then you will see Error symbol, click it to view the message
https://monosnap.com/file/Cmu9ApuZSD228kk6vdW0th5UCr1HJm
Let us know what it says.
thanks
|
|
Fakta Kurser
|
April 15, 2024 at 4:07 am
Hi Rio and Sam
I checked and tried what you guys suggested – I still get the same error message.
I have 14 messages that are blue and needs to be sent out but fail do so.
When I check the status I only see icons: The eye, the cart and the fast forward. Not the i that is on you screendump.
I tried the usual tricks with manual Send Now, Generate Now and Generate and Send Now.
Nothing works….
Please help!!
Thank you
/Lotte
|
|
Rio
|
April 15, 2024 at 4:09 am
Hello,
Can you fill this form so we can look on the error message?
https://eventespresso.com/send-login-details/
thanks
|
|
Fakta Kurser
|
April 15, 2024 at 4:26 am
This reply has been marked as private.
|
|
Rio
|
April 15, 2024 at 5:02 am
This reply has been marked as private.
|
|
Rio
|
April 15, 2024 at 7:06 am
This reply has been marked as private.
|
|
Fakta Kurser
|
April 15, 2024 at 7:16 am
This reply has been marked as private.
|
|
Fakta Kurser
|
April 15, 2024 at 7:36 am
This reply has been marked as private.
|
|
Fakta Kurser
|
April 15, 2024 at 7:37 am
This reply has been marked as private.
|
|
Fakta Kurser
|
April 15, 2024 at 8:48 am
This reply has been marked as private.
|
|
Tony
|
April 15, 2024 at 9:14 am
Hi there,
The email you recieved is likely the standard email triggered when these a data error thrown on the site and was likely triggered when Rio test the emails above which then triggered a the fatal he posted up. Your site will then capture that error and send you an email for it.
—
The error above isn’t related to the PHP Dom Extension, its usually caused by invalid HTML within the messages.
Have you recently changed the message templates/content?
|
|
Fakta Kurser
|
April 15, 2024 at 9:33 am
No changes in the mails.
|
|
Tony
|
April 15, 2024 at 10:31 am
I’ve been trying to reproduce this on a couple of sites, copying over your template data etc but so far I am unable to reproduce the error your getting.
Something changed between 11. April 2024 01:02 and 09:01 as that’s when the emails started to fail.
Can you send over FTP credentials? I’d like to enable Debug mode and see if anything stands out from that.
|
|
Tony
|
April 15, 2024 at 3:05 pm
Hi there,
I’ve spent a lot of time digging into this and can’t reproduce it outside of your site. I stepped back through the code (none of which has changed within EE itself for a long time now) and the part that is failing here is converting the the HTML to a DOMDOcument, it throws this notice:
PHP Notice: Undefined property: DOMDocument::$documentElement in /wp-content/plugins/event-espresso-core-reg/vendor/tijsverkoyen/css-to-inline-styles/src/CssToInlineStyles.php on line 135
Then the code within CssToInlineStyles attempts to use documentElement and throws a fatal as its NULL.
Googling for this:
Undefined property: DOMDocument::$documentElement
Leads me to a few different threads all highlighting the same issue:
https://magento.stackexchange.com/questions/282703/undefined-property-domdocumentdocumentelement-in-magento-2
https://github.com/phanan/kupo/issues/31
https://github.com/braincrafted/bootstrap-bundle/issues/461#issuecomment-333508959
Those state the dom module was included twice within their install and that is what caused the error for them. Can you check with your host and have them confirm the dom module has only been included once?
|
|
Fakta Kurser
|
April 16, 2024 at 4:03 am
This reply has been marked as private.
|
|
Tony
|
April 16, 2024 at 5:29 am
Just in case this comes up again, may I ask what exactly they changed to fix this?
I assume DOM was set to load twice?
—
Forum threads automatically close after 2 weeks of no activity so this thread will likely close, but you can also link back to it in a new thread and we can merge/re-open if needed.
|
|
Fakta Kurser
|
April 16, 2024 at 5:48 am
This reply has been marked as private.
|
|
Tony
|
April 16, 2024 at 6:57 am
This reply has been marked as private.
|
