Support

May 23, 2016 at 9:15 am

Hi there,

I checked and I can see the events on the front end of the site here:

http://www.creativeconnect.cc/events/

Do you have a backup of the database that you can restore to?

May 23, 2016 at 10:44 am

The registration error is from a fatal error that’s happening when the ajax call is made to process the registration.

There’s likely a more specific error that can be logged if you can set up error logging by following this guide:

https://codex.wordpress.org/Debugging_in_WordPress#Example_wp-config.php_for_Debugging

May 23, 2016 at 2:39 pm

Did you check the error log to see if there was a fatal error captured when the General Settings page loaded up?

May 24, 2016 at 7:04 am

I think if here any wrong about my Event Espresso License Key ? When I put in my Support License Key,here No response

Your license key has no effect on EE function so it will not cause this.

Your license key seems to be working find and it linked to your domain. Does it show an error message specifically regarding the license key? If not there is no issue with your key.

yesterday I also make a mistake, when I Reset Event Espresso Capabilities,all data cleaned

So did you click to reset your capabilities? This button – http://take.ms/wGghT

May 24, 2016 at 10:59 am

There should be no reason why you can’t.

There are a few possible causes to this issue. You can rule these out one by one:
1) A theme conflict. You can rule this out by temporarily switching to the default WordPress theme.
2) A plugin conflict. You can rule this out by temporarily deactivating any other installed WordPress plugins.
This was mentioned before, but it bears repeating: It may also help to turn on debug mode. You can set wp_debug to true by editing the wp-config.php file.
You can use an [FTP client][1] and [a text editor][2] to access change this line to the site’s wp-config.php file:
define(‘WP_DEBUG’, true);
[1]: http://codex.wordpress.org/FTP_Clients
[2]: http://codex.wordpress.org/Editing_Files#Acceptable_External_Editors

May 25, 2016 at 4:47 am

Omg,I did everything follow you.but still can’t show full general setting.

Does it show an error when you load the page now? You should have WP_DEBUG enabled if you followed all of the steps so if theres a problem an error should be shown.

If the reason is put the code:define( ‘EE_DROP_BAD_TABLES’, TRUE); to the site’s wp-config.php ?

You added that to wp-config.php and then the error was thrown?

Remove that from wp-config.php please, you do not need it there.

It looks like there is a problem with the database table that holds your states/countries. The reg form shows no countries or states – http://take.ms/qsuwh

Have you been manually editing the database?

May 25, 2016 at 8:32 am

You might have done some damage to the database from an earlier action. You might be able to get things back on track by letting the database do a version bump/reset.

First, you deactivate Event Espresso.
Then, you edit the version number in espresso.php so it’s
4.8.44.rc.001.
Here’s a screenshot that shows the edit in context.

Then you update the file, then you reactivate Event Espresso.

• This reply was modified 8 years, 7 months ago by Josh. Reason: fomatting

May 25, 2016 at 9:27 am

Sorry, I can’t see your wp-config.php and that’s actually a good thing. If you want to fill out the secure form on this page, someone can take a look.

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

May 25, 2016 at 12:23 pm

Hi there,

It looks like you missed the part of the form where it asks for FTP credentials. You were looking for someone to check the wp-config.php file, correct? If so, you can re-send the secure form and be sure to include FTP credentials.

May 25, 2016 at 2:14 pm

We’d need some kind of file access to be able to even see the wp-config.php file and it’d be best to be able to access the wp-content/debug.log file. If you don’t have FTP access you can send, maybe you can send cpanel file access over the secure form?

May 25, 2016 at 5:18 pm

No I would not recommend doing that because that file has all the access info for your site’s database. Along with that, it won’t help narrow down what’s causing the error on your General Settings page.

May 26, 2016 at 12:21 pm

Thanks for checking. Can you check to see if your database has an _esp_state table? If it does, is there any data in it?

May 27, 2016 at 4:01 am

Just to be clear, the table will be {prefix}_esp_state

{prefix}_ is often just ‘wp_’ so the table would be wp_esp_state but it can be anything at the begging, the important part is esp_state.

If you do not have a esp_state table at all in the database then somehow it has been removed, however EE checks for all of its tables and will re-create them if they are missing.

For example here is the table in one of my test sites – http://take.ms/Got0A

If I drop that table completely – http://take.ms/3HC4Q

It has now been removed from the database – http://take.ms/61Oj4

However if I then re-visit Event Espresso -> General Settings.

wp_esp_state is regenerated within the database after the fatal error is thrown – http://take.ms/qRUeW

So it seems something is preventing EE from re-creating the table on your server.

May 27, 2016 at 1:31 pm

Your host might be able to help find out why the tables can’t be written to.

May 31, 2016 at 4:07 am

Thanks Tony, I find the wp_esp_state in my database.

You did or did not find that table?

If that table exists does it have any data within the table?

Ohh, Godaddy also can’t fix it

What did GoDaddy say about the issue?

If EE cant not create/alter tables within the database it will be due to a server config issue.