Support

Home Forums Event Espresso Premium Updated Event Espresso plugin, system stopped working

Updated Event Espresso plugin, system stopped working

Posted: September 19, 2014 at 1:17 pm


kcray

September 19, 2014 at 1:17 pm

Hi just started the upgrade, and now I can no longer get any display on the website. Its completely dead.

Not sure where to go from here.

website is register.kellycodetectors.com


Jonathan Wilson

September 19, 2014 at 2:51 pm

Hi there,

Are you trying to install EE4 while EE3 is activated? This could cause issues. You will need to remove one of the versions via ftp before activating the other.


Josh

  • Support Staff

September 19, 2014 at 3:02 pm

You’ll likely need to deactivate the plugins via FTP or PHPmyadmin.

This guide walks you through how:

http://www.wpbeginner.com/plugins/how-to-deactivate-all-plugins-when-not-able-to-access-wp-admin/


kcray

September 19, 2014 at 3:40 pm

Hi Guys,
No I updated from EE3 previously. Just received notification of a new plugin, and did the upgrade. System went dead.
I’ll try the deactivation next week. Will give you an update, but I suspect I’m going to have to do a clean reinstall. Wanted you to know in case there was something not quite right with the latest plugin, in case others have a similar experience.


Jonathan Wilson

September 19, 2014 at 3:56 pm

This is interesting. I would deleted the Event Espresso files via ftp and reinstall. That should correct the issue. Please let us know whether that works.


Josh

  • Support Staff

September 19, 2014 at 3:58 pm

You’ll be able to find out what’s wrong if you turn on WP_DEBUG.


kcray

September 22, 2014 at 7:28 am

Hi Jonathon,
Which files do you want me to delete?
Thanks


kcray

September 22, 2014 at 7:40 am

Deleted the Event Espresso folder. system still unavailable.
I’m thinking next I should delete all plugins, but one at a time to find out which one is holding wordpress down.


kcray

September 22, 2014 at 7:51 am

Deleted the following folders in this order after the main Event Espresso folder:
Ticketing
Multiple
Social
Core-reg

After i had deleted core-reg folder, wordpress came back.
Now will attempt a reinstall.


Tony

  • Support Staff

September 22, 2014 at 8:01 am

Hi kcray,

The reason for this is likely due to the fact that that Event Espresso 4 is not compatible with the EE3 Add-on’s

If you have ANY EE3 add-on’s active on the site, please de-activate these before activating EE4 (otherwise you’ll end up in exactly the same situation)


kcray

September 22, 2014 at 8:03 am

Attempted to download Event Espresso core from account webpage, message stating not commonly downloaded, could be dangerous.

What is my best strategy for re-installing at this point please?


kcray

September 22, 2014 at 8:08 am

Thanks Tony, I have removed all Event Espresso plugins, so back to clean, regards plugins. What is my best procedure to reinstall please?

Thanks


Josh

  • Support Staff

September 22, 2014 at 8:32 am

https://eventespresso.com/wiki/installing-event-espresso/


Tony

  • Support Staff

September 22, 2014 at 8:34 am

The warning is from Chrome trying to be overly helpful.

When you download EE4, click the small dropdown arrow next to it, you’ll then be given the option to keep the file – http://take.ms/ShtnD

Then go to your site. Dashboard -> Plugins -> Add New -> Upload Plugin.

Chose the file you have just downloaded and then upload that to the site.


kcray

September 22, 2014 at 9:05 am

Sorry about the Chrome thing, I should have figured that one out.
Completed the upload and install of the Plugin.
Hit Activate – System gone again.
No webpage
No Access to WordPress.
Looks like there is something wrong here that the plugin can’t get past.
Sounds like its possibly a problem with the database, so I may need to delete all my data to get this going again, I don’t known what do you think?

While I have you, FYI this forum is a little slow updating today.


Tony

  • Support Staff

September 22, 2014 at 9:08 am

While it’s currently not working, you need to enable WP_Debug so that we can see the specific error that is being thrown.

This basically involves adding:

define('WP_DEBUG', true);

to your wp_config.php file, somewhere before the line:

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

This will then tell WordPress to display the error and we can advise from there.


kcray

September 22, 2014 at 9:08 am

Sorry about the Chrome thing, I should have figured that one out.
Completed the upload and install of the Plugin.
Hit Activate – System gone again.
No webpage
No Access to WordPress.
Looks like there is something wrong here that the plugin can’t get past.
Sounds like its possibly a problem with the database, so I may need to delete all my data to get this going again, I don’t known what do you think?

While I have you, FYI this forum is a little slow updating today.

I have always been concerned about incompatibilities between the EE3 database structure, and EE4, and think the original switch over code may not have cleanly updated the table formats.


Tony

  • Support Staff

September 22, 2014 at 9:22 am

I have always been concerned about incompatibilities between the EE3 database structure, and EE4, and think the original switch over code may not have cleanly updated the table formats

EE4 does not update the tables, it actually creates separate tables.

EE4 is designed to migrate your EE3 data to EE4, but leave all of the original data intact in the original tables within the database.

Can I ask why you think this did not transfer correctly?


kcray

September 22, 2014 at 9:31 am

I had to attempt the conversion several times. you may find history on the forum. I had to reverse it the first time, and finally when I did do the upgrade, there was data missing, and some Events could not be deleted some misc stuff effecting older Event records.

I have enabled WP_Debug.
I have deleted the event espresso plugin.

Would you like me to redo the install and activate?
If it crashes, how will we find the debug info from the fail?

Thanks


Tony

  • Support Staff

September 22, 2014 at 9:49 am

Yes please re-install EE4.

Rather than just a white screen when it crashes, an error message should be displayed this time.


kcray

September 22, 2014 at 10:04 am

Ok, When I started the install, saw this message at the top of the screen>

Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /var/www/html/kellycoregistration/wp-includes/functions.php on line 3318

Still loading at the moment.
Will update shortly.


kcray

September 22, 2014 at 10:08 am

Here is the Error:

Fatal error: Uncaught exception ‘EE_Error’ with message ‘An attempt to access and/or write to a file on the server could not be completed due to a lack of sufficient credentials.’ in /var/www/html/kellycoregistration/wp-content/plugins/event-espresso-core-reg-2/core/helpers/EEH_File.helper.php:39 Stack trace: #0 /var/www/html/kellycoregistration/wp-content/plugins/event-espresso-core-reg-2/core/helpers/EEH_File.helper.php(278): EEH_File::_get_wp_filesystem() #1 /var/www/html/kellycoregistration/wp-content/plugins/event-espresso-core-reg-2/core/EE_Load_Textdomain.core.php(43): EEH_File::exists(‘/var/www/html/k…’) #2 /var/www/html/kellycoregistration/wp-content/plugins/event-espresso-core-reg-2/core/EE_System.core.php(695): EE_Load_Textdomain::load_textdomain() #3 [internal function]: EE_System->load_core_configuration(”) #4 /var/www/html/kellycoregistration/wp-includes/plugin.php(505): call_user_func_array(Array, Array) #5 /var/www/html/kellycoregistration/wp-settings.php(237): do_action(‘plugins_loaded’) #6 /var/www/ht in /var/www/html/kellycoregistration/wp-content/plugins/event-espresso-core-reg-2/core/helpers/EEH_File.helper.php on line 39


Tony

  • Support Staff

September 22, 2014 at 10:49 am

We’d like to investigate this issue further, would it be possible for you to provide us with temporary login details so we can take a look?

If so please use this form:

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

Please note, FTP details would be appreciated in this case so we can view the file structure in use.


kcray

September 22, 2014 at 11:59 am

Ok Sure,
Note I only have limited direct access thru WordPress and i have local FTP SSH access.
right now WP is dead. So I can’t login to set up special access. Do you want me to do the following first:

1, Delete the plugin Event Espresso. (this will allow WordPress to work again)
2, Set temp access passwords to WP.
3, Re-install the plugin, but not activate it.
4, Use your link for signin criteria.

This will then provide you access to the WP environment prior to activation which results in the crash.

Here is the sub-domain of the wp index page: Register.kellycodetectors.com

Let me know what you would like me to do.

Cheerz
Ray


Lorenzo Orlando Caum

  • Support Staff

September 22, 2014 at 12:23 pm

Hi Ray,

Trying renaming the existing Event Espresso folder by adding a character to the end of the folder name:

event-espresso-core-reg-2 –> event-espresso-core-reg-2a

That should deactivate the plugin and allow you to reach your WordPress dashboard to create the temporary login information.

If it doesn’t, then move the folder here (one level above the WP plugins folder)

wp-content/event-espresso-core-reg-2

Be sure to send it through the following link:

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


Lorenzo


kcray

September 22, 2014 at 12:51 pm

Ok its working that WP i mean. I sent you login info. let me know if you have problems. I also provided my cell if you want to text.

wp domain: add standard format for admin login to subdomain specified above.

Cheerz


Josh

  • Support Staff

September 22, 2014 at 2:11 pm

Hi kcray,

I followed up with the info you sent and emailed you a link to a file you can download of a patched version of EE4 that potentially fixes the filesystem issue you’re seeing. Please try this version and let us know how it goes.


kcray

September 22, 2014 at 2:58 pm

Installed the modified plugin.
Received the following error during the activation process in the admin consule:
Fatal error: Call to undefined function submit_button() in /var/www/html/kellycoregistration/wp-admin/includes/file.php on line 1144

Then checked the webpage: Has following error:
Inside a popup window with a red border:

The following errors have occurred:
The Event Espresso plugin textdomain could not be loaded because: An attempt to access and/or write to a file on the server could not be completed due to a lack of sufficient credentials.
Event Espresso logging could not be setup because: “/var/www/html/kellycoregistration/wp-content/uploads/espresso/” could not be created.Please ensure that the server and/or PHP configuration allows the current process to access the following file: “/var/www/html/kellycoregistration/wp-content/uploads/espresso/”.

Then displayed on the page:

WordPress database error: [Unknown column ‘Datetime.DTT_name’ in ‘field list’]
SELECT Datetime.DTT_ID AS ‘Datetime.DTT_ID’, Datetime.EVT_ID AS ‘Datetime.EVT_ID’, Datetime.DTT_name AS ‘Datetime.DTT_name’, Datetime.DTT_description AS ‘Datetime.DTT_description’, Datetime.DTT_EVT_start AS ‘Datetime.DTT_EVT_start’, Datetime.DTT_EVT_end AS ‘Datetime.DTT_EVT_end’, Datetime.DTT_reg_limit AS ‘Datetime.DTT_reg_limit’, Datetime.DTT_sold AS ‘Datetime.DTT_sold’, Datetime.DTT_is_primary AS ‘Datetime.DTT_is_primary’, Datetime.DTT_order AS ‘Datetime.DTT_order’, Datetime.DTT_parent AS ‘Datetime.DTT_parent’, Datetime.DTT_deleted AS ‘Datetime.DTT_deleted’, Event_CPT.ID AS ‘Event_CPT.ID’, Event_CPT.post_title AS ‘Event_CPT.post_title’, Event_CPT.post_content AS ‘Event_CPT.post_content’, Event_CPT.post_name AS ‘Event_CPT.post_name’, Event_CPT.post_date AS ‘Event_CPT.post_date’, Event_CPT.post_excerpt AS ‘Event_CPT.post_excerpt’, Event_CPT.post_modified AS ‘Event_CPT.post_modified’, Event_CPT.post_author AS ‘Event_CPT.post_author’, Event_CPT.post_parent AS ‘Event_CPT.post_parent’, Event_CPT.menu_order AS ‘Event_CPT.menu_order’, Event_CPT.post_status AS ‘Event_CPT.post_status’, Event_Meta.EVT_display_desc AS ‘Event_Meta.EVT_display_desc’, Event_Meta.EVT_display_ticket_selector AS ‘Event_Meta.EVT_display_ticket_selector’, Event_Meta.EVT_visible_on AS ‘Event_Meta.EVT_visible_on’, Event_Meta.EVT_additional_limit AS ‘Event_Meta.EVT_additional_limit’, Event_Meta.EVT_default_registration_status AS ‘Event_Meta.EVT_default_registration_status’, Event_Meta.EVT_member_only AS ‘Event_Meta.EVT_member_only’, Event_Meta.EVT_phone AS ‘Event_Meta.EVT_phone’, Event_Meta.EVT_allow_overflow AS ‘Event_Meta.EVT_allow_overflow’, Event_Meta.EVT_timezone_string AS ‘Event_Meta.EVT_timezone_string’, Event_Meta.EVT_external_URL AS ‘Event_Meta.EVT_external_URL’, Event_Meta.EVT_donations AS ‘Event_Meta.EVT_donations’, Event_CPT.ID AS ‘Event_CPT.ID’, Event_Meta.EVTM_ID AS ‘Event_Meta.EVTM_ID’ FROM wp_esp_datetime AS Datetime LEFT JOIN wp_posts AS Event_CPT ON Event_CPT.ID=Datetime.EVT_ID LEFT JOIN wp_esp_event_meta AS Event_Meta ON Event_CPT.ID = Event_Meta.EVT_ID WHERE Event_CPT.ID = 412 ORDER BY Datetime.DTT_EVT_start ASC

WordPress database error: [Unknown column ‘Datetime.DTT_name’ in ‘field list’]
SELECT Datetime.DTT_ID AS ‘Datetime.DTT_ID’, Datetime.EVT_ID AS ‘Datetime.EVT_ID’, Datetime.DTT_name AS ‘Datetime.DTT_name’, Datetime.DTT_description AS ‘Datetime.DTT_description’, Datetime.DTT_EVT_start AS ‘Datetime.DTT_EVT_start’, Datetime.DTT_EVT_end AS ‘Datetime.DTT_EVT_end’, Datetime.DTT_reg_limit AS ‘Datetime.DTT_reg_limit’, Datetime.DTT_sold AS ‘Datetime.DTT_sold’, Datetime.DTT_is_primary AS ‘Datetime.DTT_is_primary’, Datetime.DTT_order AS ‘Datetime.DTT_order’, Datetime.DTT_parent AS ‘Datetime.DTT_parent’, Datetime.DTT_deleted AS ‘Datetime.DTT_deleted’, Event_CPT.ID AS ‘Event_CPT.ID’, Event_CPT.post_title AS ‘Event_CPT.post_title’, Event_CPT.post_content AS ‘Event_CPT.post_content’, Event_CPT.post_name AS ‘Event_CPT.post_name’, Event_CPT.post_date AS ‘Event_CPT.post_date’, Event_CPT.post_excerpt AS ‘Event_CPT.post_excerpt’, Event_CPT.post_modified AS ‘Event_CPT.post_modified’, Event_CPT.post_author AS ‘Event_CPT.post_author’, Event_CPT.post_parent AS ‘Event_CPT.post_parent’, Event_CPT.menu_order AS ‘Event_CPT.menu_order’, Event_CPT.post_status AS ‘Event_CPT.post_status’, Event_Meta.EVT_display_desc AS ‘Event_Meta.EVT_display_desc’, Event_Meta.EVT_display_ticket_selector AS ‘Event_Meta.EVT_display_ticket_selector’, Event_Meta.EVT_visible_on AS ‘Event_Meta.EVT_visible_on’, Event_Meta.EVT_additional_limit AS ‘Event_Meta.EVT_additional_limit’, Event_Meta.EVT_default_registration_status AS ‘Event_Meta.EVT_default_registration_status’, Event_Meta.EVT_member_only AS ‘Event_Meta.EVT_member_only’, Event_Meta.EVT_phone AS ‘Event_Meta.EVT_phone’, Event_Meta.EVT_allow_overflow AS ‘Event_Meta.EVT_allow_overflow’, Event_Meta.EVT_timezone_string AS ‘Event_Meta.EVT_timezone_string’, Event_Meta.EVT_external_URL AS ‘Event_Meta.EVT_external_URL’, Event_Meta.EVT_donations AS ‘Event_Meta.EVT_donations’, Event_CPT.ID AS ‘Event_CPT.ID’, Event_Meta.EVTM_ID AS ‘Event_Meta.EVTM_ID’ FROM wp_esp_datetime AS Datetime LEFT JOIN wp_posts AS Event_CPT ON Event_CPT.ID=Datetime.EVT_ID LEFT JOIN wp_esp_event_meta AS Event_Meta ON Event_CPT.ID = Event_Meta.EVT_ID WHERE Event_CPT.ID = 412 AND Datetime.DTT_EVT_end >= ‘2014-09-23 01:23:09’ ORDER BY Datetime.DTT_order ASC

We are getting closer I believe which is encouraging.

Note I’m here for 30 more minutes, after that I’ll pick up again tomorrow am.

Thanks for all your good work on this!


Josh

  • Support Staff

September 22, 2014 at 3:24 pm

Hi there,

There’s a line of code that you can add to your wp-config.php file to make sure the file system gets accessed:

define( 'FS_METHOD' , 'direct' );


kcray

September 23, 2014 at 6:55 am

Hi Josh, I added the FS_METHOD to wp-config deleted the event espresso files and attempted to re-install (, now I get an error at the beginning of the install(32_core):

“Could not create directory.”

Perhaps I need to try to get the permissions correct on the server here what do you suggest?

Thanks


Josh

  • Support Staff

September 23, 2014 at 7:27 am

Hi Ray,

You could get the permissions correct on the server, but we can also make a few tweaks to the filesystem checks. I’m sending you over another copy of Event Espresso 4 you can try installing.


kcray

September 23, 2014 at 7:30 am

Ok Thanks!


kcray

September 23, 2014 at 8:50 am

Thanks for the new update.

1, I had to remove the define( ‘FS_METHOD’ , ‘direct’ ); as this was bypassing the SSH password entry and prohibiting the write capabilities. Once this was done the plugin installed and activated fine! (hooray!)

Is there a responsive WP theme you have had success with that works with Event Espresso.

Thanks for all your assistance.
Cheerz


kcray

September 23, 2014 at 8:57 am

Ok looks like I spoke too soon.
When I selected Events menu, received the following error:

An error has occurred:
Event Espresso logging could not be setup because: An attempt to access and/or write to a file on the server could not be completed due to a lack of sufficient credentials.
EE_Log – verify_filesystem – 118


Josh

  • Support Staff

September 23, 2014 at 8:58 am

Hi Ray,

Glad to hear the update worked.

I’ve been using the Gather theme from DevPress on a few of my sites and it works well with Event Espresso 4:

https://devpress.com/themes/gather/

A few good free options from the wp.org repository that we like:

https://wordpress.org/themes/eighties

https://wordpress.org/themes/sorbet


kcray

September 23, 2014 at 9:02 am

Not sure if this helps.
I reset debug to true.
I entered the SSh password and hit continue and got the following error:

An error has occurred:
Event Espresso logging could not be setup because: “/var/www/html/kellycoregistration/wp-content/uploads/espresso/” could not be created.Please ensure that the server and/or PHP configuration allows the current process to access the following file: “/var/www/html/kellycoregistration/wp-content/uploads/espresso/”.
EE_Log – verify_filesystem – 118


Josh

  • Support Staff

September 23, 2014 at 9:10 am

Hi Ray,

I’m afraid that you will not be able to run the EE logging feature on your server due to the way the file permissions are set up on your server.

You can disable the EE logging feature by going to Event Espresso > General Settings, click the Admin Options tab > and set “Enable Full Logging” to No, then save.


kcray

September 23, 2014 at 9:20 am

Ok thanks. I disabled full logging now when I go to Events, looks like there are several database errors.

If I need to clear the database and start from scratch, that’s ok as I don’t have any active events at the moment. I’m getting ready to add some in the next 30 days, so I have time to start over if this is the best solution.

Also, if you can specifically advise which permissions to change so that I’m more compatible with the software, please let me know and I’ll see if i can get the changes done without compromising the overall security for our main website. (Is it just the list you sent before?)

Thanks.
If you go to the following page, you’ll see the error.

http://register.kellycodetectors.com/


Josh

  • Support Staff

September 23, 2014 at 9:39 am

Hi Ray,

It looks like the database migration script was not run. Here’s what you can do to fix this:

1) Deactivate Event Espresso.
2) Roll back/restore the database to the backup you made before the update.
3) Reactivate Event Espresso and let it run the migration script

If you didn’t take a database backup, you can alternatively go to the Event Espresso maintenance page and reset its data. This will clear things and allow you to start from scratch.

With the server’s file permissions, I can’t give you specific advice on how to set these up because there may be a reason they are set up the way they are. I can advise checking with the server admin and ask them to check. I can share with you a guide that has what’s normally recommended for general server permissions for a standard WP installation, they are outlined here:

http://codex.wordpress.org/Changing_File_Permissions

You’ll note that they say this:

Permissions will be different from host to host, so this guide only details general principles. It cannot cover all cases. This guide applies to servers running a standard setup (note, for shared hosting using “suexec” methods, see below).

Typically, all files should be owned by your user (ftp) account on your web server, and should be writable by that account. On shared hosts, files should never be owned by the webserver process itself (sometimes this is www, or apache, or nobody user).


kcray

September 23, 2014 at 9:59 am

Tried to send you a copy of the latest errors after deactivating and re-activating the plugin. Received the following error on your forum:

FireHost Secure Cloud Hosting
This page has been blocked by FireHost Website Protection.
Please email and provide the following information such that we may investigate and resolve this blocked action.

Session ID:
Event ID:
Realm:
URL:
Source IP:
5303619857346575933
8308293770290949678
PHX01N
https://eventespresso.com/topic/updated-event-espresso-plugin-system-stopped-working/page/3/#post-119205
N/A
Secure Cloud Hosting


Josh

  • Support Staff

September 23, 2014 at 10:06 am

Hi Ray,

This is because Firehost has some strict rules about what can be posted here.

Did you try reverting to an earlier backup of the database or a database reset?


kcray

September 23, 2014 at 11:32 am

I tried to download backups, and Chrome kept saying it was malicious so I stopped.
Then rest the data, and it asked if i want to do a conversion from EE3.
I tried this, and it failed with a fatal error. I believe it sent an email of the problem to you guys.
I then restarted with default data and it finished ok.
Now I’m checking it all out.
Thanks
Ray


kcray

September 23, 2014 at 12:02 pm

Hi Guys,

When I try to create an Event, I get an error.

The number of inputs on this page has been exceeded. You cannot add anymore items (i.e. tickets, datetimes, custom fields) on this page because of your servers PHP “max_input_vars” setting.

We have not made any changes to this parameter, and it worked before but I have also asked my server admin to take a look.

(Running on a clean database)


kcray

September 23, 2014 at 12:05 pm

Am I the only person having problems with the latest update to the plugin?


Josh

  • Support Staff

September 23, 2014 at 12:16 pm

Hi Ray,

We had one other report where we can confirm one other site had a similar filesystem issue. The max_input_vars issue would likely have happened on an earlier version of Event Espresso 4. The max_input_vars issue happens when there is a combination of many ticket types + many registration form questions.

About how many ticket types are you creating?


kcray

September 23, 2014 at 12:31 pm

Looks like its a different problem.
I just reset the database. So should be clean. I have only created a couple of categories, and an Event and a venue.
Have yet to create any questions or Tickets.

I’ll report any other problems.


kcray

September 23, 2014 at 1:10 pm

Really Strange. I re-accessed categories, and I can see categories remaining from before I cleared out the database. So looks like the reset may have only been partial, and some data remaining. I’ll go check Tickets, maybe they have remained also.

When creating an Event. If I check in the Ticket area, I see the following errors:

Notice: Undefined variable: all_tickets in /var/www/html/kellycoregistration/wp-content/plugins/32-core_ab0970ca14354/caffeinated/admin/new/pricing/espresso_events_Pricing_Hooks.class.php on line 715 Warning: Invalid argument supplied for foreach() in /var/www/html/kellycoregistration/wp-content/plugins/32-core_ab0970ca14354/caffeinated/admin/new/pricing/espresso_events_Pricing_Hooks.class.php on line 715 Notice: Undefined variable: all_tickets in /var/www/html/kellycoregistration/wp-content/plugins/32-core_ab0970ca14354/caffeinated/admin/new/pricing/espresso_events_Pricing_Hooks.class.php on line 720 Warning: Invalid argument supplied for foreach() in /var/www/html/kellycoregistration/wp-content/plugins/32-core_ab0970ca14354/caffeinated/admin/new/pricing/espresso_events_Pricing_Hooks.class.php on line 1112


kcray

September 23, 2014 at 1:34 pm

You may want to re access to see what is going on.

If I stay editing an event, set the number of tickets to 300, after awhile when I publish it changes the status to Sold out.

It looks like something is loading a counter continuously and confusing the software.

Clarification on previous observation.

Venue Categories were cleared out.

Event Categories were not cleared out of the database.

Cheerz
321-276-4211


Josh

  • Support Staff

September 23, 2014 at 1:35 pm

Hi Ray,

Categories are stored in the WP taxonomies table and don’t get reset.

It sounds like a datetime and ticket did not get created for this event. Can you try clicking the Update button over on the right side of the screen?


kcray

September 23, 2014 at 1:39 pm

I started a new Event. Added a ticket this forced too many input vars.

Looks like Lorenzo is checking it at the moment.


Josh

  • Support Staff

September 23, 2014 at 1:55 pm

You will need to ask your host to increase the max_input_vars limit in the PHP ini settings.


Josh

  • Support Staff

September 23, 2014 at 3:49 pm

Hi Ray,

There’s a new update available (4.4.3.p) that includes the fix I sent you.


kcray

September 24, 2014 at 9:17 am

Look for separate email with full error listing. Firehost stopped publishing to the forum.

FireHost Secure Cloud Hosting
This page has been blocked by FireHost Website Protection.
Please email and provide the following information such that we may investigate and resolve this blocked action.

Session ID:
Event ID:
Realm:
URL:
Source IP:
5303619857348300856
8308293770345807774
PHX01N
https://eventespresso.com/topic/updated-event-espresso-plugin-system-stopped-working/page/4/#post-119317
N/A
Secure Cloud Hosting

I removed and deleted the previous plugin.
Downloaded and then installed new plugin.
When I activated the plugin, I received the following errors:

(looks like firehost does not like SQL commands in text)


Josh

  • Support Staff

September 24, 2014 at 9:36 am

Hi Ray,

I got your email. You can also post error messages to a pastebin and link here if you’d like.

The errors that you’re seeing now indicate that the database user was not give “All” permissions on the database. If this can be changed in your webhost control panel that should fix this.

Please see these related threads from the wordpress.org forums for more info:

https://wordpress.org/support/topic/new-host-database-error

https://wordpress.org/support/topic/update-command-denied-to-user

Along with the above, I did some checking on your site and it appears that it’s running an older version of PHP that did not include the max_input_vars setting. Since you were seeing issues with the max_input_vars warning, I can advise asking your host/server admin to update the server to a newer version of PHP. Please note that max_input_vars was added in PHP 5.3.9, but there have been several security updates in the PHP 5.3 branch since then.


kcray

September 24, 2014 at 10:58 am

Hi Josh,

I spoke with our site admin, and looks like we are not going to be upgrading PHP just yet. They are still researching the impact to the main website. (kellycodetectors.com)

With respect to User priv. The Administrator is concerned with security with providing ALL access to the database in the event of a hack. Is it not possible to only give access to the app for what it needs, rather than giving a user ALL privileges?

Is this something that just changed in EE4.0?

Is my best option to go back to EE3?

What do you recommend.
Cheerz


Josh

  • Support Staff

September 24, 2014 at 12:49 pm

Hi Ray,

You could install Event Espresso 4 on a server that meets EE4’s requirements (ie. a newer version of PHP and with a database user account that allows ALTER), or you could continue using your existing server AS-IS with Event Espresso 3.


kcray

September 25, 2014 at 12:13 pm

Hi Josh,
I attempted to regress to EE3, got all kinds of errors.
Do I need to do anything else other than remove the EE4 plugin and install the EE3 plugin.

Examples of errors.

Notice: Array to string conversion in /var/www/html/kellycoregistration/wp-content/plugins/event-espresso/class/espresso_log.php on line 54 Notice: Array to string conversion in /var/www/html/kellycoregistration/wp-content/plugins/event-espresso/class/espresso_log.php on line 54 Notice: Array to string conversion in /var/www/html/kellycoregistration/wp-content/plugins/event-espresso/class/espresso_log.php on line 54 Notice: Array to string conversion in /var/www/html/kellycoregistration/wp-content/plugins/event-espresso/class/espresso_log.php on line 54 Notice: Array to string conversion in /var/www/html/kellycoregistration/wp-content/plugins/event-espresso/class/espresso_log.php on line 54 Notice: Array to string conversion in /var/www/html/kellycoregistration/wp-content/plugins/event-espresso/class/espresso_log.php on line 54 Notice: Array to string conversion in /var/www/html/kellycoregistration/wp-content/plugins/event-espresso/class/espresso_log.php on line 54 Notice: Array to string conversion in /var/www/html/kellycoregistration/wp-content/plugins/event-espresso/class/espresso_log.php on line 54 Notice: Array to string conversion in /var/www/html/kellycoregistration/wp-content/plugins/event-espresso/class/espresso_log.php on line 54 Notice: Array to string conversion in /var/www/html/kellycoregistration/wp-content/plugins/event-espresso/class/espresso_log.php on line 54 Notice: Array to string conversion in /var/www/html/kellycoregistration/wp-content/plugins/event-espresso/class/espresso_log.php on line 54 Notice: Array to string conversion in /var/www/html/kellycoregistration/wp-content/plugins/event-espresso/class/espresso_log.php on line 54 Notice: Array to string conversion in /var/www/html/kellycoregistration/wp-content/plugins/event-espresso/class/espresso_log.php on line 54 Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /var/www/html/kellycoregistration/wp-includes/functions.php on line 3318


kcray

September 25, 2014 at 12:21 pm

Ok, I changed the shortcodes back to EE3 values. Took care of most.

Please check out the messages on the Home Page.


kcray

September 25, 2014 at 12:33 pm

Hold off Josh. I was told that the php version had just been updated.
its now at 5.4.32 which should now work so I’m going back to EE4 again.


Lorenzo Orlando Caum

  • Support Staff

September 25, 2014 at 1:17 pm

Hi Ray,

If you are manually switching then see these steps:

You’ll need to deactivate EE3. Then reactivate Event Espresso 4.

Also, please be sure to update the shortcodes for Event Espresso 4.

If you are restoring from a database backup, then you’ll just need to reactivate Event Espresso 4 (since your EE4 shortcodes will already be there).


Lorenzo


Josh

  • Support Staff

September 25, 2014 at 1:32 pm

Hi Ray,

You’ll also need to verify with your host that your database user has the ALTER privileges in order for Event Espresso 4 to work as expected.

The support post ‘Updated Event Espresso plugin, system stopped working’ 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.

Event Espresso