Support

Home Forums Event Espresso Premium Spurious batch messages

Spurious batch messages

Posted: October 9, 2017 at 3:35 am


greyowl

October 9, 2017 at 3:35 am

We sometimes see spurious batch messages with weird-looking addresses waiting to be processed and apparently blocking the sending of intentional batch messages. null
Any idea where they come from or how to eliminate them?


greyowl

October 9, 2017 at 3:37 am

Queued for Generating


greyowl

October 9, 2017 at 3:37 am

I’m trying to send a screenshot. How can I do that?


greyowl

October 9, 2017 at 3:39 am

When I click on the spanner (wrench) I get the error message: The EE_Message_Registrations_incoming_data class expects an array of EE_Registration objects. EE_Messages_Registrations_incoming_data – __construct – 31


greyowl

October 9, 2017 at 3:40 am

Or, in the second case, the following error message:
An error has occurred:
The messages were not generated. This could mean there is already a batch being generated on a separate request, or because the selected messages are not ready for generation. Please wait a minute or two and try again.


Tony

  • Support Staff

October 9, 2017 at 3:41 am

Hi there,

What makes you say they are blocking the other batch messages?

For screenshots you’ll need to host the image and post the link:

https://eventespresso.com/wiki/troubleshooting-checklist/#screenshots


greyowl

October 9, 2017 at 3:43 am

The spurious messages were addressed to:
arrivenot@emailbad.fr and
buns@fcn.al
Obviously invalid.


greyowl

October 9, 2017 at 3:51 am

Can you see this?
https://greyowl.wordpress.com/wp-admin/upload.php?item=747


greyowl

October 9, 2017 at 3:53 am

The subsequent messages wait in the Q. If I click the spanner, it shows the error message.


greyowl

October 9, 2017 at 3:56 am

I deleted the waiting messages and then generated them anew. They still don’t go but show the error message:
An error has occurred:
The messages were not generated. This could mean there is already a batch being generated on a separate request, or because the selected messages are not ready for generation. Please wait a minute or two and try again.


greyowl

October 9, 2017 at 4:15 am

After some time they did get sent, but only after deleting the spurious messages.


Tony

  • Support Staff

October 11, 2017 at 4:11 am

The spurious messages were addressed to:
arrivenot@emailbad.fr and
buns@fcn.al
Obviously invalid.

So you have registrations using invalid email addresses, and you’re selecting those registrations to send a batch email to?

Then those batch messages remain in the queue and block other messages?

Can you see this?
https://greyowl.wordpress.com/wp-admin/upload.php?item=747

No that’s a link to the dashboard, we need the Full URL, for example:

domain.com/wp-content/uploads/2017/somefile.jpg

I deleted the waiting messages and then generated them anew. They still don’t go but show the error message:

The messages system uses WP-Cron to process messages, are you allowing time for the messages to work through the system?


greyowl

October 11, 2017 at 4:54 am

No, we have no registrations with such invalid addresses! These messages appeared from nowhere in the Q for processing. I have no idea where they can possibly come from.
I’ll try to send a better screenshot when I’m back home…


Tony

  • Support Staff

October 11, 2017 at 5:00 am

Its simply not possible for EE to randomly generate email addresses, especially the address you mentioned above.

Go to Event Espresso -> Registrations -> Contact list (tab)

Search for the 2 email addresses mentioned above, do you get any hits?


greyowl

October 11, 2017 at 11:44 am

I have checked the Registrations and there are no such addresses. I’ve also uploaded the screenshot here: https://greyowl.files.wordpress.com/2017/10/bildschirmfoto-2017-10-09-um-11-14-54.png


Tony

  • Support Staff

October 11, 2017 at 12:24 pm

I have checked the Registrations

I mentioned contacts, not registrations. Did you check the contact list?

Are these definitely batch messages types?

Under ‘Message type’ in the message queue what does it show – http://take.ms/XoScv


asteiner

October 17, 2017 at 6:31 am

So these emails (‘buns@fcn.al’, ‘arrivenot@emailbad.fr’) are generated by EE.. This is what I have found in “/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/data_class/EE_Messages_Preview_incoming_data.class.php” line 185

    /**
     * This just returns an array of dummy attendee objects that we'll use to attach to events for our preview data
     *
     * @access private
     * @return array an array of attendee objects
     */
    private function _get_some_attendees()
    {
        //let's just setup a dummy array of various attendee details
        $dummy_attendees = array(
            0 => array(
                'Luke',
                'Skywalker',
                'farfaraway@galaxy.sp',
                '804 Bantha Dr.',
                'Complex 8',
                'Mos Eisley',
                32,
                'US',
                'f0r3e',
                '222-333-4763',
                false,
                '999999991'
            ),
            1 => array(
                'Princess',
                'Leia',
                'buns@fcn.al',
                '1456 Valley Way Boulevard',
                'Suite 9',
                'Alderaan',
                15,
                'US',
                'c1h2c',
                '78-123-111-1111',
                false,
                '999999992'
            ),
            2 => array(
                'Yoda',
                'I Am',
                'arrivenot@emailbad.fr',
                '4th Tree',
                '5th Knot',
                'Marsh',
                22,
                'US',
                'l18n',
                '999-999-9999',
                false,
                '999999993'
            ),
        );
        
        //let's generate the attendee objects
        $attendees = array();
        $var_array = array(
            'fname',
            'lname',
            'email',
            'address',
            'address2',
            'city',
            'staid',
            'cntry',
            'zip',
            'phone',
            'deleted',
            'attid'
        );
        
        //EE_Registry::instance()->load_class( 'Attendee', array(), FALSE, false, TRUE );
        foreach ($dummy_attendees as $dummy) {
            $att = array_combine($var_array, $dummy);
            extract($att);
            /** @var $fname string */
            /** @var $lname string */
            /** @var $address string */
            /** @var $address2 string */
            /** @var $city string */
            /** @var $staid string */
            /** @var $cntry string */
            /** @var $zip string */
            /** @var $email string */
            /** @var $phone string */
            /** @var $attid string */
            $attendees[$attid] = EE_Attendee::new_instance(
                array(
                    'ATT_fname'    => $fname,
                    'ATT_lname'    => $lname,
                    'ATT_address'  => $address,
                    'ATT_address2' => $address2,
                    'ATT_city'     => $city,
                    'STA_ID'       => $staid,
                    'CNT_ISO'      => $cntry,
                    'ATT_zip'      => $zip,
                    'ATT_email'    => $email,
                    'ATT_phone'    => $phone,
                    'ATT_ID'       => $attid
                )
            );
        }
        
        return $attendees;
    }


Tony

  • Support Staff

October 17, 2017 at 8:14 am

Hmm, ok. Those are the dummy details used for the message previews, have you been sending testing messages recently?

Which version number of EE are you using?


greyowl

October 19, 2017 at 1:57 pm

Yes, we have been sending test messages. We have “Event Espresso – 4.9.46.p Version 4.8.2” (Copy-pasted from footer)


Josh

  • Support Staff

October 25, 2017 at 9:07 am

You can update to the current version of Event Espresso 4 to prevent future tests from creating entries in the message activity list table. Version 4.9.47.p included this fix:

Fix generating preview for registration type messages creating entries in the message activity list table

Then you can delete the messages that were sent as tests from the queue if they’re still in the queue.

The support post ‘Spurious batch messages’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso