Forum Replies Created

Viewing 15 replies - 1 through 15 (of 27 total)
  • Thread Starter jpm2f

    (@jpm2f)

    Hi Jonas

    Good to hear from you.

    1. “button” styling … Oh, OK … thanks for that. I have looked but was unable to find any settings that affected the button. May be the theme we are using, which we are contemplating changing. Currently Twenty-Twenty Four. We are looking for something better.
    2. Unfortunately, cannot send you a link because, since writing to you, we have had to deactivate WooCommerce in order to try to solve a major problem. WooCommerce is blaming all the plugins we have tried, including yours, for the fact that we seem unable to add more than one donation form to a single page. If, for example three donation projects are added, having added them as “products” in Woo, only the first one is visible, the others are shown as “Only one donation form per page allowed”. This is a major limitation and may mean we are forced to abandon Woo altogether.
    3. “does not yet support redirecting to the cart page” – that is a big limitation for us at the moment, however I am sure you can overcome that.

    Your plugin is excellent and frankly, if Woo would get their act together, it would be an ideal solution for us and many other charities. It is WooCommerce we have major concerns with. If they fix the issue of multiple donations, then we can use them and your solution. If not we will be forced to find another platform or a work around, which we are not sure how to achieve.

    Speak again soon.

    Thread Starter jpm2f

    (@jpm2f)

    Thank you for your eply.

    1. you’re having them as a donation product through a third party plugin” … No. The products are added in WooCommerce as regular products. The plugin is only to permit donors to enter their own contribution amount – its called Donations for WooCommerce. However, we have attempted the same with other plugins and, upon adding a second or third “product” the Woo Shop page always reverts to the result, “Only one donation form per page allowed” displayed for any product beyond the first one.
    2. Advanced donation – poor and long delays on support, too expensive for what it is supposed to be able to accomplish, donors increasingly object to parts of their donations being used to pay for commercial profit.
    3. My team has asked me to ask you the list of plugins you’ve tried for this, as the limitation seems to be on the plugins side, not WooCommerce side. I’d love to learn more about the plugins you’ve tried already and review such limitations.” … I am not here to service you and do your work for you. The fact remains that the same result occurs with each plugin we have tried. Blaming the plugins for what is clearly a limitation of the WooCommerce platform, is not acceptable. I suggest if you wish to learn more about the plugins, either ask the developer teams or trial them for yourself.

    In the meantime, I would like to know how and when this limitation will be addressed please, and in the meantime how we may be able to circumvent the limitation.

    To recap:

    We need to be able to list multiple projects for donation on a single page. The donations need to be donor-nominated amounts. Each “Donate button”, on each project must sent that contribution to a basket without leaving the multi-donation page. When selection is complete, the donor must be able to review the basket and proceed to a single payment checkout. The first stage of this process, the listing of multiple self-nominating donations, on a single page, is not possible. This is a problem.

    Thank you.

    Thread Starter jpm2f

    (@jpm2f)

    Thank you for your reply.

    1. I see it has already been suggested and dismissed.” … Yes, for obvious user experience reasons. I’d appreciate you not making it sound as if this is a fickle choice by us.
    2. Another option would be to have your donations as products that you can add to the cart.” … This is what we have been doing. Each project is a product. Each product is a donation. Only the first product/donation is displayed, the rest shown up as “Only one donation form per page allowed”, as mentioned above. (and a direct add-to-cart link for each donation is not possible)
    3. GiveWP, like many “to help charities” plugins is far too expensive, exploiting charity’s needs and capitalizing on offering only the most mundane and largely redundant capabilities in their lower priced packages.
    4. The workaround in https://www.wc-donation.com/documentation/advanced/multiple-donation-forms-on-one-page/ does not work. Besides, this plugin is not supported by the developer. We tried for weeks to get any response.
    5. From the Slack forum we were recommended against using https://woocommerce.com/products/advanced-donation/ by another charity. Too expensive anyway.
    6. We have tried the WooCommerce Support several times with requests. Most have been ignored.
    7. Another charity advised us to avoid needing the services of your refund team, as they are not reliable and take too long.

    We are building a charity platform which shows donors where 100% of their donation goes and what the donations are used for. Donors object to watching their contributions being spent to cover the commercial profit of companies, rather than the cause to which they are donating. And, like WooCommerce, most solution providers refuse to provide discounted or free services to support charities or conservation. meaning they become simply too expensive to justify to donors.

    I look forward to perhaps hearing from your developers at some point.

    Thread Starter jpm2f

    (@jpm2f)

    Thank you for your suggestions.

    Firstly, as we both know, submitting a suggestion for an update to WooCommerce will never be given any attention by the developer team. Woo developers have a reputation for not paying any attention to such submissions, and even if they were interested in making the change, it would likely take months, which we do not have.

    Second, creating one donation per page is completely impractical. That would mean 30 donation pages. No visitor is going to waste their time going through multiple page changes just to make a donation to a few projects. Besides which the donation on each page could not be collected to a central page, and then to a basket, as this would be a mess and terrible user experience. Not to mention is not something that the payment gateway at checkout would support.

    Why are WooCommerce passing the blame on what should be a simple fix for them. Is it the case that WooCommerce are not interested in nonprofits as clients, and therefore have no interest in their requirements?

    Whatever the reason, I would appreciate an explanation as to exactly why WooCommerce will only allow one donation form per page please.

    The reason must be substantial, given that on the face of it this restriction is ridiculous.

    Thread Starter jpm2f

    (@jpm2f)

    We want donors to choose their own donation amount and be able to choose more than one project to donate to.

    To do this we have tried several plugins.

    They all have the same problem when adding the short codes to the WC shop – only the first short code will generate a usable donation. The remainder always show up on the page preview as “Only one donation form per page allowed”. This happens with several plugins. We have contacted the developers of these plugins and they all say the same thing – it is a restriction of WC and they cannot help us.

    I do not understand why it is not possible to have a single page, containing multiple project donation forms, and for a visitor to simply enter their amount into projects they wish to support, for those donations to end up in a single basket and from there a single checkout.

    Thread Starter jpm2f

    (@jpm2f)

    Hi @jordesign – problem solved.

    The solution – signing into the domain URL WordPress site, not the AWS Lightsail location, after using Bitnami to edit the site domain and WordPress URLs away from the default IP location to the domain URL.

    Images loaded from there work perfectly. Thank you for your guidance.

    Thread Starter jpm2f

    (@jpm2f)

    Thanks for explaining @jordesign … am I correct in thinking this is largely to do with our AWS LightSail hosting? (… as https://3.75.63.24/ is the URL in LightSail)

    Could you suggest a solution to overcome/solve this problem please? (especially as it seems to be both a header and footer image issue)

    Thank you.

    Thread Starter jpm2f

    (@jpm2f)

    Hi @jordesign … to clarify

    … the image needed is a wave effect …

    Here https://3.75.63.24/ is what I see when I make the change to the footer, update, and view the page in preview … however …

    Here https://5wf.org/, is what that same page looks like on the actual domain – the wave image does not show up.

    The current solid colour on the domain page is because if I add no background colour in the footer, the image is simply missing on the domain, meaning the site is not releasable and therefore I cannot leave it like that for you to see the “white” missing image. That you will have to imagine I’m afraid. Sorry.

    I have experimented – trying different images, different format images, and images in the header – all with the same result = any image placed in either the header or the footer will show in the preview once updated, but will not show on the actual domain.

    I have tried with-image-with-background and with-image-without-background.

    The result is that without a background, the image does not show in the header or the footer and therefore a background colour is necessary.

    I hope this helps clarify.

    Thread Starter jpm2f

    (@jpm2f)

    Hello @jordesign … Thank you for your reply.

    The “correct” footer image in the editor test view looks like this … https://3.75.63.24/ … however on the domain no image show at all and it is entirely white, as per the background.

    I have therefore had to temporarily adding a straight background which looks like this … https://5wf.org/

    This issue also occurs when using a background image in the header.

    Any advice would be appreciated.

    Thread Starter jpm2f

    (@jpm2f)

    @richardmallick … Amendment to above – have publicly posted the https://3.75.63.24/?page_id=84 page … https://5wf.org/?page_id=84 … which now shows the Private publish/ Public Publish difference with the missing image.

    Many thanks

    Thread Starter jpm2f

    (@jpm2f)

    Hello there.

    Can anyone assist please?

    Thank you.

    Thread Starter jpm2f

    (@jpm2f)

    Hello Richard.

    Thank you for your reply.

    I am unable to share the public site URL with the error showing, as this is a working charity site on which we cannot have errors. Here however is a duplicate test page is here.

    https://3.75.63.24/?page_id=84

    Top … the image we are trying to add the hover action to …

    Bottom … the result of adding the exact same image to the hover effect – which works on the preview page but not when published on the public site. https://5wf.org/

    When we publish on the proper URL the image disappears and is replaced by four corner making line, yet with the hover still working.

    Any advice would be appreciated please. Thank you.

    Thread Starter jpm2f

    (@jpm2f)

    @edo888

    Thank you for getting back to us.

    One quick question however. If there is nothing wrong, how is it that we have complaints from visitors/contractors/conservation projects that the three language links on the main top menu do not actually change the language of the page?

    If the menu options are working for you and the pages are translating, please explain why this is not the case for either us or the supporters who have complained to us the translation is not taking place.

    Step by step instructions are not needed. The links are there for all to see and their placement was made over a year ago, with all working perfectly fine until recently.

    We would appreciate it if you did not go down the path of attempting to infer that we have somehow altered, adjusted, added or deleted something. We have not altered anything and therefore the only reason which feasibly makes sense as to why your plugin appears to have failed, for so many people, is perhaps an incompatibility or adjustment made during your last plugin update.

    In any case, we would request that this be addressed please, as, without translation, the loss of translation function potentially looses us donations to our wildlife conservation nonprofit. Something I am sure you would be keen to avoid.

    Many thanks.

    Thread Starter jpm2f

    (@jpm2f)

    I don’t think anyone is available or interested in providing support.
    Have just been dismissed and ignored by the Chat agent “Suzan”. Incredibly rude.

    FYI
    @edo888

    Thread Starter jpm2f

    (@jpm2f)

    Hi there.

    Thank you for responding. One small problem however, which you seem to have overlooked … Once updated, it is not possible to re-update.

    Are you saying the only solution is for me to uninstall/delete your plugin and then reinstall it? You are aware this will mean I lose all of my settings, blocks, lists, IPs etc?

    Would appreciate knowing because we did not touch the installation, as you appear to be inferring, and we, reading in the forum, are not the only user to have experienced this failure. This is a MAJOR inconvenience and liability to security you have caused here.

    Thank you.

Viewing 15 replies - 1 through 15 (of 27 total)