Forum Replies Created

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

    (@dashedslug)

    Hello,

    If the money appears in your hot wallet balance (not cold storage) then it’s not lost. The plugin simply wasn’t notified of the deposit.

    1. Have you had successful deposits before or is this a new site? Have you tested deposits before production?

    2. Please go through the how-to guide to determine the source of the problem. https://www.dashed-slug.net/howto-debug-an-incoming-deposit-coinpayments-adapter/

    Let me know what you found on each step and whether this is the first deposit or whether there have been successful deposits using this adapter in the past.

    with regards,
    Alex

    Plugin Author dashed-slug.net

    (@dashedslug)

    Are you saying that you installed the plugin, and clicked on “Wallets” and immediately saw this error? This is very unusual. Additionally, even if that’s the case, the capability should be restored soon after to all admins.

    In any case, you can force your admin user to have the manage_wallets capability in some other way.

    A good plugin for this is User Role Editor. First, go to SettingsUser Role Editor, and set “Show Administrator role at User Role Editor”. Then, go to UsersUser Role Editor, select the Administrator role, click on Add Capability, and add the manage_wallets capability.

    Alternatively, if you’re using wp-cli you can simply do a wp user add-cap admin manage_wallets.

    Hope this helps.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    First of all, to see why you should’t be editing the plugin’s code, please read the FAQ under “I want to do changes to the plugin’s code.”

    I will give first a long explanation on how to approach this, and then also a complete solution.

    You cannot set the value attribute directly, because the form’s input fields are bound to knockout.js “observables”. “Observables” are simply variables that are part of the viewmodel.

    This particular observable is moveUser and is found here: https://github.com/dashed-slug/wallets/blob/4.4.8/assets/scripts/wallets-ko.js#L353

    You can set the observable like so: wp.wallets.viewModels.wallets.moveUser('admin');.

    To do this, you would first need to wait for the wallet’s front-end to load. When the front-end loads, it fires a wallets_ready bubbling event that you can catch at the root of the DOM, like so:

    jQuery( 'html' ).on( 'wallets_ready', function( event, coins, nonces ) {
    	wp.wallets.viewModels.wallets.moveUser('admin');
    }

    The trick is to add this in your child theme, so that even if all the plugins and your theme get updated, your code doesn’t get wiped out. One quick way to do this is to add the following to your child theme’s functions.php file:

    function set_move_recipient() {
    	?>
    	<script>
    		jQuery( function() {
    			jQuery( 'html' ).on( 'wallets_ready', function( event, coins, nonces ) {
    				wp.wallets.viewModels.wallets.moveUser('admin');
    			} );
    		} );
    	</script>
    	<?php
    }
    add_action( 'wp_head', 'set_move_recipient' );

    Hopefully your theme knows about the wp_head action, as some low-quality themes don’t use it. If that’s the case, add the JavaScript code into your site some other way.

    Hope this helps. Let me know if you need any help implementing this into your theme.

    with regards,
    Alex

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    What exactly did you click before this happened?

    Some times when you are editing role capabilities (WalletsCapabilities), the admin user can lose the manage_wallets capability. This capability is required to display the Wallets menu.

    I am not sure exactly under what circumstances this can happen, but in any case there is a fail-safe mechanism that will restore the capability to administrators on the next cron tick: https://github.com/dashed-slug/wallets/blob/4.4.8/includes/caps.php#L252-L283

    Please let me know exactly what you clicked right before the error appeared, so I can investigate.

    with regards,
    Alex

    Plugin Author dashed-slug.net

    (@dashedslug)

    Go to the Wallets β†’ Capabilities admin screen, and assign has_wallets to the administrator role, and to other user roles, such as subscriber, editor, etc. Then hit the “Save changes” button.

    Alternatively, or if this doesn’t work, you can use any other plugin that edits WordPress capabilities. There are several out there.

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    The deposit shortcode requires the has_wallets capability. For some reason it seems this capability is not assigned to the admin user (user 1). Normally the plugin assigns this capability automatically. In any case, capabilities can be controlled at the Role level in the WalletsCapabilities admin screen, or with any other plugin that edits WordPress capabilities.

    All shortcodes require the has_wallets capability. Other shortcodes require additional capabilities. For example, [wallets_withdraw] requires has_wallets and withdraw_funds_from_wallet. The bundle download of the plugin (from the website) comes with an accompanying PDF manual that details all the available capabilities.

    Please let me know if this helped or not.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    Thank you for the additional info.

    Can you please be more clear? Which plugin did you identify? What problem was it causing? Was the problem resolved after you deleted it?

    Also, can you please reply to points 2 and 4?

    Alternatively, if you give me access I can try to diagnose the issue myself.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    1. You say you’ve cleared the cache. I assume you’ve cleared the server-side cache, not the browser cache.

    2. In what screen are you getting “Updating failed. Error message: The response is not a valid JSON response”? What are you doing to get the error message?

    3. Can you try deactivating all other plugins? Do you still get the error? Do you still get the error after switching to another theme?

    4. IF you have enabled debugging, then also set the constant define( 'WP_DEBUG_DISPLAY', false ); otherwise errors and warnings can creep into the JSON API responses, making them invalid JSON.

    5. If all else fails I can login to diagnose the issue. You can contact me here about this if you wish.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    @oliverskillz Thank you for opening a new thread, as your issue may not be relevant to this thread. I have replied to you here: https://ww.wp.xz.cn/support/topic/no-currency-enabled/#post-12278671

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    Please check all of the following:

    1. Go to Wallets -> Adapters. There should be at least one coin adapter with status “Responding”.

    2. Check for any JavaScript errors in your browser’s console. If there are any errors (not warnings), these can interfere with the frontend knockout.js templates and thus prevent the views from rendering. Fix any errors and disable plugins that have JavaScript errors.

    3. It is possible that one of your server-side caches has retained a stale copy of the HTML or JSON API. Try clearing your server-side cache, if any. If this is the root of the problem, the cache can be configured to work with the plugin. Please let me know which cache was causing the issue and I’ll be able to help.

    4. Disable any HTML minifiers/optimizers. These are known to cause this issue. The plugin relies on HTML comments which many optimizers are stripping away.

    Please let me know if the problem is resolved by one of these things or not.

    with regards
    Alex

    Plugin Author dashed-slug.net

    (@dashedslug)

    The latest version 4.4.8 includes a fix for @superpwa compatibility, based on the above discussion.

    Plugin Author dashed-slug.net

    (@dashedslug)

    After some digging, it turns out that the filter works, as long as you call superpwa_generate_sw(); once, right after providing the filter in functions.php. The call does not need to be called every time, only once and then the generated js code works.

    Even the code that does caching is cached πŸ™‚

    I will be including a fix in the next release of wallets.

    Plugin Author dashed-slug.net

    (@dashedslug)

    Normally I should be the one who summarised the findings here, but again thanks for taking the time to do so!

    While you may have found a temporary workaround, I will continue to investigate this to find a more permanent solution.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    Unfortunately there is no support for ERC-20 at this time.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Thank you.

    I have logged in to your site.

    You have developed your own knockout.js views, and these have errors which prevent them from working as expected.

    I will contact you over email about this, to discuss how the ko bindings can be improved.

    with regards,
    Alex

Viewing 15 replies - 106 through 120 (of 492 total)