Support

April 27, 2015 at 4:14 pm

Hello,

Could you please create a temporary WordPress admin login so we can take a closer look at this issue?

Specifically, we would like to look at your database using a tool like PHPMyAdmin.

Please share that temporary login through the secure link below:

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

Thanks

—
Lorenzo

May 6, 2015 at 4:27 pm

Hi, I replied to your email earlier. I’ve asked a developer to take a look at the database to see if we can determine why its not completing.

I’ll follow up with you tomorrow via email.

Thanks

—
Lorenzo

May 11, 2015 at 5:41 am

Hi there,

That statement is false, at no point will Event Espresso set your memory limit and yes a VPS with a single site should be more than adequate to run Event Espresso.

WordPress itself sets the memory limit to 40MB IF your php_memory limit within php.ini is set to a lower value.

You mentioned a Visual Editor, would this be Visual Composer (VC) or another? Most visual editors are heavy on the resources and Event Espresso also uses more memory than most plugins (because it does a lot more).

VC recommends 128MB as standard.

Can you go to Event Espresso -> Maintenance -> System Information.

Search for wp_memory and you’ll find something like this – http://take.ms/I9TbG

Can you tell me the value displayed there please? (Note Event Espresso simply reads this value and does not set it)

You can usually alter this value by editing your wp-config.php file, details here:

http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

But its basically adding (or editing if currently there):

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

However it depends on your host setup as this setting can be overridden on your server.

May 11, 2015 at 6:08 pm

Hi, could you let us know the value that is set for wp_memory in the system information page?

https://monosnap.com/file/O3B1P6d47f06ckVEQuC8icWYfzSx7P

You mentioned that you tried 512M via your wp-config.php file but what does it show in the system information screen?

—
Lorenzo

May 12, 2015 at 2:25 pm

“Fatal error: Out of memory (allocated 90177536) (tried to allocate 7680 bytes) in …”

90177536 byes == ~90MB

What this usually means is that your host is overriding the value you set within wp-config.php.

Starting with the easiest to check, where are you adding the wp_memory_limit definition? Within the wp-config.php file it must be above this line:

require_once(ABSPATH . 'wp-settings.php');

Usually just above this comment:

/* That’s all, stop editing! Happy blogging. */

http://take.ms/lqtG2

What kind of hosting package are you using?

May 12, 2015 at 3:10 pm

Ok, so that should apply fine.

Have you tried restarting apache?

May 13, 2015 at 12:53 am

Hmm, strange.

It seems to all stop when disabling EE but that doesn’t mean that’s it.

Event Espresso is taking you over your limit, because your limit is still at 90MB.

With Event Espresso disabled install a plugin such as this:

https://wordpress.org/plugins/wp-memory-usage/

That will add something like this – http://take.ms/i7oX3 to you dashboard.

It shows your current memory limit and your current memory consumption.

What does it show your memory limit as?

Do you have any custom php.ini files saved within wordpress? Usually within /wp-admin/ but could also be within root.

May 13, 2015 at 4:11 pm

I noticed you’d sent log in details so I took a quick look over the files.

There’s something really strange going on with the server set-up.

php_info() within root shows a memory limit of 300M, WP shows a limit of 1024M, EE shows a limit of 80M, php.ini with wp-admin has 100M, php.ini.backup has the limit at 72M.

I’m not sure which should/would be used but ‘something’ is a miss with this setup, there’s just too many different values being shown. .htaccess also shows multiple version of the same rulesets.

I would recommend contacting your host and have them investigate this further, I doubt very much this is an issue with Event Espresso, but a server config issue, unfortunately what within the config is currently a mystery.

You host should be able to provide further details as they will know their server better than anyone.

May 13, 2015 at 4:28 pm

I also noticed you have a /plugins/ directory within /cache/ that contains all of the sites plugins.

Then wp-content/plugins/ also has plugins within there.

That’s not something I’ve seen before and I’m unsure how that would work, is that something you have set up yourself?

May 13, 2015 at 5:12 pm

It’s not something that I’ve setup or know exactly why that’s like that. Possibly the host troubleshooting the issues or an old caching plugin. There’s no caching currently.

I’ve not seen plugins stored within the cache directory before, I don’t think they would actually work from there so I’m not sure why it would be set up that way.

The host is currently looking into the memory issues more to see if they can find the 90meg limit it looks like it’s set to.

It’s a really strange issue, please let us know what your host finds.

May 15, 2015 at 7:32 am

Thank you for letting us know, Adam.

I’m glad your host found the cause and your now back up an running, any further problems just let us know.

Have a great day.