Support

November 30, 2018 at 8:56 am

In regard to your comment on the out of date codebase – quite simply, the client doesn’t wish to pay yearly for support and is running on this version. It meets their needs. In fairness, I’m not looking for support from EE on this issue as I’m fully aware we’re not paying for and are using an outdated version. I just felt this is a big enough issue that it’s going to impact a number of your clients running older versions and wanted to make you aware if you weren’t already that there were likely changes made on your end that are causing a severely negative impact to clients on an older version.

The redirect works on a browser for the feed – it appears the curl request does not follow the redirect and just hangs.

function espresso_news_dashboard_widget_function() {
	wp_widget_rss_output('https://eventespresso.com/feed/', array('items' => 5, 'show_author' => 1, 'show_date' => 1, 'show_summary' => 0));
}

Issue 2 – This does not connect & hangs until it times out:

if (file_exists(EVENT_ESPRESSO_PLUGINFULLPATH . 'class/pue/pue-client.php')) { //include the file
			require(EVENT_ESPRESSO_PLUGINFULLPATH . 'class/pue/pue-client.php' );
			$api_key = isset($org_options['site_license_key']) ? $org_options['site_license_key'] : '';
			$host_server_url = 'https://eventespresso.com'; //this needs to be the host server where plugin update engine is installed.
			$plugin_slug = array(
				'free' => array('L' => 'event-espresso-free'),
				'premium' => array('P' => 'event-espresso'),
				'prerelease' => array('B' => 'event-espresso-pr'),
				);
			$options = array(
			//	'optionName' => '', //(optional) - used as the reference for saving update information in the clients options table.  Will be automatically set if left blank.
				'apikey' => $api_key, //(required), you will need to obtain the apikey that the client gets from your site and then saves in their sites options table (see 'getting an api-key' below)
				'lang_domain' => 'event_espresso', //(optional) - put here whatever reference you are using for the localization of your plugin (if it's localized).  That way strings in this file will be included in the translation for your plugin.
				'checkPeriod' => '12', //(optional) - use this parameter to indicate how often you want the client's install to ping your server for update checks.  The integer indicates hours.  If you don't include this parameter it will default to 12 hours.
				'option_key' => 'site_license_key', //this is what is used to reference the api_key in your plugin options.  PUE uses this to trigger updating your information message whenever this option_key is modified.
				'options_page_slug' => 'event_espresso',
				'plugin_basename' => EVENT_ESPRESSO_WPPLUGINPATH,
				'use_wp_update' => TRUE, //if TRUE then you want FREE versions of the plugin to be updated from WP
				'extra_stats' => $extra_stats
			);
			$check_for_updates = new PluginUpdateEngineChecker($host_server_url, $plugin_slug, $options); //initiate the class and start the plugin update engine!
		}

I’m noticing both of these are going to an http endpoint rather than https so maybe you’ve made changes to your site to no longer allow connections on http and force a redirect to https at all times? Just a thought.