Ben Meredith
Forum Replies Created
-
Forum: Plugins
In reply to: [GiveWP - Donation Plugin and Fundraising Platform] Great butI actually appreciate you reaching out, and let me be the first to agree with you, adding custom styles to GiveWP in its current state is no fun at all (unless you use the Legacy form template, where it’s still quite easy).
There’s a long backstory to the reasons for that, and even better, a bright future ahead for developers who want to make fully customized form templates without all of the headaches that are currently involved.
First, an abbreviated backstory: back when the legacy template was the only template there was a common refrain among the vast majority of end users of “why does my form look so bad with my theme?”
That refrain was based on the fact that the legacy template was not defensively styled at all, and themes (or other plugins) could easily (and usually inadvertently) mess up the styles of GiveWP forms. Even one unspecific selector targeting
inputcould make for a difficult time making the Donation Form do the one thing it needed to do: raise money for the organization.That led to the decision (starting in version 2.7 back in 2020) to create new templates that are more resistant to style changes. The Multi-Step form template (version 2.7) and the Classic template (version 2.18) are both displayed in an iframe, and much more difficult for themes and other plugins to inadvertently mess with. Those !important declarations you’ve run into are in there, for sure.
That has led to a dramatic decrease in folks reaching out with broken forms, and an increase in requests from folks like you who want to style things. I know it’s no consolation to hear “we chose to intentionally frustrate third party developers, in favor of end users” but that’s exactly the tradeoff we made.
The legacy template is still there, and fully supported. It will be as long as I have any say in things (I do) or until there’s a way for developers and others to more easily customize form templates. If I were custom-styling a form template today, I’d use exclusively the Legacy template, and I’d disable the built-in GiveWP styles in the settings, and start fresh.
That leads to the good news: in GiveWP 3.0, we are totally overhauling the form building experience, and really the underlying architecture that is used to create forms, separating form functionality from form display in lots of ways.
This change will make way for developers like yourself to easily and programmatically create entirely custom designs. No more “I can’t style this button” and more “Here’s a simple template API to create buttons with classes to match my theme.” You can add custom styles directly into the builder!
GiveWP version 3.0 has a public roadmap that we are excited about, and inviting folks like yourself to join in. We’ve had public previews in the form of Town Hall meetings, and soon (11 May) we’re having focus groups for testing the new Beta version. You can test out the new version here: https://givewp.com/next-generation-donation-forms/
Let me know if I can clarify at all.
Forum: Plugins
In reply to: [GiveWP - Donation Plugin and Fundraising Platform] Missing transactionsHi there @polina81
If there’s no record of it at Stripe, then it didn’t happen. I know that sounds like me being a bit blunt, but that’s been my experience in 6+ years at this job. There’s never been an instance of a charge that couldn’t be traced to a Stripe transaction.
So either you’ve connected multiple Stripe accounts and it’s on some other account, or something else is going on. If it were me, I’d ask the donor for a screenshot of the transaction from their bank/card issuer and then have them approach it with Stripe to see if the Stripe team can isolate the payment by its ID or something.With no record of it on the GiveWP side, that makes it nearly impossible for us to help with, but Stripe should be able to help you find it.
There simply has to be a record of it on some Stripe account somewhere.
Hey @timlecroy !
Apologies for the slow turnaround, here. I don’t have a boldgrid account, so I am just guessing a bit. That shortcode looks just fine, so something to do with BoldGrid is preventing them from being parsed. If you can get me access to a test playground or something with boldgrid where the problem is replicable, I am more than happy to dig in and see what I can find.
Update here: The Jetpack team is handling at least part of this from their side. Here’s the PR that is currently open but will resolve this issue. https://github.com/Automattic/jetpack/pull/29681
Hey folks. Sincere apologies for the slow turnaround here. I am able to reproduce the problem here, but I’m at a bit of a loss on how to resolve it. I’m reaching out to some friends here to try and find someone who knows more than I do.
In the meantime, it appears you need to temporarily disable Jetpack to add in a Better Click To Tweet block on a page or post.
I’ll update here as I learn more.Forum: Plugins
In reply to: [Donation Form Block for Stripe] Plugin opens you up to fraud on StripeHey @cadfile
Just wanted to give you a heads up that the version of the Donation Form Block For Stripe plugin released last night adds in reCAPTCHA support.
Have a great day!Hey @isolaj02
Following up here. We want to make sure you’re all set.
Let us know if we can help in any way.
Hi @hardiksaspaceo232
This is an issue that we’ve uncovered with certain hosts not supporting the INTL extension for PHP.
The fastest way to resolve it is for your host to enable that PHP extension, which will make the error message go away.
We’re considering doing something from our side to fix it, based on the number of reports. We’re tracking those here: https://feedback.givewp.com/bug-reports/p/php-intl-extension-should-not-break-givewp
The pinned comments there explain much more in detail what’s going wrong, but for now your best bet is to reach out to your host to have them enable INTL. If they can’t, you should find a better web host.Hi @earthnewspaper!
Very glad you reached out. This is a problem caused by your server not having the INTL library (which is an extension for PHP) installed and active by default. You should reach out to your web host and have them install that library. For the handful of users we’ve seen report this, their host was able to install that extension no problem.
For more on that, see the public feedback here: https://feedback.givewp.com/bug-reports/p/php-intl-extension-should-not-break-givewp
Hi there!
Yes, we released a patch yesterday for that vulnerability, and wrote more about that here: https://givewp.com/core-2-24-0-vulnerability-patched
Update to 2.24.0, and you should be all set!
There’s no indication that this vulnerability is being exploited in the wild, so updating to 2.24.0 should resolve things.That is certainly not what we want! I am more than willing to hop in and see how I can replicate that problem, and see about a fix. Is simply activating jetpack alongside my plug in and viewing a page sufficient to replicate the problem? Do I have to have any specific blocks or other content on a page in order to see the error?
Let me know as soon as possible, and I’ll have a look. In the meantime I will be trying to replicate the issue on a test site, but so far I’ve not had any luck with that.
Hi @johnteh !
WordPress itself is not fully compatible with PHP 8.2, currently. See this page: https://make.ww.wp.xz.cn/core/handbook/references/php-compatibility-and-wordpress-versions/ (it’s marked as “beta”)
GiveWP is compatible with 8.0 (there may be a few PHP notices in the logs for some of our premium add-ons currently, but they are functional), mildly tested on 8.1, and almost completely untested on 8.2
I’d recommend 8.0 today.One thing, you mention it working in some cases, and being logged in. Make sure that “Registration and Login fields” are set to display. On the back end of the form, enable that:
That may fix it.
Hi there!
We’re very happy to help, but from the amount of information given, I’m not able to really give you much actionable. I see that the Form is not loading, and I see lots of errors in the developers console that are 400 errors, as well as a more serious looking error from https://api.trstplse.com/ which is optinmonster-related.
I would deactivate any non-critical functionality on the site, and also deactivate any caching you’ve got running.Also, please send along your System Info.
Navigate to Donations –> Tools –> System Info (tab) and click the button to “Get System Report” and copy/paste that in your reply here.
That will give me some more context to be able to help.
We’re not allowed by forum rules to support premium add-ons here, and the Square gateway is a premium add-on.
Definitely reach out via priority support at https://givewp.com/priority-support and we’ll have a look.
In a brief check I see some errors int he developer console that point to the Square JS not loading because of a display policy of “sameorigin” which sometimes points to a security plugin or some configurations at your host. Also, make sure that all traffic is pointing over https, to rule that out.
Reach out via priority support, and we’ll get it taken care of for sure (note our reply times are a bit slow for the holidays)