January 15, 2019 at 9:09 am #134323
We’re having an issue with the datbase table wp_inbound_events generating too much data and maxing out our allotment with our hosting causing the entire website to be disabled. Are there any settings that can be changes to minimize this?January 15, 2019 at 12:11 pm #134324
I’ve toyed around with writing an extension that auto deletes data X days old.
Ideally we can keep all our data though.
I could begin writing a “for now” solution and upload it here until I have a chance to polish it and list it to the public or include it in the main files.January 16, 2019 at 7:47 am #134326
That would be helpful. At the moment it’s causing the file to get too big for the amount of data we’re allowed by GoDaddy, and it only takes a few hours for it to happen so I am not sure what to do to make it work.January 16, 2019 at 11:47 am #134327
Only a few hours? Do you mind providing me with temporary access to wp-admin privately? I’d like to see what events are driving the table becoming over populated so quickly.
Did GoDaddy provide a number of max available rows? / Did they give more detail?January 16, 2019 at 1:04 pm #134328
They deleted that table in order to restore our website. In the process, somehow, the login table got corrupted as well so at the moment I can’t log in to the website myself. I have put in a support ticket to get that fixed, and as soon as it is I am switching over to Bluehost. They offer more database space as well as cron-events (can run 1 every 15 mins). Will let you know as soon as I get the new hosting set up.January 16, 2019 at 1:17 pm #134329
If I may offer recommendation. Many of my developer colleagues are recommending Kinsta right now. I don’t recommend BlueHost, Hostgator, HostMonster, or Godaddy. I do recommend WPEngine though. I’ll try Kinsta soon enough myself with a new project. I use WPEngine and DreamHost personally. WPEngine does a great job with WordPress.
They should not of deleted the table. They should have truncated it (emptied all it’s rows). There was no need to restore a backup either if that’s what they did and they were sure wp_inbound_events was the culprit.January 16, 2019 at 1:48 pm #134330
I’ll consider those, thanks! And what does that table do exactly?January 16, 2019 at 4:01 pm #134331
It’s where we store our events like, list adds, email sends, cta clicks, form submissions. My wp_inbound_events table at inboundnow.com has over a 1 million rows.January 17, 2019 at 7:13 am #134332
Okay wow! They told me that this particular table exceeded 2gb in size and that’s what caused the problem because it’s more than our hosting allowed for.January 17, 2019 at 2:32 pm #134333
It’s possible it did over time, but in less than a day I find it hard to believe. I’d have to study the table to see what’s going on though.January 17, 2019 at 2:42 pm #134334
Yeah that was my thought as well. Will prob go with Bluehost. The other hosts you mentioned look great too but they’re more expensive and seem geared to larger sites. Ours is pretty small and Bluehost should be more than sufficient and I’ve ready lots of great reviews. As soon as we’ve resolved everything with GoDaddy and migrated to Bluehost I’ll provide a login so you can take a look. Thanks again!January 29, 2019 at 8:17 am #134348This reply has been marked as private.January 29, 2019 at 11:02 pm #134356This reply has been marked as private.January 30, 2019 at 8:29 am #134364
Sounds good, thank you! And also I posted a blog post yesterday and no notification email to all leads went out. I noticed dkim sending domain says invalid. See attached. Any suggestions?
Attachments:January 30, 2019 at 8:16 pm #134370
I recommend switching to this method. Should also help with testing:
What do the automation logs say when the ‘Send Email’ action event fired? It should contain a response message from SparkPost.
The topic ‘[Account Management] wp_inbound_events’ is closed to new replies.