Forum Replies Created

Viewing 15 replies - 601 through 615 (of 1,684 total)
  • Plugin Support Matheus Martins

    (@matheusfd)

    Hi, @davidpotter.

    Glad you reached out.

    Please send us an email via https://givewp.com/contact-us/. I’ll customer success team can help you log in!

    Thanks for using GiveWP! Have a great day.

    Plugin Support Matheus Martins

    (@matheusfd)

    We will, @enderbhopal. Thanks for using GiveWP! Have a great day.

    Plugin Support Matheus Martins

    (@matheusfd)

    Glad to hear that you found a workaround, @trashcashph.

    Thanks for using GiveWP! Have a great day.

    Plugin Support Matheus Martins

    (@matheusfd)

    Hi, @infaithly.

    If the error logs are empty on your public_html folder, there are chances your host is saving it somewhere else. In this case, I need you to reach out to your host and ask them for error logs because they will be helpful – even if we do not need at the end.

    Looking forward to helping you get to the bottom of this!

    Plugin Support Matheus Martins

    (@matheusfd)

    Hi, @cherissa.

    Glad you reached out.

    Indeed, the Form Countdown works only for the legacy template. We are happy to consider it if we see more interest from our community.

    Thanks for using GiveWP! Have a great day.

    Plugin Support Matheus Martins

    (@matheusfd)

    Hi, @jamijares.

    Glad you reached out.

    Translation for GiveWP is handled in two different ways: one is for the main plugin and the other for premium add-ons.

    The main GiveWP plugin available on the wordpress.org plugin directory is translated by the (largely volunteer) team at the official translation page for the WordPress project. Here’s the specific page for GiveWP: https://translate.wordpress.org/projects/wp-plugins/give

    We as a company don’t have control over those translation files, though we can make suggestions and contributions there just like anyone else. I’d encourage you to get involved there to make GiveWP translations the best they can be.

    The premium add-ons, because they are not on the official WordPress directory, have to handle translations differently. A handful of our add-ons ship with translation files (PO and MO files) but as most of our team is not multilingual enough to manage translations, we rely on others to provide translations for GiveWP add-ons. The most established way to do that is with a program called Poedit: https://poedit.net/download

    If you want to translate the files just for your site, you can also use a plugin called Loco Translate: https://wordpress.org/plugins/loco-translate/

    We have documentation about how you can do that here https://givewp.com/documentation/resources/translating-give/translating-givewp-with-loco-translate/.

    ​Please let us know if you have further questions or need additional assistance!

    Plugin Support Matheus Martins

    (@matheusfd)

    Hi, @jpschwartz.

    Glad you reached out.

    I’ve seen a similar issue before, but it would happen when you update GiveWP from an older version to a newer one, and it happens because, during the process, database tables need to be created. Some hosts can prevent some tables from being created (sometimes you do not have the correct privileges, for example).

    Can you let me know if this issue happened after an update or if it happen right after you install a fresh GiveWP on your site? And if it happens after an update, I need to know the version you are coming from so we can try to replicate it on our end.

    Your success with online donations is our number one priority. Looking forward to helping you get to the bottom of this!

    Plugin Support Matheus Martins

    (@matheusfd)

    Hi, @fredhowe.

    Thanks for it. The Donor Dashboard translation issue was resolved with the release of GiveWP 2.26.0 (On April) so you should now need custom code anymore. Go ahead and update at your earliest convenience, and let us know if you have any issues moving forward.

    Thanks for using GiveWP! Have a great day.

    Plugin Support Matheus Martins

    (@matheusfd)

    Hi, @litoves.

    It’s been a while since we’ve heard back, and I know troubleshooting needs a little extra time. I’m marking this as resolved for now, but if you still have questions, you can send them along right here, and I’ll be happy to hop back in.

    Have a great day!

    Plugin Support Matheus Martins

    (@matheusfd)

    Hi, @philipg100 & @keegandhue.

    I noticed that you both are using paid plugins. In this case, if you are still facing issues, please reach out to us using our Priority Support form here https://givewp.com/priority-support/.

    I ask you to do this because one of the rules of this forum is that we cannot support paid plugins here. When you submit a new ticket, please add a link to this page so we know we already talked before. I’ll be happy to help both of you there.

    Your success with online donations is our number one priority. Looking forward to helping you get to the bottom of this!

    Plugin Support Matheus Martins

    (@matheusfd)

    Hi, @raccroc.

    Glad you reached out.

    Refunding donors work in two different ways: there are some gateways like Stripe that allow you to refund directly using GiveWP, but there are others that require you to refund directly from the payment gateway.

    ​To cancel and refund a donation on the GiveWP side, you need to navigate to Donations > Donations and click on the donation that you want to refund.Now, on the left side, you’ll change the status to Refunded, and if the payment gateway supports refunding via GiveWP, a new checkbox will show up above the saving button asking if you want to refund the charge in the payment gateway.

    If this checkbox doesn’t show up, then you need to mark it as refunded on GiveWP and then navigate to your payment gateway and refund your donor directly from there. ​ ​

    Something I’d encourage you to do is to double-check when you cancel on GiveWP and check the refund checkbox because if there is some kind of cache on your site, it may not refund on the payment gateway. So, mark it as refunded, check the checkbox and double-check the payment gateway. It will prevent future headaches. ​

    ​Now, let’s focus on preventing spam donations.

    What you are experiencing is what we call “donor spam.” This can happen for a wide variety of reasons, and it is sadly very common across all donation platforms, not just GiveWP.

    Your success with online donations is our number one priority, and spam donations can be a real detriment. We’ve done lots over the years to combat it, but there’s still more to be done. You can follow this post on our feedback site where we are tracking additional spam protection options, and I’ve added your name to the list of folks asking for it. You can see that here: https://feedback.givewp.com/bug-reports/p/additional-spam-donation-protection

    In the meantime, here are some ways that others have combatted donor Spam:

    1) Our Akismet Integration
    Install or activate the free Akismet plugin. Then go to “Donations > Settings > Advanced” and ensure that our Akismet SPAM protection is enabled there and save changes.

    2) Use Cloudflare or Sucuri
    These are third-party services that help both speed up your website and provide protection against bot attacks like what you are experiencing. Some sites get added to bot lists and there’s nothing you can do to prevent them from just continually attacking your site, except using a strong and dedicated firewall/security service like these two. Cloudflare has a paid option, but it also has a free basic plan in case that is a better fit.

    3) Set a higher minimum donation amount
    Sometimes, simply increasing the minimum donation amount is a huge method of preventing these types of attacks. Bots tend to test forms with $1 or up to $5 amounts. If your form only accepts donations of $10 or higher you can prevent these low-hanging easy bots.

    4) Use a spam-stopping plugin
    You can use these plugins: https://wordpress.org/plugins/zero-spam/ and https://wordpress.org/plugins/recaptcha-give/. Zero Spam is a heavy favorite of our team. They offer excellent support and are pros at managing the ins and outs of stopping spam. Both plugins integrate very nicely with GiveWP. Both plugins integrate very nicely with GiveWP.

    Also, one of the things on our roadmap to implement is an optional reCAPTCHA block on the form itself. That won’t happen until after GiveWP 3.0, because the current architecture of the form itself just is not conducive to adding something like that easily. After 3.0 (you can read more about that and sign up to be alerted when 3.0 launches here: https://givewp.com/lps/next-generation-donation-forms/ ) It’s going to be among our top priorities.

    Please let us know if you have further questions on this or need any additional assistance!

    Plugin Support Matheus Martins

    (@matheusfd)

    Hi, @philipg100.

    Glad you reached out. I can help you fix this error. If you have the Form Field Manager add-on installed on your site, here is what happened.

    We released a new version of GiveWP and Form Field Manager that fixes the issue you are facing (GiveWP 2.29.0 and Form Field Manager 2.1.0).

    First, if your site is broken, I would restore a backup of your site so you are up and running again.

    Then, I’d deactivate the Form Field Manager add-on, update GiveWP, update the Form Field Manager add-on, and then activate it again.

    To fix it, you need to update both GiveWP and the Form Field Manager add-on. In this case, you can click on Plugins > Installed Plugins and click to update your plugins. If you do not see an update for it, it’s just the cache. You can navigate to Dashboard > Updates and click on Check Again. It will check for the updates and clear the cache and you’ll be able to update the plugin.

    Before taking any steps for troubleshooting or updating, I highly recommend taking a good backup of the site you can confidently restore from. Having a backup of your site is essential to a solid workflow, and will allow you to restore to a previous version of the site if you run into any issues. You can read more about our top recommendations for taking a backup here: https://givewp.com/backup-for-faster-troubleshooting/

    However, if this is not your case, please send a copy of the error you get when you try to update it and we will help you.

    Your success with online donations is our number one priority. Looking forward to helping you get to the bottom of this!

    Plugin Support Matheus Martins

    (@matheusfd)

    Hi, @flaxtrade.

    ​We’ve investigated it and we found that you’ve uncovered an edge-case issue with the Fields API. What is happening is that we refactored the code to make it compatible with GiveWP 3.0 which is coming, and it will include huge changes. We made sure to make it backward-compatible but from what we saw, we still need to polish it to make sure it works.

    I’ve escalated this to our development team so they can work on a fix. You can follow up on the progress of the fix here https://feedback.givewp.com/bug-reports/p/the-checkbox-field-creation-using-the-fields-api-should-work.

    ​​We are actively tracking user issues to make sure our dev team is aware of them and can get them fixed. You can use the link to check in for updates or to provide additional details of your own.

    Give the post above a look, and let me know if you would like me to add any additional details. I want to ensure your need is as accurately reflected as possible, and I’m happy to include an internal note to our teams with any specific information you would like them to have.

    The only workaround I know of is to stay on GiveWP 2.27.2. I would prefer to update it to the latest version and use our Form Field Manager add-on to create the checkbox field.

    While we work on a fix, feel free to message us if you have further questions or need any additional assistance!

    Plugin Support Matheus Martins

    (@matheusfd)

    Hi, @feedmypeoplecorp.

    It’s been a while since we’ve heard back, and I know troubleshooting needs a little extra time. I’m marking this as resolved for now, but if you still have questions, you can send them along right here, and I’ll be happy to hop back in.

    Have a great day!

    Plugin Support Matheus Martins

    (@matheusfd)

    Hi, @wtnhistwebmaster.

    It’s been a while since we’ve heard back, and I know troubleshooting needs a little extra time. I’m marking this as resolved for now, but if you still have questions, you can send them along right here, and I’ll be happy to hop back in.

    Have a great day!

Viewing 15 replies - 601 through 615 (of 1,684 total)