Source evidence

Unknown customer ref

WP-Chargify · support · 2015-10-29T20:17:00+00:00

WP-Chargify plugin evidence original source source API

complaintsentiment

highseverity

1.0relevance

3replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

4 / 23 rows with source links

17.4% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

19 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support

olliekav unresolved

I’m really struggling to get this plugin to work 100%. Sometimes WordPress accounts are created, most of the time though I get ‘unknown customer ref’ yet it actions a subscription on Chargify which surely should’t happen as I now a customer has paid but they have no account on WordPress? All my settings are correct and I can connect to the API from within WordPress. I’m thinking maybe it is to do with using a test account on my development environment but I’m really hesitant to put this into any sort of production environment with bugs like this. Has anyone else encountered this? Also is there any way to block full posts and pages rather than just the content? Or a function I can use in my template to wrap full blocks? https://wordpress.org/plugins/chargify/ More issues I’ve come up against: If I cancel a subscription within Chargify or it runs out, the content gets blocked but when I try and re-subscribe it says ‘You already have access to this level’, even though no subscription exists. Even If I delete the user within Chargify it still won’t let me re-subscribe. I can create multiple subscriptions under one email address, which seems odd. Surely it should block you signing up for multiple? WordPress emails are never sent out to new users. I’m having the same issue with the ‘unknown customer ref’ in my test environment. Did you come up with a solution or fix? I gave up with this plugin as I can’t get any support on the bugs and it doesn’t feel anywhere near solid enough for a production environment (especially with payments involved). I’ve moved the client over to Restrict Content Pro.

Commercial Context

Opportunity

access control and account operations

Registration access-control assurance for keeping user access, permissions, and protected content correct

Buyer: membership site owners, agencies, and operations teams

Wedge: test registration roles, protected content, SSO/login handoffs, and private-data exposure

Proof Blocked card complete market

Analysis

heuristic-v1

Summary: Unknown customer ref: users show bugs, missing feature, pricing pain that may indicate a product gap.

Evidence quote: Sometimes WordPress accounts are created, most of the time though I get ‘unknown customer ref’ yet it actions a subscription on Chargify which surely should’t happen as I now a customer has paid but they have no account on WordPress?

Affected feature: payment

bugs missing feature pricing support

Plugin

API

WP-Chargify

10 active installs · 5.4K downloads · rating 76.0

chargify membership registration subscription tools

Comments

3 shown

olliekav 2015-10-29T21:11:00+00:00

More issues I’ve come up against: If I cancel a subscription within Chargify or it runs out, the content gets blocked but when I try and re-subscribe it says ‘You already have access to this level’, even though no subscription exists. Even If I delete the user within Chargify it still won’t let me re-subscribe. I can create multiple subscriptions under one email address, which seems odd. Surely it should block you signing up for multiple? WordPress emails are never sent out to new users.

John 2015-12-04T14:39:00+00:00

I’m having the same issue with the ‘unknown customer ref’ in my test environment. Did you come up with a solution or fix?

olliekav 2015-12-04T14:59:00+00:00

I gave up with this plugin as I can’t get any support on the bugs and it doesn’t feel anywhere near solid enough for a production environment (especially with payments involved). I’ve moved the client over to Restrict Content Pro.