|
Karen
|
December 9, 2024 at 8:15 am
On the “Payment Methods” page I’m getting a an error”
An EE_Error exception was thrown! code: TableManager – createTable – 217
”
WordPress database error: [Tablespace for table ‘xxx.wp_esp_currency_payment_method‘ exists. Please DISCARD the tablespace before IMPORT]
CREATE TABLE wp_esp_currency_payment_method ( CPM_ID int(11) NOT NULL AUTO_INCREMENT, CUR_code varchar(6) NOT NULL, PMD_ID int(11) NOT NULL, PRIMARY KEY (CPM_ID), KEY PMD_ID (PMD_ID) ) ENGINE=InnoDB DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci
”
I have no idea how to fix this! We’ve had this error for a while (we can still process through Paypal) but now there’s the Jan 2025 deadline, I need this fixed so that we can update our payment methods.
|
|
Tony
|
December 9, 2024 at 9:07 am
Hi there,
What type of hosting are you using for the site?
The above means there is currently a file within your DB taking the wp_esp_currency_payment_method namespace, it will need to be manually removed, generally, you’ll need to contact your host and have them do that for you.
Backup your database as is (you can use whichever method you prefer, for example Updraft or your host will usually have their own backup solution) then open up a ticket with them with the above error.
They should be able to remove the file for you and then EE will create the table.
|
|
Karen
|
December 9, 2024 at 10:19 am
We are using VPS Hosting. I’ll contact customer support and see what they say.
|
|
Karen
|
December 9, 2024 at 10:59 am
So customer support manually deleted the table and the error is still there… They told me to come over and talk to you all about this.
|
|
Tony
|
December 9, 2024 at 2:38 pm
This isn’t an EE issue in itself; what is happening is EE is telling WordPress to create a new table and for whatever reason, the table namespace is already taken (could have been from a previous request creating the table then it being dropped).
So customer support manually deleted…
What exactly did they do?
Deleted what file?
Did they restart MySQL afterwards? Simply deleting ‘the file’ often won’t fix this.
Was the file instantly regenerated again causing the error to be thrown again?
In fact, I’ve just done a search for this error to give another example and found your old thread on the same issue here:
https://eventespresso.com/topic/critical-error-on-payment-settings-page/
My replies to this thread would be pretty much exactly the same here, something has gone wrong within the database and when I tried to fx it for you last time I didn’t have the access required so your host needs to fix it.
I don’t know what they’ve done so I’m only guessing, but the table namespace needs to be cleared before the error will stop.
This is what I would likely try next:
https://stackoverflow.com/a/39651666
They told me to come over and talk to you all about this.
I get the feeling you’re going to end up stuck in the middle of “it’s not us, it’s them” here.
This isn’t an EE issue, it’s an issue with the database. Your host will now likely tell you it’s not an issue with the server and it ‘must’ be Event Espresso but again all EE is doing is telling WP to create a database and it can’t, becuase the namespace is taken…. that’s what needs fixing.
|
|
Karen
|
December 9, 2024 at 2:45 pm
I did give you access then, and I can resend the credentials, that’s not a problem.
What they deleted was the table “wp_esp_currency_payment_method” (and I was able to confirm that they did.)
I did read the link, and I have no idea how to even begin with that. I’m getting super frustrated with this whole situation. At least we could take payments and I didn’t really need to go into that page. But now that we are going to be forced to update the payment method and I can’t access that page at all I have to get this resolved.
It also doesn’t help that communication is so completely hampered by forcing to go through a forum format instead of a chat or even a call.
|
|
Karen
|
December 9, 2024 at 2:49 pm
Here is my last email to you:
Subject:
Re: Auto Reply: I Am Sending Login Info As Requested
From:
C— W— <cw@—.net>
Date:
1/9/24, 9:04 AM
To:
support@eventespresso.com, p—n@gmail.com
Hey there, just wanted to touch base. We gave you guys full access, including to our Cpanel and this issue is still not resolved. I also noticed that the thread we started is now closed.
Has this just fallen through the cracks? Or is someone still looking into this? Please advise.
Thank you,
On 10/2/23 3:25 PM, Event Espresso wrote:
> Auto Reply: I Am Sending Login Info As Requested
> Event Espresso
> Event Espresso
>
> Auto Reply: I Am Sending Login Info As Requested Hello —,
>
> We have received your temporary login. A member of our team will review your support request during business hours (Monday — Friday from 9AM – 6PM EDT & 1PM – 10PM GMT).
>
> Be sure to follow us on Twitter and check out our blog for updates on Event Espresso.
>
> Cheers
>
> —
> Event Espresso
>
|
|
Tony
|
December 9, 2024 at 3:59 pm
This reply has been marked as private.
|
|
Karen
|
December 10, 2024 at 8:35 am
This reply has been marked as private.
|
|
Tony
|
December 10, 2024 at 9:38 am
This reply has been marked as private.
|
|
Karen
|
December 10, 2024 at 9:41 am
Thanks! Knowing the time difference will definitely help, and I’ll most likely be addressing this off regular business hours anyway.
Thanks again, and hopefully this will get resolved soon.
|
