Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.
Backend adds the subscription to the user directly. There is no payment process in backend (so it has no idea if it should use Offline, or PayPal for example). So there's no reason for it to go through payment process.This is something that seems like it should be a high priority given that it's an advertised feature.
The integration should work the same in backend as they do backend. Set your query to fire on first activation for example. Pending actions will not work on backend as there is no Pending state as the subscription becomes active immediately.Additionally, we've written a SQL statement using the CB SQL Statement integration plugin. This statement does not run when a user is activated via the front-end method. So in addition to the method being convoluted, it also does not trigger the appropriate functions as it does when a user self-activates.
This could be a bug. You're saying when going through Offline process on frontend on a users behalf does not add an invoice to the invoice page? Even after paying the Offline invoice?Additional problem: User invoices are not generated when a front-end administrative activation is processed. So even work-arounds that we have in place do not work correctly using the front-end administrative activation on plans.
Please Log in to join the conversation.