Support

July 28, 2013 at 7:11 pm

Hi Chris,

I’ve never heard of that before. Can you try deactivating and reactivating Event Espresso and let me know if the page loads correctly?

July 29, 2013 at 9:25 am

Hi Chris,

Can you try setting the WP_DEBUG constant to true in the wp-config.php file and load up the Payment settings page? This will display any PHP errors being thrown and help narrow down the issue.

July 29, 2013 at 10:13 am

Hi Chris,

The error you posted was reported along with some discussion in this core trac ticket:

http://core.trac.wordpress.org/ticket/11831

A few of the participants in the discussion related that they didn’t have php-curl installed, which you could check to see if that’s the case for your server:

http://core.trac.wordpress.org/ticket/11831#comment:20

http://core.trac.wordpress.org/ticket/11831#comment:21

July 29, 2013 at 12:06 pm

Hi Chris,

Is the footer or the right sidebar displaying? If so, what widgets are displaying in the right side bar?

July 29, 2013 at 1:40 pm

I understand. Normally there is a footer message in the admin, as well as a right sidebar that displays two widgets in the admin on the payment options screen. The reason I’m asking about this is there may be a timeout or another error happening when the Payment options screen loads up.

If you want to empty the payment options you can do this by adding the following to your theme’s functions.php, saving, refreshing a page on your site, then remove the code and save again:

update_option ( 'event_espresso_active_gateways', '' );

July 29, 2013 at 2:25 pm

This would be an expected error since the gateway options have been wiped out. The error will go away after a gateway is activated then updated/saved. You might try a offline gateway first since the PayPal one was originally causing errors. The check gateway would be a good one to try activating then saving first.

July 29, 2013 at 3:07 pm

What happens if you try to activate the 2Checkout gateway?

July 29, 2013 at 4:24 pm

I think I know what this might be. We added a check for SSL to the settings pages, and I think your server isn’t handling it too well.

If you look in event-espresso/gateways/paypal/settings.php there is a block of code that starts around 231 that reads like this:

<?php if (espresso_check_ssl() == TRUE || ( isset($paypal_settings['force_ssl_return']) && $paypal_settings['force_ssl_return'] == 1 )) {?>
	<li>
	<label for="force_ssl_return">
		<?php _e('Force HTTPS on Return URL', 'event_espresso'); ?>
		<a class="thickbox" href="#TB_inline?height=300&width=400&inlineId=force_ssl_return"><img src="<?php echo EVENT_ESPRESSO_PLUGINFULLURL ?>/images/question-frame.png" width="16" height="16" /></a>
	</label>
	<input name="force_ssl_return" type="checkbox" value="1" <?php echo $paypal_settings['force_ssl_return'] ? 'checked="checked"' : '' ?> /></li>
	<?php }?>

What you can do is comment out the first line where it starts the check, and the last line where it ends the check.

It will look like this when you’re done:

<?php //if (espresso_check_ssl() == TRUE || ( isset($paypal_settings['force_ssl_return']) && $paypal_settings['force_ssl_return'] == 1 )) {
?>
	<li>
	<label for="force_ssl_return">
		<?php _e('Force HTTPS on Return URL', 'event_espresso'); ?>
		<a class="thickbox" href="#TB_inline?height=300&width=400&inlineId=force_ssl_return"><img src="<?php echo EVENT_ESPRESSO_PLUGINFULLURL ?>/images/question-frame.png" width="16" height="16" /></a>
	</label>
	<input name="force_ssl_return" type="checkbox" value="1" <?php echo $paypal_settings['force_ssl_return'] ? 'checked="checked"' : '' ?> /></li>
	<?php  //}
?>

July 30, 2013 at 5:08 am

Hi Chris,

If your are using offsite PayPal (normal PayPal that takes the user to the actual site) then no SSL isnt required.

I think what Josh is saying here is that some code we added to do checks for SSL were conflicting with your server so taking them out resolved the issue.

July 30, 2013 at 8:26 am

No, the SSL check was to hide the SSL options so people didnt accidentally use them and break things by having them active but without SSL.