rsnsb

Hi Lap,

Thanks for the reply – much appreciated!

I do find it a little odd that not many people have asked about it — I would have thought that it would be something that *everyone* in Europe (at least!) would have an interest in, as it would be a fundamental part of their email/marketing setup (even with the work-around of using an interest group in-place). Integrating with Mailchimp’s own core feature just makes life (and setup) easier :-).

In our particular case, it’s also a little tougher as we have a separate CRM system which also integrates with Mailchimp and we just need to make sure things tie up properly (e.g. when contacts subscribe or unsubscribe, and their ‘consent’) as contact records are also synced with CRM system and not just between the website and Mailchimp.

Regards,

Scott.

Hi there, yes – this was all resolved for us on another ticket. Thanks.
SB

Hi Thomas,
Thanks for clarifying – that’s cool. It’s great that you guys are actually that responsive – many aren’t!

As a minor suggestion it might be worth adding a note to that effect on that screen, as I’m guessing many people may just hunt for a ‘new ticket’ button (as I did) and get confused.

Thanks again,

SB

Thomas, for info:

If I go to https://woocommerce.com/my-account/create-a-ticket/ (when logged in) the “support request” section, once filled in allows me to ‘start chat’ but not just submit a ticket (in the conventional sense) and walk away. ‘Chat’ seems to be the only option, for which one has to hang around for and actually talk to someone then and there.

Now, to be fair, you guys are damn quick, and talking to someone is great, but sometimes you just want to submit a ticket and get on with life if it’s not a desperate problem! ??

SB

For info, this finally worked for me on our live site:
1) Deactivate the 1.0.38 plugin
2) You need to go SQL: Use your favourite MySQL tool to find the wc_square_access_tokens option in the wp_options table in the database and remove the option’s value, leaving it blank.
3) Our site is cached – I flushed all caches.
4) Re-activate the plugin and it should now hopefully ask you to reconnect to Square. Make sure you reconnect with an *owner* level Square account.

Regarding the plugin not being in the support ticket list: I ‘re-ordered/re-downloaded’ the plugin from the WooCommerce site, whilst logged in correctly, and it added it to my downloads list and it now magically appears in the support ticket list as well. (it’s of course free to download).

SB

We have the same problem. Reverting to 1.0.38 on our live site caused Square orders to fail. Oddly, as of last night, reverting to 1.0.38 works fine on our development site but not on our live one. On our dev site I removed and reinstalled (1.0.38) the plugin, disconnected/reconnected to Square and did a test order and it worked fine. I repeated precisely the same process on our live site and the plugin will not ‘disconnect’ from Square – the page just reloads with the button saying ‘disconnect’ again. I have a ticket open for this myself.

The support site seems very confusing: there appears to be no option to open a new ticket directly from what I can see. I had to talk to someone on the ‘chat’ and they did it for me (again). Also, in email notifications I receive about the ticket, I can’t click the link to view or reply to the ticket online, I get blank pages. I have to reply via email ??

SB

The WooCommerce Square plugin was briefly released as 2.0 (and then 2.0.1) but it had problems and was pulled and reverted back to 1.0.38 on Friday (26th July). Support should know that. ??

For those on this thread: despite rolling back to 1.0.38 we still have issues – all payments are now failing (not authorising). Square doesn’t seem to show anything on the dashboard there – the last ‘transaction’ being the last one before the 2.0x upgrade snafu. I’ve updated another thread about it with more information, but you might all want to check if your installations are working correctly.

Hi all,

I have the same problem – since reverting to 1.0.38 (including disconnecting and reconnecting to Square, twice!) we can’t process payments. They all fail (see below). I’ve checked the settings under the ‘integration’ tab for 1.0.38 and they seem good. The latest transaction shown in our Square dashboard is from last Friday before all this kicked off, there is no mention of any (all failed) over the weekend. All orders that tried to use Square have a status of ‘failed’ in WooCommerce. I have disabled Square payments (and am now directing people to Paypal) to get around this. I now also have to manually sort and tidy up a whole pile of failed orders ??

Help required!

Example error in ‘order note’ in a failed order:

Array
(
[0] => stdClass Object
(
[category] => AUTHENTICATION_ERROR
[code] => UNAUTHORIZED
[detail] => This request could not be authorized.
)

)
Order status changed from Pending payment to Failed.

-end-

I’ve just posted on the earlier 2.0.0 thread but, yeah, it (2.0.1) buggered us up as well in various ways. Reverting to 1.0.38 fixed all issues immediately.
SB.