Support

July 7, 2015 at 7:08 am

Hi,

Do you have any caching plusing running or does your server have server level caching? If so you will need to add the EE4 pages to the no cache rules: https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/

You may also want to check the General Settings > Critical Pages tab to make sure all the pages and shortcodes are correct.

July 8, 2015 at 4:34 am

Hi Rebecca,

There are a couple of issues shown on your site.

The google web font is being loaded over HTTP whilst the page itself is HTTPS, your browser should block these connections meaning the font won’t actually load. How are you loading the font?

Also if you input your details onto one of the events, click the recaptcha and click to proceed with the registrations you’ll see this:

Warning: file_get_contents(): https:// wrapper is disabled in the server configuration by allow_url_fopen=0

Which basically means fopen has been disabled on the server, I would recommend contacting your host and have them enable allow_url_fopen on your site.

Are you running any caching plugins on the site?

July 8, 2015 at 5:35 am

Thanks, I am not very tech savvy, so not sure about how to fix the google web font thing, I use the plugin called HTTPS. Would that stop ee4 working?

No but you will need to enable HTTPS on your registration pages, we have a guide here:

https://eventespresso.com/wiki/espresso-sslhttps/

Also note that when you do this you’ll also need to enable the option ‘Force SSL Administration’ within WP HTTPS in order for everything to work as expected.

July 8, 2015 at 6:01 am

reCaptcha will need to be disabled currently.

I’ll create a ticket for this and request some feedback from our developers, however…

allow_url_fopen is also used within DOMPDF which is the library EE4 uses to generate the PDFs available for users to download. Currently there is no workaround available to allow images (and other files) to be displayed within the PDFs if allow_url_fopen has been disabled.

EE4 uses the latest version of reCaptcha and does so slightly differently than with EE3 so their may be an option to work around this, but not the PDFs.

July 8, 2015 at 6:19 am

If you go to Event Espresso -> Payment Methods -> Mijireh.

Can you check you have entered your Mijireh Access Key please – http://take.ms/Ylzb7

Double check that is the correct key from your Mijireh Dashboard and that there are no leader or trailing spaces before/after the key.

Then re-save those settings.

July 9, 2015 at 3:25 am

I set up Mijireh and now it is coming up with a ‘Nothing in your event queue’ error. I am selecting a ticket and going through the whole process.

Turns out that error is being shown on Mijireh, not EE4.

It looks like Mijireh is ‘slurping’ the wrong page, or the page it is slurping has the wrong shortcode.

Can you go to Event Espresso -> Payment Methods -> Mijireh.

At the bottom you will see an ‘Edit slurp page’ link – http://take.ms/f6HnD

Click that link, does it display a page like this? – http://take.ms/s1aBv

July 9, 2015 at 5:07 am

The PMD number on the first page is 60 though, not sure if that makes a difference?

No that should not make any difference.

On the Slurp page can you click the ‘Slurp this page’ button at the bottom to force Mijireh to re-slurp the checkout page.

Also I’d recommend disabling comments on that page, you can do this by going to Screen options and enabling the ‘Discussion’ checkbox – http://take.ms/h7lxI

That will enable this box on the page – http://take.ms/jzusL

Uncheck the checkbox for enable comments on that page, then update the page.

(Do this before re-slurping the page so the change is shown on the checkout page)

If you prefer you can also do this on /registration-checkout/ pages to remove this section – http://take.ms/ksSvf
(Dashboard -> Pages -> Registration Checkout page)

July 9, 2015 at 6:53 am

You can add something like this:

add_filter( 'FHEE__EE_Front_Controller__display_errors', 'ee_remove_notices_from_front_page' );
function ee_remove_notices_from_front_page($display_errors) {
	if( is_front_page() || is_archive() ) {
		$display_errors = false;
	}		

	return $display_errors;
}

To either your sites theme or a Site Specific Plugin to fix this.

To test this I installed that theme and created a plugin using this code – https://gist.github.com/Pebblo/4c374a93c255b57fe262

You can download and install the plugin I created from here – http://take.ms/iuzte

July 13, 2015 at 3:09 pm

An update on the reCAPTCHA issue: Event Espresso 4.7.8.p is released and includes an update to the reCAPTCHA library and reCAPTCHA will work even in allow_url_fopen is disabled.