Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 How to remove debugging line from Payment Options page | Event Espresso - Staging Server
If you visit our testing site at http://sbane.knowarecms.net, and register for any Event, you will see an unwanted debugging line when you reach the page showing the payment gateway options. It appears just below the title of the page “Registration Page”, and appears to the value of an array containing the registration ID, the attendee quantity, and the price type.
I cannot locate where this value is being generated – it appears whether I have the EE General Setting for “Use Full Logging” toggled on or off. I also have looked at gateway_display.php, add_attendees_to_db.php, and payment_page.php, to no avail.
If anyone has thoughts on where else to check, please advise.
It’s actually in includes/process-registration/add_attendees_to_db.php line 162, but I’m not able to change it. The login credentials that we have are for a different user than the owner of the file and the permissions are 644.
Viewing 2 reply threads
The support post ‘How to remove debugging line from Payment Options page’ 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.