Square WebPay support thread.

Quote:

---

Originally Posted by dbltoe

Those of you who were already using Square prior to carlwhat's update to WebPay may want to check your ADMIN >> Customers >> Orders for orders made in late March or earlier that have square under the Payment/Shipping header versus square_webPay.

We (myzencarthostDOTcom) updated several of our customers while some did 1.0.0 and 1.0.1 on their own. Both groups have shown cases where the Payment/Shipping was not changed to square_webPay on orders made with the old square.

If you are using WebPay and the Payment/Shipping shows square, you will not be able to access the full details for the order. IOW, you will not see anything AFTER the payment method. A partial blank screen with no log created and no way to see comments on the order.

NOTE: Some sites with Edit Orders are able to access the data with that mod. Still, the fix needs to be made.

Somehow, the upgrades did not modify the orders table in the database for any existing square orders. Specifically, the payment_module_code field. Some sites had a DB prefix and others did not so, I don't think that's the problem.

There's a quick fix if you find this happening. Go to ADMIN >> Tools >> Install SQL Patcches (it shows up as SQL Query Executor on the page).

Please read the instructions on that page that are in RED.

Enter the following code.

Code:

---

UPDATE orders
SET payment_module_code = 'square_webPay'
WHERE payment_module_code = 'square';

---

Then click on send.

You'll be good to go

---

Is this still the method to fix the order details not showing up? Tried it and doesn't work.

solved. had to login and set the credentials for oauth again for it to work.

So why does the token expire even when there have been multiple orders processed in the last week?

Quote:

---

Originally Posted by barco57

So why does the token expire even when there have been multiple orders processed in the last week?

---

because the developer stinks?

i do not know.

how many clients do you have using this module? is it happening to all of them? is anyone else on the forum having this problem?

best.

> because the developer stinks?

Dunno - I've heard good things. They say he is a bit OCD about formatting though.

Some people seem to get the "OAuth access token has expired" more often than others - not sure why.

Are people just preventatively renewing the token every couple of weeks to prevent this issue?

I have a cron job that runs every 3 days that seems to keep my square web pay alive.
I set it to run at 01:01 every 3 days 1 1 */3 * * with the command php PATH_TO_M_STORE/squareWebPay_handler.php

Possibly because it's server dependent but the php command cron didn't work for me. From a post by @dbltoe the command I now use

HTML Code:

---

/usr/bin/wget https://mydomainDOTcom/squareWebPay_handler.php

---

the scheduling is set in the control panel. Seems to be working.

OTOH,
I've got one site without cron that has had no sales since the update to webpay.

Yet, the thing has never dropped.

go figure.

Run a test order to be sure it truly works?