Forum Replies Created

Viewing 15 replies - 1 through 15 (of 29 total)
  • Plugin Contributor t4top

    (@t4top)

    Hi @scandidesignco,

    Thanks for your feedback and feature request. The QR code is a standard Solana Pay URL, and according to the Solana Pay spec, how it’s handled after scanning is up to the wallet app. Unfortunately, we have no way to trigger a “no valid wallet” message from our side. What we can do is add a note next to the QR code clarifying that it only works with wallets that support Solana Pay.

    In addition, we’re planning to provide a generic QR code that presents a deposit wallet address in an upcoming release, which should help cover wallets like Cake Wallet that hold SOL but don’t actually support Solana Pay.

    Thanks again.

    Plugin Contributor t4top

    (@t4top)

    Thanks a lot Mike for your feedback and suggestion. We’re glad to hear that the issue has been resolved.

    Plugin Contributor t4top

    (@t4top)

    Hi @mike0612,

    Thanks for reaching out. Unfortunately, we were unable to reproduce the reported issue. We recommend upgrading to the latest version of the plugin and trying again. If the issue persists, please provide a link to your WooCommerce store for our further investigation via the link below. Thank you.

    https://docs.google.com/forms/d/e/1FAIpQLSdle6xaiO0s8BxYpfE6m_nxylHl6VPLtbgsNmW195CO1EjHWw/viewform

    Plugin Contributor t4top

    (@t4top)

    Thanks for your kind words and detailed review. We’re really glad you like the plugin.

    Plugin Contributor t4top

    (@t4top)

    Thanks for your question. Our plugin supports all major Solana wallets, including Exodus Wallet. Below is a link to the list of compatible wallets:

    https://solana.com/solana-wallets

    Since we use the Solana Wallet Adapter library under the hood, all wallets that support Wallet Standard are compatible and are auto-detected. Please feel free to try any wallet that supports signing Solana transactions. If you encounter any issues, please let us know.

    Plugin Contributor t4top

    (@t4top)

    Thanks for the update and your interest in our plugin.

    The “[Report Only]” message in your screenshot indicates that the browser is only reporting a violation, but not actively blocking the script from executing. This means our plugin is functioning as expected. The violation notice comes from how your WordPress site is configured.

    As shown in screenshot https://drive.google.com/uc?id=131RObxld5n3zKuhx71T2VNicGTIJ7PX2, we were able to successfully complete a purchase on your website using our plugin, which confirms that there is no issue with the plugin itself. However, we did notice a few issues with your site setup, some of which are listed below:

    1) Your site is behind Cloudflare firewall and REST API requests to your site occasionally fail, resulting in blocked connections (see screenshot https://drive.google.com/uc?id=1K1mu9qL94AoA1B5LyfSUMkorZBY9pv3W). This suggests that your Cloudflare configuration may be incorrect or too strict.

    2) It appears you have an optimization plugin enabled that is minifying and lazy-loading script files. We had to ensure all JS scripts were fully loaded before attempting the successful payment. We recommend testing our plugin without any additional optimization, as our scripts are already minified and optimized by default.

    To troubleshoot, try the following:

    • Disable all other plugins and switch to a default WordPress theme.
    • Disable Cloudflare firewall
    • Enable only WooCommerce and our plugin, then test the payment flow.

    You should see that the plugin works correctly. From there, re-enable your other plugins one by one, testing after each activation. This process will help you identify which plugin might be causing the conflict.

    Plugin Contributor t4top

    (@t4top)

    Hi @reservedaily,

    Since we haven’t heard from you in a while, we’ll go ahead and mark this thread as resolved. If you experience any further issues or have additional questions, please feel free to start a new thread. Thanks.

    Plugin Contributor t4top

    (@t4top)

    Hi @payweb,

    Since we haven’t heard from you in a while, we’ll go ahead and mark this thread as resolved. If you experience any further issues or have additional questions, please feel free to start a new thread. Thanks.

    Plugin Contributor t4top

    (@t4top)

    Thank you for your patience. This issue has been resolved with our latest update. We’ve removed the dependency on PHP sessions, and the checkout workflow has been enhanced for improved stability. We encourage you to upgrade and kindly let us know if you encounter any other issues. Thanks.

    Plugin Contributor t4top

    (@t4top)

    Thank you for your patience. This issue has been resolved with our latest update. We encourage you to upgrade and kindly let us know if you encounter any further issues. Thanks.

    Plugin Contributor t4top

    (@t4top)

    We believe the issue is related to caching not working well with the PHP session. We plan to remove the dependency on PHP session in our next major release, scheduled for mid April. We expect this release will resolve the issue. We’ll make sure to keep you updated via a reply to this thread once the release is available. Thanks again for your interest in our plugin.

    Plugin Contributor t4top

    (@t4top)

    The fix is scheduled for our next major release in mid April. We will keep you updated by replying to this thread once it is released. Thanks and apologies for the delayed response.

    Plugin Contributor t4top

    (@t4top)

    Thanks a lot for bringing this issue to our attention. We are currently investigating it and will get back to you soon.

    Plugin Contributor t4top

    (@t4top)

    Thanks for bringing this issue to our attention. The root cause is that the “cart_created” field is empty, which can be seen in the link from your last comment. The default checkout uses the cart hash and creation time to uniquely identify a cart. However, CheckoutWC plugin does not set the cart creation time and appears to use a different internal parameter to identify carts. We have added this issue to our backlog, and it will be addressed in either our next release or the one following it. We’ll make sure to keep you updated via a reply to this thread once it is fixed.

    Plugin Contributor t4top

    (@t4top)

    Thanks for reaching out. From your question, we assume you are referring to Blowfish whitelisting.

    Based on our investigation, you will need to contact Blowfish and request that they whitelist your domain address. You can reach them at [email protected]. Please note that since the Blowfish whitelist operates based on domain addresses, the request must come from the domain owner. Fortunately, our plugin is open source and freely available for the entire WordPress community to download. Please feel free to share the plugin webpage (https://ww.wp.xz.cn/plugins/wc-solana-pay/) with them for their review.

    Please let us know if there’s anything else we can assist you with.

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