Support

March 3, 2021 at 8:46 pm

I changed CalculateEventSpacesAvailableCommandHandler and commented out this line:

// $spaces_available -= $this->eventMeta()->getPromotedRegIdsArrayCount($event);

Now promoted registrations from the waitlist won’t be counted towards the number of sold tickets, correct?

How do I prevent promoted registrations from counting as sold tickets and prevent EE from keeping a reserved spot for that promoted registration? Did I do it correctly?

I tried commenting out this code as well:

// plus consider wait list registrations as taking available spaces
        $spaces_available -= $this->eventMeta()->getRegCount($event);

But it seemed to mess up everything, so I re-added that to the spaces remaining calculation.

Now, what do I need to change so that everyone on the waitlist is promoted and gets an email when a spot opens (and doesn’t count towards the sale)?

I can’t seem to figure out how UpdateRegistrationWaitListMetaDataCommandHandler code is called…

March 5, 2021 at 12:44 pm

So in EED_Wait_Lists.module.php:

I just need to comment out the following:

/*
        add_filter(
            'FHEE_EE_Event__spaces_remaining',
            array('EED_Wait_Lists', 'event_spaces_available'),
            10,
            2
        );
        add_filter(
            'FHEE_EE_Event__total_available_spaces__spaces_available',
            array('EED_Wait_Lists', 'event_spaces_available'),
            10,
            2
        );
        */

This should make the waitlist manager work as we’d like, correct? I believe removing these calculations will cause everyone in the waitlist to be promoted when a spot opens, a notification will be sent to each, and a spot will be open for anyone to take including waitlist users. If a promoted waitlist user attempts to buy the spot and it’s been taken by someone else, they should be informed a spot is no longer available, and they can be placed on the waitlist again.

Correct?

March 5, 2021 at 2:02 pm

Again, rather than commenting out core code, remove the callback function from the action.

Can you provide an example? And where should I put this code?

March 5, 2021 at 8:32 pm

Commenting out those 2 filters as mentioned above, adding the following code to core\modules\single_page_checkout\EED_Single_Page_Checkout.module.php, and extending EE_Error class to not fade-away seems to have made everything work the way we want.

EED_Single_Page_Checkout.module.php _initialize():

After these lines:

       // verify that everything has been setup correctly
            if (! ($this->_verify_transaction_and_get_registrations() && $this->_final_verifications())) {
                EED_Single_Page_Checkout::$_initialized = true;
                return;
            }
            // lock the transaction
            $this->checkout->transaction->lock();
            // make sure all of our cached objects are added to their respective model entity mappers
            $this->checkout->refresh_all_entities();
            // set amount owing
            $this->checkout->amount_owing = $this->checkout->transaction->remaining();
            // initialize each reg step, which gives them the chance to potentially alter the process

I added:

$registrations = $this->checkout->transaction->registrations($this->checkout->reg_cache_where_params, false);
			if (!empty($registrations)) {
				$firstReg = reset($registrations);
				$spacesLeft = $firstReg->event()->spaces_remaining_for_sale();
				if($spacesLeft < 1 && !$this->checkout->admin_request) {
					throw new EE_Error('<p style="color: red; font-weight: bold;">This class is sold out.&nbsp; Please <a href="' . $firstReg->event()->get_permalink() . '?join_waitlist=true" target="_blank" style="text-decoration: underline;">rejoin the waitlist</a> so you will be notified if another spot reopens!</p>', 0, null, true);
				}
			}

This is a check to make sure the event isn’t sold out when someone on the waitlist attempts to complete their registration and the slot has already been sold to someone else.

I added a new optional property in the EE_Error.core.php code so that the error message doesn’t fade away (no fade-away class is applied to the html).

I feel like this could be a configurable option to make your waitlist plugin that much more valuable. I always seem to be doing the dev work for EE for free anyways by sharing my plugins / modifications…