|
Peter Levine
|
November 11, 2014 at 1:16 pm
Hello,
Serious issue here: I have 4 transactions that occurred from November 4th through the 7th where the names cannot be recovered I am getting the below error.
For some reason, the primary attendee cannot be retrieved for this transaction. It is possible there is an error in the database Transactions_Admin_Page - _txn_registrant_side_meta_box - 730
I am (luckily) able to see these enrollments in my registrar. but how do I fix this? Also, can anyone direct me to where to look to prevent this from happening again? Thanks.
|
|
Garth
|
November 11, 2014 at 5:12 pm
Hi Peter,
How are you today?
Where is that error occurring, an admin page or emails or reports? Have you edited the EE core files or the system questions?
|
|
Peter Levine
|
November 13, 2014 at 2:41 pm
Hi Garth,
Things are getting better all the time. How are you?
The error is occurring in the admin panel under the transactions list. There are 4 transactions that have replaced the Primary Registrant and email fields with “Could be something wrong with the primary registration associated with this transaction in the db”. I haven’t messed with any of the EE core files.
The registrant data was saved by the credit card processor. And transactions that have occurred since show no problems. It is restricted to just these four. Therefore, I have to assume this has to be due to corrupting the database, since there was heavy traffic during this period.
At this point, can you offer insight as to exactly WHERE i manually input that information into PHPMySQL?
Much thanks.
|
|
Lorenzo Orlando Caum
|
November 13, 2014 at 3:17 pm
Hi Peter, since there are four transactions, I think a better option would be to remove those via the database and then manually add the registrations through the Add New Registrations button in the WP dashboard.
This can be found by going to Event Espresso –> Events. Then hover over the name of the event and click on Registrations.
For removing the bad information, try this:
1a) Backup your database
1b) Pull the site onto a staging site (if possible)
2) Go to wp_esp_transactions. Locate the first transaction by looking for the datestamp and remove it. Then repeat for the other transactions
3) Go to the wp_esp_registrations. Locate the first attendee for this transaction by looking for the date and attendee information and remove it. Then repeat for the remaining transaction.
4) Go back to your transactions overview screen and it should appear okay. Also check the registrations screen.
Once you have checked both, you can manually create the four registrations again.
—
Lorenzo
|
|
Peter Levine
|
November 13, 2014 at 3:23 pm
Hi Lorenzo,
Thank you for the insight. I will try this and either close the case or let you know if I need help. Thank you.
|
|
Peter Levine
|
November 14, 2014 at 2:08 pm
To whomever is in today. Emergency. None of my transactions are getting added since November 9th. Please help.
|
|
Lorenzo Orlando Caum
|
November 14, 2014 at 3:42 pm
Hi,
What happens if you try to add a registration through the WP dashboard. Is it recorded?
—
Lorenzo
|
|
Peter Levine
|
November 14, 2014 at 4:09 pm
Hi Lorenzo,
I can indeed add entries via the wp dashboard.
|
|
Lorenzo Orlando Caum
|
November 14, 2014 at 4:43 pm
Hi,
Another plugin may be blocking or interfering with the registration information. Try re-testing with only Event Espresso and its add-ons running.
If it works, then restore a few plugins at a time and re-test again. Continue this process until it fails.
—
Lorenzo
|
|
Peter Levine
|
November 18, 2014 at 5:36 pm
Hi Lorenzo,
I updated to v. 4.4.5 right before I posted to you, which seems to have resolved the issue. I just had to add a few registrations in.
It is indeed a plugin issue. I had a conflict with Tinypass (a Paywall for selling videos online). However, this does create a problem for me, since I need both functions to run. So, I need some help with determining why these two are conflicting. I have provided the cited code below. Nothing sticks out to me. The offending bit of code on TinyPass’ side seems to be a declaration of the Tinypass file location constant. Do you have any idea what is causing this problem that I can take to Tinypass to see what is wrong on their end?
It created the following error message:
Notice: Constant TINYPASS_PLUGIN_FILE_PATH already defined in [Install location]/wp-content/plugins/tinypass/jslite/tinypass.php on line 12
Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at [Install location]/wp-content/plugins/tinypass/jslite/tinypass.php:12) in [Install location]/wp-content/plugins/event-espresso-core-reg/core/EE_Session.core.php on line 245
An error has occurred:
Notice: Constant TINYPASS_PLUGIN_FILE_PATH already defined in [Install location]/wp-content/plugins/tinypass/jslite/tinypass.php on line 12
EE_System - load_core_configuration - 703
The plugin generated 188 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.
Now, the line12-16 on Tinypass shows the following:
define(‘TINYPASS_PLUGIN_FILE_PATH’, __FILE__);
define(‘TINYPASS_PLUGIN_PATH’, plugin_dir_url(__FILE__));
define(‘TINYPASS_IMAGE_DIR’, plugin_dir_url(__FILE__) . ‘css/images/’);
define(‘TINYPASS_TPM_JS’, ‘http://code.tinypass.com/tpl/d1/tpm.js’);
And, line 245 from ee_session.core.php is a private function for opening a session with the client. Here are Lines 230- 253
/**
* @initiate session
* @access private
* @return TRUE on success, FALSE on fail
*/
private function _espresso_session() {
do_action( 'AHEE_log', __FILE__, __FUNCTION__, '' );
// is the SID being passed explicitly ?
if ( isset( $_REQUEST['EESID'] )) {
session_id( sanitize_text_field( $_REQUEST['EESID'] ));
}
// check that session has started
if ( session_id() === '' ) {
//starts a new session if one doesn't already exist, or re-initiates an existing one
session_start();/**THIS IS LINE 245**/
// set initial site access time
$this->_session_data['init_access'] = $this->_time;
// set referer
$this->_session_data[ 'pages_visited' ][ $this->_session_data['init_access'] ] = isset( $_SERVER['HTTP_REFERER'] ) ? esc_attr( $_SERVER['HTTP_REFERER'] ) : '';
}
// grab the session ID
$this->_sid = session_id();
// set the "user agent"
But any help you can give on the nature of this conflict will help me find better success with the other plugin provider.
|
|
Dean
|
November 19, 2014 at 3:06 am
Hi,
With wp_debug active those notices and errors will show, but they should have zero impact on the site once wp_debug is disabled.
The notice is due to poor coding on TinyPass’s part, but it should not be a show stopper.
The warning occurs simply because the notice is being shown.
Again, those errors do not seem to be affecting EE’s operation.
I tested TinyPass (from the WP.org repository) and I personally didn’t come across any issues in the transactions page, but it’s quite possible that I simply don’t have it set up in the same way as you.
I would try turning wp_debug OFF, but turn on define(‘WP_DEBUG_LOG’, true); and see if anything comes up in the error log after creating some registrations.
|
