Forum Replies Created

Viewing 15 replies - 121 through 135 (of 492 total)
  • Plugin Author dashed-slug.net

    (@dashedslug)

    Hello Gisele,

    Here’s a few things:

    1. Are there any JavaScript errors in your browser’s console? If an error occurs, not right after page load, but shortly after, this would explain the behavior you see. The knockout library doesn’t like JS errors.

    2. A long shot, but are you minifying your HTML markup? This can cause issues, because the plugin is using some knockout directives that are embedded in HTML comments.

    3. If you like, you could give me access, so I can login and debug this. I do not believe that admin access is required, a normal user account with the has_wallets capability should do. If you want me to do this, please contact me over email with credentials.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Thank you, I appreciate it 🙂

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    For reference, you would normally get this message if the current user does not have enough balance to pay for the cart.

    If the product prices are denominated in a fiat currency, you might also get this message if you have not set up any exchange rate providers, so the plugin does not know how much your coins are worth in fiat.

    Glad you resolved the issue

    with regards,
    Alex

    P.S. In the future, please try to open a new thread for each distinct issue. This helps people who later read these posts. Thank you.

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    This message comes from WooCommerce: https://github.com/woocommerce/woocommerce/blob/master/templates/checkout/payment.php#L33

    It usually indicates that the shipping methods have not been configured for the delivery address you entered. For more information see this post:

    http://sangkrit.net/fix-woocommerce-invalid-shippingpayment-method-error/

    So please check your shipping methods/zones and let me know again if this doesn’t solve your issue.

    with regards,
    Alex

    P.S. This is the support forum for the main plugin. The support forum for the WooCommerce payment gateway is over at https://www.dashed-slug.net/forums/forum/woocommerce-cryptocurrency-payment-gateway-extension-support/

    Plugin Author dashed-slug.net

    (@dashedslug)

    @maxwellolowo Hello, you mentioned two issues:

    1. This is because you copied the double quotes from here, where the straight double quotes have been replaced with curly double quotes. Instead, type the double quotes yourself or copy from here: ".

    2. If you are using the CoinPayments adapter, this is likely due to a missing permission on the API key. Add the get_callback_address permission if you haven’t already. Alternatively, check your JS console for any errors.

    In any case, this thread is old. Please open a new thread on the forum if you continue to encounter problems or if you have any further questions.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    Glad you found it. For reference, the documentation is here: https://wallets-phpdoc.dashed-slug.net/classes/Dashed_Slug_Wallets_PHP_API.html#method_api_deposit_address_filter

    Note that the force_new argument will give you a brand new address and it will assign that address to that user and it will also mark all the other addresses for that user and coin as “old”.

    If you simply wish to get the deposit address, do not include force_new in your call.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hi again,

    I logged in to your site and investigated. You do not have any JavaScript errors.

    The frontend for this plugin relies on knockout.js, a framework that allows JavaScript directives to be placed inside HTML comments. You are running some plugin that strips these comments out to reduce page size. Many optimization plugins or caching plugins do this as an extra feature.

    The problem will be resolved once you allow HTML comments in the website output, because the plugin relies on them to work properly. You should be able to switch off this option in whatever plugin does this. (See also “After minifying the HTML output of my webpage, the UI no longer works” in the troubleshooting section of the documentation.)

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    What does the following URL show:

    This is most likely due to JavaScript errors in your console, so check for these first. The dynamic UIs in the frontend rely heavily on JavaScript (the static ones less so).

    If you have checked and there are no errors and you still get this issue, please let me know. I will also be able to login to your site if you wish to check for myself.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    Thanks for reporting. I have never been able to reproduce this issue but I’ve heard others who had it.

    I have prepared a patch where the plugin’s cron job will check if there are admin users with the manage_wallets capability, and if not, it will re-assign the capability to the *Administrator* role.

    Because of this new safety precaution it will again be possible to edit capabilities of the Administrator role.

    In the meantime, you do not have to reinstall the plugin. Simply use any capabilities-editing plugin to restore the manage_wallets cap to your user. Again, this will not be necessary after today’s release.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    Most likely there is some restriction placed by your hosting provider on what you can do on the database.

    Did you attempt steps 1-3 from my post above?

    If your host is using cPanel, go to Databases -> phpMyAdmin. Instructions from your host are here. Then, go to the SQL tab to find the SQL console. What happens when you enter the create command?

    Any errors will also be in your mysql.log. Your host will be able to tell you how to access the log. Usually it is in /var/lib/mysql/{SERVER_NAME}.err where {SERVER_NAME} is the name of your server. Your host may be able to tell you how to view this from cPanel.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    Either the plugin will create all the tables successfully on activation, or there will be errors in mysql.log. Did you drop the table and then attempt to deactivate/reactivate?

    If you like I can also log to your site and attempt to diagnose the problem. If you want me to do this please contact me by email.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    If I understand correctly, once you entered the CREATE TABLE command you got an error. This could be because you copied the code in such a way that the quotes were mangled.

    If you saw this issue after somehow migrating your site using some migration tool, then deactivate the plugin and activate it again. (The plugin normally creates all the tables and indices required on the DB, when it is activated. It’s possible that the import/export tool you used only copied the standard WP tables and not any custom ones. Or if you performed a full SQL dump it’s possible that the table was not migrated due to incompatible collations or character sets.)

    In any case, I asked you to run the CREATE TABLE query manually to see if it was somehow incompatible with your version of MySQL. You entered the CREATE TABLE command in your SQL console, and you got a syntax error. It is possible that the quotes were mangled during copy-paste. Can you try again with the raw version of this pastebin? https://pastebin.com/raw/GKyKVwdD I have double checked that the syntax is correct, so if you get any errors here, please let me know again.

    Any subsequent errors that you see are normal. The plugin requires two tables plus some indices to work correctly. The query I gave you will not fix the error, it’s only so we can understand what went wrong.

    Ultimately one of two things must be true: Either
    a. the plugin will create the tables successfully, or
    b. there will be an error in your mysql.log file, corresponding to the time when you activated the plugin.


    In conclusion:
    1. Try deactivating/activating the plugin again.
    2. Please check again to see if the CREATE query actually created the table in your DB.
    3. Let me know if you see any error in your SQL console, immediately after entering the CREATE query correctly from the raw pastebin (i.e. NOT errors in WordPress).
    4. If you find any errors in your mysql.log file around the time you activated the plugin, please share them with me.

    Thank you.

    with regards,
    Alex

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    Judging by your DB prefix, it looks like you may be on a shared hosting platform. It’s possible, although unlikely, that they don’t allow new tables to be created; you can check with them to see if you have CREATE TABLE rights.

    If you have access to your MySQL logs, the error will be apparent there.

    Alternatively you can go to your MySQL console or phpMyAdmin SQL console, and paste the following code: https://pastebin.com/GKyKVwdD

    This will either create the transactions table with your prefix, or it will give you an error. Let me know what happens when you try this, and we’ll proceed from there.

    with regards,
    Alex

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    Are you using the CoinPayments adapter? Did you follow the video? Please check the pinned message below the video, i.e. check that your CoinPayments API key has the get_callback_address permission. Once you do this, deactivate the plugin for two minutes and then activate it and try again.

    Please let me know how it goes.

    with regards
    Alex

    Plugin Author dashed-slug.net

    (@dashedslug)

    This address is in BIP-21 format, which allows it to be unambiguously placed in a QR code.

Viewing 15 replies - 121 through 135 (of 492 total)