|
Ian
|
November 8, 2015 at 7:08 pm
Here is a previous post that didn’t really rectify anything. https://eventespresso.com/topic/the-incoming-statuses-argument-must-be-an-array-with-keys-as-the-status_id-and-2/
I have spent the last 6 weeks rebuilding the site locally and uploaded yesterday and all seemed good.
Until This morning, was presented with create database screen for the home page, Then consulted with host and found database to be totally corrupted and could not be repaired.
Main issue was database Type for some tables were innodb instead of MyISAM
We restored the site back one day to the previous day, which was still not perfect,
here is screen shot of PHPmyadmin now, (Midday AU Time Monday) https://www.dropbox.com/s/cqit4gsfuxuruf7/Screenshot%202015-11-09%2011.59.40.png?dl=0
Only tables as innodb Type are EE tables, They seem to be working right now, but I’ve had this issue before where they work for a short time and then fail.
I don’t know where to go from here as this as Event espresso has been the start of the issues.
Hope you can help soon.
|
|
Lorenzo Orlando Caum
|
November 9, 2015 at 6:33 am
Hi Ian,
I ran some searches as this report did not look familiar and I found a prior support post where a restricted DB user was in use:
https://eventespresso.com/topic/successful-install-but-error-page-when-i-click-anything-event-espresso/#post-124414
On your prior support post, you mentioned that you were in contact with the web host. Did they share any details?
On InnoDB, I don’t think that DB engine is causing this issue and I looked at a few of our testing sites and some are using all InnoDB and others have a mix of InnoDB and MyISAM.
—
Lorenzo
|
