RexAK

Sorry for the delay in response. I’ll setup a dev site and see if I can reproduce this issue.

Hi ocm001,

To help troubleshoot, are there any other Payment Gateways in use on your site, and does this happen to all subscriptions, or just some… or just one? Was a particular subscription that fails, originally ordered and setup with a non-CardConnect gateway plugin?

@losting
Would you verify for me that under WooCommerce >> Settings >> Checkout >> CardConnect, that you see no “port” error notifications, in red, at the bottom of the page?

If there are no errors, would you verify your MID, username and password are correct, and that the “Site” field contains “fts” only?

If all of that looks good, and you are on shared hosting, you may need to request that CardConnect ports be opened for communication with the Card Connect servers, even if you see no port errors.

I know its a little late, but you can access the setup and modules from DashBoard >> Tools >> Core Control

Same problem here.

Alright, go ahead and update to the new 1.0.5 release. Let us know if that fixes your issue. When you are on your checkout page, clear the cache, so we get rid of any left over data hanging out in the browser.

If all is good, we’ll set this to resolved.

Hi You2media,

I just need to confirm that this is the theme you are using: https://www.ads-software.com/themes/classic/

Can you send us a link to the site? That would help us troubleshoot, and give you an exact reason.

Same issue here. Have you found a solution? It seems to import correctly, at least with the one file I needed to import.

Late to the party, but your code has helped me a lot, Emily! To get the data I needed, I figured I would need to query the wysija tables in the DB, and it turns out that is correct.

It would be a lot simpler if I could find methods in the plugin like:

get_subscribers($list_id;) or get_lists($user_id); or even get_wysija_lists();

instead of making my own, unless I’m missing something… ??

Nice plugin, either way.

Thanks varktech, found a way and posted it over in that thread!

In my case, I needed to allow a single role into the dashboard.
My role had a custom capability, so I used that as a check:

add_filter('woocommerce_prevent_admin_access', 'allow_role_access_to_admin', 10, 1);
	function allow_role_access_to_admin($prevent_access) {
		if (current_user_can('{your-custom-capability}')) { //stick any check in here
			$prevent_access = false;
		}

		return $prevent_access;
	}

This way, I can still use the Woocommerce feature, but allow access to some roles.

The original way I had it, was:

add_filter('woocommerce_prevent_admin_access', 'allow_access_to_admin', 10, 1);
   function allow_access_to_admin($prevent_access) {
    $prevent_access = false;
    return $prevent_access;
}

Needless to say, Mike’s answer for overriding, is much quicker ??

I need the same answer, let me know if you found a way. Thanks.

Having the same issue. Replacing the plugin with the previous version fixed it for me…hopefully.

I eventually reverted back to the previous version of the plugin. Seems to work now.
Let me know if I can help troubleshoot, or if you think it was a fluke.