Ben Meredith
Forum Replies Created
-
Hey @sharonmay
I’m still digging into this while I wait to hear back from you, but your post here prompted me to write a comprehensive blurb in our documentation about (a) what webhooks are and (b) what’s going on when you connect to Stripe.
Here’s that specific section of our docs (inspired by you! Thanks!)
When you first connect to Stripe using StellarPay, the entire process of establishing those webhooks is done for you automatically. During that process, StellarPay tells Stripe to check and validate the specific endpoint URL that it is configuring. If it fails, it lets you know during the “onboarding” connection to Stripe.
Since it sounds like yours did not let you know, that means that it was, at least initially, working.
Then at some point in the intervening time, it stopped working. That points to something “outside” of StellarPay (and even potentially outside of WordPress itself) blocking requests to your website.
A list of other plugins (specifically caching or security plugins) would be helpful as we continue to help you diagnose the issue.
Hey @sharonmay !
Glad you reached out, here!
StellarPay, as a part of connecting to Stripe, automatically configures webhook (event) endpoint URLs. What those do is allow Stripe to communicate whenever something happens on the Stripe side, back to your website where StellarPay is installed.
The message from Stripe there is indicating that the webhook endpoint URL that was functional no longer is. That can happen if (for example) you set up a testing site, connected to Stripe, and then later moved things to a production (live) site. Every time an event happens within Stripe that is set to go to that endpoint, it’ll try, fail, and let you know that it fails.
So, I’ll need your help to see what specific endpoint URLs are failing, and if they are legitimate, it might point to some issue on your site that is blocking them. It could also be an “all clear, nothing to worry about” moment, if the URL is for a test site or something.
Can you pass along the specific URL?
There’s no security issue with sharing a webhook URL, as the only way to *do* anything with it is to be authenitcated with a token, etc. So you sharing the endpoint URL is not a problem.
Hey @brooksnt
I am going to mark this issue as “resolved” here because we were able to isolate things. We’re still working with you on the thread in our support system to see if we can fully resolve the issue. In the meantime we added a feature request to https://stellarwp.com/stellarpay/feedback named “Advanced Fee Functionality” that would address the need for that third party plugin, and mitigate the problem in a different direction.Thanks again for bringing this to our attention, and for being one of the first wave of users for StellarPay!
Following up publicly here just so everyone stays in the loop: we’ve isolated this down to a conflict with the
WooCommerce Payment Gateway Based Feesplugin, which is causing the block-based cart page to display incorrectly when StellarPay is active.
We’re still digging to see if that’s something that we can resolve from our end, or if we’ll need to collaborate with the maker of that plugin to get this resolved. I’ll continue to follow up with you in the thread we’ve got going elsewhere, but I wanted to make sure this public thread was up to date as well.@brooksnt Thanks for that extra hoop-jumping. Even using your block markup, I’m still not able to replicate a problem.
<sarcasm>My favorite problems are ones that only happen on sites I can’t control</sarcasm>I’d like to get you access to a test installation where you can attempt to “make the problem happen” so that I can fully troubleshoot it.
Please reach out at https://stellarwp.com/contact-us/ and in that message, link to this thread and mention me (Ben Meredith) by name.
Moderators note: I am NOT asking for access to the user’s site. I am offering them access to a test environment.
Interesting.
My test site has Cart and Checkout Blocks, already.
The only thing I can think of that might cause it to not work on your site is some specific configuration related to the blocks themselves.
Can you copy the markup of the cart page (with blocks) and paste it into a reply here?Here’s an image showing how to get that info:
https://stellarwp.com/wp-content/uploads/2025/01/CleanShot-2025-01-22-at-19.04.53.png
You may need to save that to a txt file (or similar) and then pass along a link to it publicly available on the web. The support forums here don’t have a way to upload files.
Happy to get to the bottom of this!Hey @brooksnt
Glad you reached out, for sure.
I just double checked on a test site of mine and I can’t replicate exactly what you are seeing.
In looking for clues on your site (thanks for adding the link) I saw a console error that saidStellarPay (Stripe) initialization data is not available.That usually indicates that something in your setup is blocking the “object” that loads the payment element from Stripe.
During typing of this message, it looks like you may have figured it out, because I’m no longer seeing that message, and your cart is loading for me now.
Did you figure it out? I’d love to know if there’s a potentially conflicting piece of software out there!
Also, the website betterclicktotweet.com still exists, but I bet you purchased back when I was selling from wpsteward.com. All told, this just seems like a giant worst-case scenario of communication, and I feel pretty bad about that.
Hey @lifeishotblog !
Wow, this is a shocking message to get, and I feel pretty terrible that it came to you asking this publicly (but completely understand, and would have taken to publicity well before now if I were you.)
I checked my messages and I did find a recent one, but none from the years before. I’ve cancelled the subscription, and refunded as much of it as Stripe would let me refund.Please let me know (via email… I just replied there too) if there’s anything else I can help with!
Hi there!
There are two ways to exclude the “via” in a Better Click To Tweet box. First, using the block editor settings:
Unselect that setting to “include an X username” and it’ll take out the “via”
Next, with the shortcode: This shortcode will display with no “via”
[bctt tweet="This text will not have a via." via="no"]That
via="no"parameter of the shortcode is doing the work there.There’s not a way to modify the via text, just a way to include it or remove it. You can change the prompt for the reader to click (using either a shortcode parameter or a block setting), but not the via text.
There is one way that you could change that text, but it would involve translating the plugin into a different language. Not impossible, but also not easy. I’m happy to help with that, but translating the plugin falls outside the scope of free support.
- This reply was modified 1 year, 5 months ago by Ben Meredith. Reason: formatting shortcode
- This reply was modified 1 year, 5 months ago by Ben Meredith. Reason: more formatting shortcode
Forum: Reviews
In reply to: [GiveWP - Donation Plugin and Fundraising Platform] Great supportHey @jane-shakespeare !
Great to hear that Matheus was able to take care of you, and welcome to the world of GiveWP-powered donations! Let us know if you need anything at all! Your success with online donations is our number one priority!
Hey @swmarlow
First, I do appreciate the feedback here. I was *confident* that we didn’t send out 8 emails to a single person in 7 days, but then went and checked, and you won the email-lottery for sure. You were essentially registered as a part of two different “segments” of the marketing email list, so yep… that’s on us. We didn’t intentionally pummel you with those messages, but the fact remains that we did pummel. (And nobody wants to hear the pummel-splanation, after the fact, but here I am ‘splaining)
Next, I wanted to genuinely say thanks for all the years of business here. We made a ton of changes over the last year (rebranding from iThemes to SolidWP, completing a massive overhaul of our flagship backups product, and sunsetting historically-beloved-now-legacy products). We opted for over- and not under-communication of those changes. Frankly, it worked well unless you were segmented into two different “lists” and therefore getting all those communications in slightly different flavor multiple times.So yeah, we’ve cancelled your subscription here and hate to see you go, but definitely understand. If you have any other feedback or questions, definitely reach back out via email reply to your support/cancellation ticket.
Hey @lowthian !
Somehow this slipped through the cracks and I’m just now seeing it. Apologies for the slow turnaround!
As to the specific problem here, I just tried to replicate a problem and was unable to, which means either that it’s somehow specific to your site, or just that I’m not able to replicate some setting that is causing it for you. Either way, happy to get to the bottom of it.The first thing I’d do is to go to the settings at Settings > Solid Perfomance > Advanced and follow the link/button to “regenerate advanced-cache.php” to see if that resolves things.
If that doesn’t work, I’ll need you help figuring out what’s preventing your site from “seeing” that caching is enabled with Solid Performance.Thanks again for reaching out!
Thanks so much for taking the time to write this review! We really appreciate it!
Forum: Reviews
In reply to: [Solid Mail – SMTP email and logging made by SolidWP] Solid mail is superVery glad to hear this! Thanks so much for taking the time to post a review!
