bruschr
Forum Replies Created
-
Thanks! From what I gathered from the support agent, they suggested that since this plugin integrates with pretty much every corner of my website, including other plugins) that the query to run the upgrade was too much. He said he increased my query limit, and I could try again.
I’m nervous because I’ve brought down my site twice trying to upgrade. In the past query limit errors self-resolved over time, but my first outage was 16 hours (because I assumed), until I called to have my host reset it.
If I simply download the v.4.7 plugin zip and try to install it as a new plugin vs running the built-in upgrade, would this be less likely to cause a query limit issue? I’m skeptical that it was a query limit to blame, but that’s what the host says. It tempts me to try, but we’re not doing anything in Italian, so maybe I should leave well enough alone…
I welcome your thoughts and insight. There was a bit of a language barrier with the agent, so as I asked him to explain, I’m not sure if he was just saying “yeah” or if what I was summarizing was truly the root cause.
I believe the 500 error is the server timeout; is that right? Can you see what your memory limit is on your site? You should be able to see that from your website domain controls (not via WP-admin), or your hosting provider can tell you. I needed to adjust that value higher due to having a more complex site than average. That’s what my hosting company told me, anyway.
Forum: Reviews
In reply to: [Events Manager Pro Stripe Gateway] No issues yetUpdate 4/27/17: we’re still using this plugin successfully with Events Manager v.5.6.6.1 (our Pro has since expired) on WordPress v.4.7.4
@hampmir: I’m accepting Stripe payments for Events Manager events using this plugin: https://ww.wp.xz.cn/plugins/events-manager-pro-stripe-gateway/
It looks like it hasn’t been updated in a while, but we have used it successfully. We’re on the latest versions of WordPress and Events Manager. We once had Pro, but it has expired. The plugin still functions as expected.
That might be an option while you wait for a response from other plugin’s developers.
Just wanted to follow up in case someone with a similar issue searches back and finds this thread.
The issue ended up being a vulnerability in the Jetpack plugin, which added a set of “Share This” options to the bottom of my site’s pages, posts, events, products for sale, etc. Even though the Jetpack vulnerability looked like event spam, but this was in no way related to Events Manager, as @caimin_nwl indicated. Having the option to share via email caused the flood of outbound spam. Sadly this known-issue seems to date back to 2014(!!) and is still unresolved…yikes!
Thanks for the super speedy reply. It helped me rule out this plugin and eventually pinpoint the culprit (Jetpack). Thank you thank you!
@pixelbits I determined my issue was a vulnerability in Jetpack. I’ve deactivated it, and my email issues seem to be resolved. Not sure if you’re using Jetpack, but these email outpourings seem to be a known issue…for many years, sadly.
Shoot. Which plugin did you find that can stop it? My hosting provider keeps suspending my website over this. I need it fixed ASAP 🙁
You may be right. I’m so sorry, I didn’t even think of that since it was sharing the event. It must be another plugin.
As soon as my query limit resets and I can do more digging, I know where I’ll start looking. Thanks!
I’m encountering a similar issue, but it’s loop-sending a “share this event” email, not a test email.
Any luck? I’m not getting the AJAX error like @remcovanrossum was.
Forum: Fixing WordPress
In reply to: Changing out an image and thumbs tipneat hack!
Forum: Plugins
In reply to: [WooCommerce] Storefront Empty After Database UpdateGood grief…
I made exactly zero changes, but I clicked my store link above, and all of a sudden all 15 products are showing just fine now.
Seems to be resolved for now. Marking as such.
Magic? 🙂
Thank you for the update; I’ll check it out!
@bhogi thanks for taking the time to chime in! Last I heard the developers were considering this resolved because we couldn’t pinpoint a cause. We have a few payment buttons hanging around, but they’ve never generated a deposit. Not sure if anyone has tried using them and failed or if they just get ignored. (We’re a nonprofit; they’re donation buttons.)
We’ve moved to using a different payment gateway for our events where I was trying to use these a year ago and first started realizing there were issues. We weren’t able to provide the greatest troubleshooting info because of our infrequent events and low available spots per event.
Perhaps they’ll revisit if you have regulars who are reporting this same problem and can provide more info. Ours were also first-time customers just thinking we had a shoddy website, not so interested in helping us troubleshoot.
@phil: is there a reason to assume this has been resolved? I was hoping to hear more regarding the compatibility with WP Spam Shield as a potential culprit.
In the meantime, I’ve added a note near our donation buttons that if users don’t receive an email receipt, their donation has not gone through. We’ve been using workarounds for larger fundraising campaigns until we’re sure this is resolved. Is there some evidence it’s been permanently corrected?
Hey Phil,
Thanks for checking in. We started by testing theme and plugin conflicts as best we could per the documentation. Unfortunately due to the intermittent nature, there’s no way to know if it’s working because a plugin was turned off or because it just happened to work that time.
It’s worked 100% of the time on all my various systems and devices, all in live mode, and I cannot reproduce the issue in test. When a user had an issue, they would call me, and I would complete the checkout as if I were them. I did this on whatever machine I was using at the time using both Mac, PC, and iPhone through both Safari (iOS and Mac) and Chrome (iOS, Mac, and PC).
Echoing the statements above we (1) don’t have a test/staging site, and (2) we cannot recreate the issue. If I was able to recreate it, I would have provided that long ago as that would point to an identifiable bug. The intermittent, nonreproducable-on-demand nature of the issue is what’s making this problem so frustrating.