lestaticon

Must be related to this bug in WCML: https://wpml.org/forums/topic/latest-update-adds-wcml_converted_total-to-manually-created-order-e-mails/

Hello Hannah,

For sake of replication. Before using this free plugin, we used the paid one this one replaced. When installing this free one, it appeared to pull in all of the settings from the old one. Just a factor to consider when you try to replicate it on your side. Perhaps that element is involved in this anomaly.

Thanks

• This reply was modified 8 years, 2 months ago by lestaticon. Reason: clarification

Hello,

Hannah, it is set to “Authorize.” We capture later after the order is finalized in our physical store for shipping, etc.

Thanks

For one, the payment process on the backend is not good. When your settings indicate authorizing payments in the plugin and someone submits an order, it gets added to your order list as “in process” when it should be “on hold”. When it is “in process”, you cannot edit the cart and update totals, etc. That’s essential.
Also, in the message log of the order, it says that the payment has been processed, when it should be saying that the payment has been authorized.
Also, since it’s status is “processing”, you have to manually change it back to on “hold” in order to edit the totals. Once you do that, the ability to capture the funds is removed from the actions list of the order. The order is locked as if you have already taken the funds.
When I go to paypal, the funds are still in authorization status only and remain that way until I manually capture the funds from paypal.com directly.
So, hopefully you can see how this is not working well.
Also, the popup Paypal Express from the cart has been broken since 1.0.
It has been several weeks since that was reported and confirmed.

All you need to do is get a copy of the old, paid plugin and the differences will be obvious.

I can get over some of the limitations at checkout as described above, but the backend process NEEDS to be fixed before we can use it.

Same error as above in my error log as well.

Hello,

Thanks, that is definitely a workaround we will consider once the other issues are addressed (hoping they are).

** Just noting that this is not critical. We can work around this limitation. Consider as suggestion.

* Though the PE checkout not working from the cart is a critical issue, but I understand it’s fixed in 1.01. Just hope that gets pushed out soon.

** Just noting that this is more of a critical issue, not a suggestion.

Please update with correct link. I noticed the Docs link from the plugins backend in WP also goes to this same broken link.

Thanks

When I switched manually to “On Hold” to be able to generate a shipping label and then update the total with the correct amount (10 cents less for shipping, in this example), it appears to have removed the option to capture the charge from the edit order page for this order.
I don’t think the plugin is handling authorizations well at all.

When the order was first entered in the backend, it came in as “In Process” and in the order notes, it listed this fact and there was an entry saying the paypal transaction completed with the same timestamp. First, it should not say that. It should say that the transaction has been authorized, not completed.

I then manually updated the order status to “on hold” so that I could generate a shipping label and then update the totals.
The order notes added a line stating the change from processing to “on hold”.

After I updated the totals and generated a label, I changed the order status to “processing”
In the order notes, I noticed two new lines with the same time stamp.
One showed the order status changing to “processing”, the other stated that the “PayPal Express Checkout charge complete”, which is not correct. First, it should not have done that, and the fact is that at the paypal site, the transaction still shows as authorized and gives us the choice to capture the charge.
However, on the WP backend, in the edit order screen, I no longer have the option to capture the charge.
Something is not working right here.

Thanks