capynet / drupalpaypalrecurrringpayment Goto Github PK

The basics are:

• Manage plans (for the managers. alloe ABM plans)
• Allow subscription (for the field. only prints if the rol has the perm)

I mean this kind of link:

We dont want a user gets a charge next year if it deleted it's account.

The task of the main module is allow visitors subscribe to a paypal plan but what to do when the job is done should be tacked by contrib modules (or submodules in this case)

• The module needs to be able to be added as dependency on a project via composer require drupal/OURMODULE
• The module itself needs a composer.json with "paypal/rest-api-sdk-php" as dependency.

And this is a problem since I can install a new drupal with bar.com and if a plan been created at foo.com and I want use it at bar.com, the ok and ko URLs will be pointing to foo.com.

We need to check if the available plans should be filtered by site (from the drupal side) or if the plans (any plan) can be used on any site changing the URLs on the fly.

Im not sure about the best implementation for this. As a extra field for the user entity maybe?

Must print:

• Agreement name
• Payment cycle date.
• Amount
• Cancel button.

Use case: The user approves or cancel the agreement at paypal. Paypal will return the response to static process urls BUT we need to decide what to do after the processing.

We need to add to the config area (/admin/config/system/paypal-sdk) the possibility to redirect a user to an url and optionally show a message.

You will not see any error or warning. Just edit the plan and try to save it. Will see the changes get not applied:

I tried on unactive plans too and I cant change the title (for example)

Add a field multivalued and add 2 or more plans to a content. Chack if 2 or more links gets printed.

If you still did not setted up the credentials and try to enter to admin/store/billing-plan/list will get a PHP error.

We need to check if the user entered the credentials and if not, show a message indicating the need to setup them.

Falta una pantalla en al cual se pueda poner la api key y el secret. Ahora mismo los tengo hardcoded en paypal_sdk.services.yml

A README.md is needed with information about how use the module. We also should update README.txt file.

Whe the user accepts the agreement we are processing the response at PaypalSDKController->processResponse()

We create a new account for the user if it does not exist or use an existing accound (we search it via the paypal's email matching).

BUT we are not persisting the agreement to use it at the user profile. Thats what we need to implement here.

Depends on #5. When #5 gets completed we need to modify paypal_sdk.services.yml -> paypal.billing.agreement to allow it read the credentials from the sys conf instead the yml file.

To allow select between test and live.

And implement this code

   $this->apiContext->setConfig(
        array(
          'mode' => 'live',
        )
      );

Prior this capture I had an older subscription in that place and I thought the new statos was going to be a table with tow subscriptions.

At paypal We can see both subscriptions

Te plan changes and:

User cases:

• The user is subscribed. What happend. His plan gets updated or supended (see paypal documentation)
• The user is have a suspended subscription. What happend. His plan gets will be updated when it gets enabled or he/she must subscribe to a new plan? (see paypal documentation)

The url comes from BillingAgreement->getUserAgreementLink() and we should cache the api call since the link is always the sam (at plan level. If the plan is another one the link is different).

I didn't checked out but just want to be sure the admin user cant delete the default created agreement field.

For:

• Anonymous but really existent user.
• Anonymous but non existent user.
• Logged in user.

And both 3 cases but with existing subscriptions (can be of the same plan or a different plan).

Review the form logic. for example If you select infinite "Plan type" then "Payment cycles" should not be shown as an option.