Support

January 30, 2017 at 5:59 pm

I’m not sure what you mean? Can you add a screenshot of what you see?

https://eventespresso.com/wiki/troubleshooting-checklist/#screenshots

January 30, 2017 at 6:09 pm

You don’t extract the zip file, you leave it as is.

Then within your plugins menu you select the full .ZIP file, NOT one of the files from within it.

So save the zip to your desktop for example.

Then select that zip/archive from the plugins menu.

January 30, 2017 at 6:14 pm

Its automatically opening up on your mac, I’m a windows users so don’t know how to prevent that.

However I can update the WP user integration add-on for you if you prefer?

I can do that if you send temporary login details using this form:

https://eventespresso.com/send-login-details/

January 30, 2017 at 6:28 pm

Its best to create a new user yes.

Just go to Dashboard -> Users -> Add new.

Set a user name (we need this)

Set a password (we need this)

You can use any email address you prefer, a dummy email will work.

Set the role to Admin.

Then create the user and provide the details you used in the above form.

January 31, 2017 at 8:19 am

No the ATOS message has nothing to do with the other warnings. The warnings are for the older EE3 add-ons that are installed on your site, that still need an update. Your account page has the newer versions of the EE3 add-ons.

January 31, 2017 at 9:19 am

Hi Nick,

Apologies for the delay in my response.

The error your seeing often happens when a plugin is trying to start buffering, inside another buffer. It’s common for caching plugins to buffer the entire response which can cause this however looking over your site there are no caching plugins other than a ‘drop-in’ plugin which currently states is inactive as you need to enable it within your wp-config.php file for it to work.

Another possible cause is the PHP is running out of memory during a buffer and then throwing an error but we can’t see it because of lack of memory and the fact that’s its within the buffer. Your site is currently running on 40 MB of memory which is considered a little on the low side, personally I would recommend 96 MB or more.

So my first recommendation is to increase the amount of available memory to the site, to do that your going to need FTP access to the server, do you have those details?

You need to add this to your wp-config.php file (its within the root directory of your site):

define( 'WP_MEMORY_LIMIT', '96M' );

(Or if there is a value already set in the file increase it to 96)

If you don’t have FTP access to the site or are in any way unsure about making the above change I recommend creating a ticket with your hosting company to have them increase the value for you. The wp-config.php is vital for your site to function, do not remove any values from it and make sure you have a backup of the original file before changing it.

Its also possible this is a theme conflict as mentioned above, I see there is an update available for your theme which may include a fix for this, however I don’t use that theme so I’m not 100% sure if that’s the case.

January 31, 2017 at 9:55 am

Because everything was working before we did this update with EE3 my assumption is that the air is found there, but that could be a naïve assumption.

Whilst I do fully understand why this would appear to be an issue with EE3 its important to note we’ve not had any other reports of this from any sites running the latest version of EE3 which points to a conflict rather than an issue with the code.

As there’s no error message to point to EE and no other reports this again points to a conflict.

Because we are aiming to get this fixed ASAP which of these options would you suggest we move forward with first.

My first recommendation is to increase the available memory to the site.

I checked within your theme options system report and they actually recommend 128MB, your site may have just been getting by on 40MB but no longer does (again, no error message so just educated guesses currently)

If I’m hearing you correctly it appears that the cash plug-in is not the issue, as it is not activated.

Correct, as far as I can tell the drop-in cache plugin is currently de-activated. It may well still be caching, server side maybe? But as far as I can tell you don’t have caching enabled.

I do not understand why the memory would be an issue since this was fully functioning before we purchase the new support license with you and did the upgrade to the newest version of EE3.

Same reason above, you may have been just on the end of available memory, the updates now take you over the amount of memory needed.

Finally if it’s a theme issue, and again pardon my naivety, but wouldn’t there be issues on the main pages and not just on the EE registration pages?

Depends if every other page uses output_buffering, if not then whatever is using the buffer can continue to do so, its when something else tries to use a buffer this seems to happen.

What I did to test if this is a theme conflict is to live preview one of the default themes from within the dashboard.

If you go to Dashboard -> Appearance -> Themes.

Hover over the ‘twentyfourteen’ theme and click the Live Preview button – http://take.ms/YNUGC

What that does it use that theme to load your site to let you (the admin) view the pages and how it would look. You’ll notice the public events page works fine within that theme – http://take.ms/JJWJw

As do the EE pages – http://take.ms/40SBH

So if EE was throwing that error it also should not work when viewing that theme.

I’m more than happy to increase the memory limit on your site for you if you can provide FTP details using the same form you did previously, however if increasing the memory limit then shows this is a conflict with the theme/plugin you will need to purchase a support token for us to investigate further.

Does that work better for you?