Rules don't get updated or set to invalid state

@jucallme

Tnx for your guide. There is just one point that I couldn't find :

13. Click profile and select website options (the one with we site in can't rem off top of head now)
14. Add the return address http://yoursite.com/checkout/complete (make sure radio button above is set to on the automatically redirect)

I cannot find the "select website options" .

@jucallme
Question: What about the title of your issue ??

It could better be : How to setup a PayPal Sandbox .

Paul

@latulipeblanche

If you go to "more options", you will find "Website Payment Preferences". From there you can add in the returning web address.

Crystal

There is not a "Website Payment Preferences" option.

These complete instructions would sure be nice in a "README" file within the Module. Could this happen?

@nelslynn, For what I saw in your screen shot you were on the customer test account. This type of account that is not a business account, doesn't have any option to configure "Website Payment Preferences". You must log out from the customer and log in the business test account, there you will find this option. I know that Paypal sandbox is very confusing...

@jucallme nice that when you write a guide and the layout changes :) .... tnx for the guide, worked very well.
Found the "Website Payment Preferences", in the selling preferences list (look at the image).

@devline you are right :"I know that Paypal sandbox is very confusing..." ... it is.

Is it true that PayPal sends a message to confirm the order, and that the order stays "pending" ?
I've been re-directed to the "checkout/complete" page. In the order I see the remote ID (i guess that it's a number from PP), but status "pending"

How does this work with Paypal Sandbox, and later on the production-site (it's my first e-commerce-site)

@latulipeblanche. What you see using the sandbox is exactly the same you will get on production. Yes paypal is sending emails to both the customer and the vendor. You can see how these emails are set by viewing the fake mail boxes you have when you log in the developper sandbox interface. The 'pending' status means that the order has been recieved and paid, but that it has not yet been fulffilled. You have two more status available out of the box (that can be set either by manually editing the order or through some automated process, using rules for an example...) 'Processing' and 'Completed'. These status are shown both in admin orders and in the user account, so then the customer can check the state of his order.

@devline, so when i understand you well, a "pending" order is paid, so ready to be sent to the client.

Does this mean that, in general, an order is set to "completed" when the order is sent ?

PayPal is also sending a message that give you a REMOTE ID, not only a e-mail ?

@latulipeblanche.

#1 : Yes when it's on 'pending' it does mean that you recieved a payment ( kinf of pending to be fulfilled). You may check your order list in admin and review the payment information.

#2 : Yes if you don't have any process that will automatically update the status of the order, it should be better to manually set the status as completed as soon as it is sent, that way a customer going back to his account will be informed that everything is on track.

#3 : The email that the vendor recieves from paypal reports the remote id (id of the transaction in Paypal account) along with a summary of the order that was paid by the customer. This remote id is identical to the id recorded in the payment transaction (in the database) when processing the IPN.

I have used this guide to create the Drupal Commerce user guide page at http://www.drupalcommerce.org/node/305 which hopefully explains the process fully.

This issue has a very odd title. I didn't want to go in and update the title for this myself, as I would be overstepping the boundaries, but can it be renamed?

Reviewing this issue, I think I'm going to have to conclude that there's simply nothing we can do here. This is a drawback of using Rules to store the payment method configuration, and it's something we've already put on the to-do list to change for Commerce 2.x.

The way it's functioning is as designed by Rules, and there's no real way to look at the data in code and determine that the user should go update the payment form settings. One of the reasons is that when we add new settings, we also put the default value in the code, so even if you have an outdated Rule, it won't cause any errors - the module will simply assume that you haven't changed the default value of the new settings. That's really the best we can hope for here, and if settings seriously change from release to release, we can simply indicate that as part of the update process, the configuration should be evaluated and updated as necessary.

rewritten to focus attention back to reason issue was filed. The paypal guide now has a home on drupal.org and can be removed from here to prevent further noise.