|
icl
|
May 8, 2018 at 1:49 pm
I have a brand new install of EE4, and I’m getting this error message when creating or editing an event – The “EE_Declined_Registration_message_type” message type class can’t be loaded from EE_Declined_Registration_message_type.class.php. Likely there is a typo in the class name or the file name. EE_Message_Type_Collection_Loader – load_message_types_from_folder – 90
I see another user had this issue (https://eventespresso.com/topic/the-ee_declined_registration_message_type-error-message/). I checked the folder structure, and the file is there.
Please advise how to fix the error.
WordPress Version: 4.9.5
PHP Version: 7.0.10
MySQL Version: 5.7.14
Event Espresso Version: 4.9.61.p
|
|
Josh
|
May 8, 2018 at 2:34 pm
Can you check the contents of the file? It should have some code that starts with this:
class EE_Declined_Registration_message_type extends EE_Registration_Base_message_type
{
|
|
icl
|
May 8, 2018 at 2:42 pm
It looks like all the code is there.
<?php
if (!defined('EVENT_ESPRESSO_VERSION') )
exit('NO direct script access allowed');
/**
* Event Espresso
*
* Event Registration and Management Plugin for WordPress
*
* @ package Event Espresso
* @ author Seth Shoultes
* @ copyright (c) 2008-2011 Event Espresso All Rights Reserved.
* @ license https://eventespresso.com/support/terms-conditions/ * see Plugin Licensing *
* @ link http://www.eventespresso.com
* @ version 4.0
*
* ------------------------------------------------------------------------
*
* EE_Declined_Registration_message_type
*
* Handles frontend registration message types.
*
* @package Event Espresso
* @subpackage includes/core/messages/message_type/EE_Declined_Registration_message_type.class.php
* @author Darren Ethier
*
* ------------------------------------------------------------------------
*/
class EE_Declined_Registration_message_type extends EE_Registration_Base_message_type {
public function __construct() {
$this->name = 'declined_registration';
$this->description = __('This message type is for messages sent to registrants when their registration is declined.', 'event_espresso');
$this->label = array(
'singular' => __('registration declined', 'event_espresso'),
'plural' => __('registrations declined', 'event_espresso')
);
$this->_master_templates = array(
'email' => 'not_approved_registration'
);
parent::__construct();
}
/**
* _set_contexts
* This sets up the contexts associated with the message_type
*
* @access protected
* @return void
*/
protected function _set_contexts() {
$this->_context_label = array(
'label' => __('recipient', 'event_espresso'),
'plural' => __('recipients', 'event_espresso'),
'description' => __('Recipient\'s are who will receive the template. You may want different registration details sent out depending on who the recipient is', 'event_espresso')
);
$this->_contexts = array(
'admin' => array(
'label' => __('Event Admin', 'event_espresso'),
'description' => __('This template is what event administrators will receive with an declined registration', 'event_espresso')
),
'attendee' => array(
'label' => __('Registrant', 'event_espresso'),
'description' => __('This template is what each registrant for the event will receive when their registration is declined.', 'event_espresso')
)
);
}
} //end EE_Declined_Registration_message_type class
|
|
Josh
|
May 8, 2018 at 3:33 pm
I’m afraid I’d need to know the cause of this error to be able to advise a fix. If there’s an issue with file permissions where some files within Event Espresso are not allowed to be read by PHP, then the file permissions need to be set correctly.
You could also check with the server admin to see if they have logged any errors that led up to that particular file not loading.
|
|
icl
|
May 9, 2018 at 12:12 pm
The issue is incompatibility with PHP 7. I switched to an older version of PHP (5.6.25) and the errors cleared up. Are there any workarounds to make EE4 compatible with PHP 7?
WordPress requirements recommend PHP 7.2 and our host’s optimized servers are using it as well.
|
|
Josh
|
May 9, 2018 at 12:25 pm
Event Espresso 4 is compatible with PHP 7. We know it is compatible because Eventsmart.com runs Event Espresso 4 and its servers have PHP 7. What’s probably happening is the host’s PHP 7 configuration has some type of bytecode (Opache or APC) caching activated, where the 5.6 configuration doesn’t have bytecode caching activated.
Event Espresso 4 may have issues with bytecode caching because some server configurations for bytecode caching may result in
class EE_Declined_Registration_message_type
getting changed to something like
class \xa0L\xdaor\x7f
|
