Posted: September 20, 2013 at 7:10 am
|
I purchased the business version of Event Espresso yesterday and unzipped all the files on my computer then uploaded them to my FTP, following the installation directions. When I go to Plugins on my wordpress site and try to activate Event Espresso I get a “Fatal Error” message but nothing else, no descriptor like I’ve seen in the other posts on here which would lead me to know what the error is involving. It just says ” Plugin could not be activated because it triggered a fatal error.” Wordpress Version: 3.6.1 Thanks! |
This may require turning on the WordPress Debugging constant. If it’s possible to do so, can you please send temporary WordPress admin level log in credentials and working FTP credentials via the contact form on this page so we can investigate further? |
|
September 20, 2013 at 11:09 am Hi Nichole, When I tried to log into the WP admin it displays this: Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. The FTP credentials will not allow me to log in as well. The first issue may be resolved by changing a security setting on your server as mentioned in this thread from the wp.org forums: http://wordpress.org/support/topic/error-service-temporarily-unavailable |
|
|
September 20, 2013 at 11:30 am I’m really sorry about that and not sure why that is. For some reason the school I work at has my server site blocked so I cannot sign in currently and change the security settings. I expect to be home by 3:30pm CST and should be able to get onto the server at that point and resend you the credentials if that’s ok. It’s weird though because when I go into another browser and log onto my site with the credentials that I gave you, it worked for me. Same with when I log into the FTP server using WinSCP on my computer. Not saying you’re doing anything wrong because you’re the pro and I’m the newbie but I wonder what I’m missing. Maybe it’s because it knows my IP address? Either way, once I get home I’ll log onto my server and change the security settings. Sorry for the inconvenience and thank you very much for your help and time. |
September 20, 2013 at 11:54 am I can log into the admin now, but the FTP client says this when I try to FTP in: The user name or password was not accepted by the server. The site may be inaccessible or your password may be incorrect. Please double-check your login settings. If I had FTP credentials I would go into the wp-config.php file and set WP-DEBUG to true. While there I would also try increasing the amount of memory allowed for PHP (which can help in cases like this one) http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP What may be happening is the limit is set at 40MB. Since the Memory usage on your site is at 39.81MB right now activating a memory consuming plugin like Event Espresso might throw the fatal error. |
|
|
September 20, 2013 at 12:41 pm Thanks, Josh, I’m glad that you were able to get into the site now. I was able to go in through FTP on my end and set WP-DEBUG to true. I tried to set the PHP memory to be increased but I wasn’t sure where to do so. I tried to within the WP-DEBUG file but that didn’t seem to help. My husband was able to get into the FTP with the credentials that I sent you but he also set up a new user so I will send you those credentials the way I did last time. Thank you! |
September 20, 2013 at 12:48 pm If increasing the memory limit by adding
to wp-config.php does not increase the memory limit there may be a limit set by the host that’s overriding this. You can contact the hosting company’s support staff to find out if they can raise the limit. |
|
Hi Nicole, I’ve checked through the admin and the files and I’m not finding anything out of order. The custom files add-on was not installed in the correct location so I deleted it from there (it needs to be installed in /wp-content/uploads/espresso/ as directed here: https://eventespresso.com/wiki/custom-files-addon/) Have you tried ruling out a plugin or theme conflict by deactivating all the other plugins and temporarily switching to the default WP theme? I have used the super skeleton theme successfully with Event Espresso myself, but there’s that slight chance there is a modification to your copy that could potentially cause an issue. |
|
You can scratch that. With a little trial and error I was able to get the plugin to install by commenting out line 43 of espresso.php which kicks off the auto update feature. I’m going to check with one of the developers to see what to do next. For now you can use Event Espresso and it will function, the exception is the auto updater will not work. |
|
|
Great! Thank you! |
|
Though now I’m not able to log into my site. It says server error. I was able to log in once and then got this: Session expired Please log in again. The login page will open in a new window. After logging in you can close it and return to this page. + β Γ Total Arguments:1 Total Files:0 wp-content/themes/super-skeleton/update-notifier.php:47 – get_theme_data is deprecated since version 3.4! Use wp_get_theme() instead. |
Sorry about that. You should be able to log in now. I deactivated Event Espresso. While I was able to activate Event Espresso, loading up the Event Espresso>General Settings screen locked up the admin. I set up an error log file (which I am going to delete for security purposes). This is the error that shows up when Event Espresso is activated (after the admin crashes) :
At this point I can advise checking with the host about getting more memory allocated. There was another fatal error that was logged that was related to S2 Members that should be checked into as well:
These might be related to the s2-hacks.php file that’s in the wp-content/mu-plugins file. I don’t really know much about s2 to say for sure, but the developer who added this may be able to look into it. |
|
|
Ok, thank you. I’ll check into both of those things and hopefully get this resolved. |
You’re welcome. Thank you for your patience and I’m sorry I couldn’t get the plugin working, this was a tricky one because it wasn’t showing any errors until I set up the log file. |
|
|
Hello again! My husband who help me set up this site looked into the S2Member-hack file but didn’t see anything wrong with it and was wondering if you still had the log that you saw the error in that I’d be able to show him. I’m guessing you don’t since you said you got rid of it for security reasons but thought I’d ask anyway π Let me know what you think regarding the ‘not sufficient access’ problem and if you still have the passwords from last week; they’re the same if you need to look into the site at all. Thanks! |
September 27, 2013 at 11:23 am Hi Nicole, It may require rebooting the server after increasing the memory. I was getting the exact same error last week after activating Event Espresso where it said I do not have the permissions. What was happening was the site was crashing when I followed the link to the settings and that was triggering the No permissions error. I can turn error logging on again and send you a copy of the error log when I get a minute this afternoon. In the meantime can you check with the server admin to see if they will reboot the server? |
|
Hi again, I did some further investigating and I logged back in with the Super Admin account you set up for us and set up an admin account. While logged in with the regular admin account I was able to configure Event Espresso. So it looks like you may need to set up an admin account with the way S2 is set up on this site in order to use Event Espresso. I will delete the admin account I set up. Re: the log file: I left the code that generates the log file in wp-config.php but I commented it out so that it would not keep logging every error thrown on the site. You can make it log all the errors to a “debug.log” file in the wp-content directory by uncommenting in lines 84-88 of wp-config.php so it looks like this: if ( WP_DEBUG ) { define( 'WP_DEBUG_LOG', true ); define( 'WP_DEBUG_DISPLAY', false ); @ini_set( 'display_errors', 0 ); } Then two lines above that set WP_DEBUG to true: define('WP_DEBUG', true); Then when you’re done you can set WP_DEBUG back to false and delete the log file. |
|
|
Hi Josh, |
The support post ‘Unable to install: Fatal Error (w/o details)’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.