Syde Joost

Hello @alpha966123

Thank you for reaching out to us, we are here to help.

You are correct, we have not added this feature in our plugin, but we may add it in the future. So far, simply nobody ever asked for it, but it should be possible.

We have created a feature request for this and will discuss it soon with the product owner. I think in test mode Mollie may not report back the fees, making the testing a bit more tricky, but I will need to do some investigations to figure out what is possible and how we can go about creating this functionality.

The feature request has been linked to this thread, so you should get updated once we have the feature available. Just to set the right expectations, this could take some time.

Kind regards,
Joost

Hello @calderwood

Thank you for reaching out to us, we do appreciate it! However, we are currently not doing much updates and development of new features, we do try to keep our plugin functional for current releases. This is why we would appreciate you sending us any details you have available about this, so we can see if we can do anything about this.

If you would be willing to, please open a ticket with our service desk. You can find the instruction for this here: https://zettle.inpsyde.com/docs/request-support/
(please add the URL of this thread in the ticket as well).

Once we have this, we can have a look and possibly get a developer involved to see if we can get some improvements/fixes in place.
Thanks again for your proactivity, we really appreciate it.

Kind regards,
Joost

Hello @fabioweb

Thank you for reaching out to us, we are here to help.

This is not so much an error as it is only checking if Reference Transactions are activated for your account. If you want to read more about Reference Transactions, please go here.

I don’t think any action needs to be taken, so I will mark this thread as resolved.

Kind regards,
Joost

Hello @giulia65

thank you for reaching out to us, we are here to help.

For your issue, we expect that this is likely only an error you see in your logs. No acute problem on the site. This error was probably triggered because site was navigated while plugin was updating; it should not affect the site, please check and verify if this is the case.

Hello @pattyjansen and @hossammoghrabi, your errors are most likely not related and have nothing to do with each other. here is a short response to the:

• second error: Plugin conflict – this error is a compatibility issue with another plugin implementing a more recent?psr/log?version. It should not be a widespread problem.
  This compatibility issue may also arise with some more advanced development setups like Bedrock, but it’s not something we can address at this time.
  Here is the open GitHub issue:?#1518
  In most cases, the conflicting plugin causing this error can be found by forming a?conflict test. In some cases, other plugin developers may be able to downgrade their?psr/log?implementation for improved compatibility.
  We are in ongoing discussions about increasing e.g. the minimum supported PHP and WC versions which is a requirement for us able to address these compatibility problems properly. But I expect it will take few more months before we can provide a long-term solution for this.
• third error: The TypeError is most likely caused by a plugin conflict. You may want to perform a full conflict test to rule out eventual issues with the theme or a different plugin. We recommend temporarily activating the default theme Storefront and disabling all other plugins except for?WooCommerce and?PayPal Payments to see if the behavior persists. Here’s a guide that explains the steps in more detail: How to test for conflicts

In summary, all three of these are separate issues and deserve a separate thread. @pattyjansen and @hossammoghrabi, if my response above does not help, please raise your own thread for this, since this thread was initially opened for the issue @giulia65 raised.

Kind regards,
Joost

Hello @lparga

Thank you for reaching out to us, we are here to help.

In order to use Advanced Card Processing (this is the payment method that allows you to pay without having a PayPal account), you need to get your PayPal account approved for using this feature. You can do the request for this by selecting the option while initially onboarding the plugin. Or you can go to this link and follow the instructions to do the same after onboarding.

After the request has been approved, you should get the payment method added to the WooCommerce payment method overview.

Here, you can find some details on the countries that allow using this payment method, and here are some more general details on the payment method within our plugin.

Please let us know if you have any further questions.

Kind regards,
Joost

Hello @christopherplus,

Thank you for reaching out to us, we are here to help.

I just checked on my own environment if the same behavior occurred for me, but this setting is being saved when I press the button “save changes”. I am not sure what could be causing such a situation. Have you tried deactivating all other plugins and trying this again? Maybe there is a plugin conflict present?

If that doesn’t help, you might want to

open a ticket with our service desk, so we can take a look at your system report and logs. You can find the instruction for this here: https://paypal.inpsyde.com/docs/request-support/
(please add the URL of this thread in the ticket as well)

Kind regards,
Joost

Hello @fierceknockouts

Sorry to hear about the problems you are facing. I have just tested the link, and it does go to the website. I have also tested creating a private support ticket via the instructions shown there, and that also works as expected. Maybe you should try using another web browser (I would always advise trying Chrome)?

The functioning of the device is not something that I can support. Our team/company only creates and supports the WordPress plugin, so anything that occurs between the WooCommerce site and the Zettle web interface can be related to a problem that our plugin can cause. For issues with a non-responding device, you need to contact Zettle directly.

At this moment, I don’t have many details I can use to provide you any other advice. Please try again to open a private engagement, or provide some screenshots here that show your settings of the described pages. It would also help to get more details on your attempts to fix this; what did do, what did you see?

Pending your response.

Kind regards,
Joost

Hello @fierceknockouts

Thank you for reaching out to us, we are here to help.

The most common cause for this to occur, is when you have assigned a tax class to a product that is not completely configured. You can check this by going to the product, finding out what tax class it uses, then go to the WooCommerce > Settings > Tax and check the tax class tab, to see if there is any entry populated with the tax class rates. If it is empty, you need to press “Insert row” and add any details that are required.

If this is not the cause of your problem, you might want to share some screenshot of all settings that you use and details of your products. Maybe it is caused by something else, but we need to have a look to find out what that could be. If you don’t feel comfortable sharing those details on a public forum, please open a ticket with our service desk. You can find the instruction for this here: https://zettle.inpsyde.com/docs/request-support/
(please add the URL of this thread in the ticket as well)

Let me know if this helped you resolve the issue or if you require additional support.

Kind regards,
Joost

Hello @qurdis

Yes, if you want to have the product bundles also shown in the Zettle POS library, that will be an issue, because this product type cannot be synchronized by our plugin. Also, if you would have any way of adding such a product manually to the Zettle library, the individual products would not sync correctly to WooCommerce.

The only option is to only sell these product bundles via the online store. There is currently no option to add a product bundle on Zettle, so I also don’t see any option to create what you are looking for. Maybe I am still missing something? How can you create a product bundle in Zettle? This seems to be the start of the problem, and you might need to ask Zettle for options on this situation?

Please let me know if there is anything more I can do for you.

Kind regards,
Joost

Hello @effectedduck

I believe we have continued our investigation via a private engagement and found that this issue was being caused by a conflict with the plugin “LiteSpeed Cache: door LiteSpeed Technologies – 6.1”.

I will mark this thread as resolved. Please let us know if this is not the correct action, and you require additional support from us.

Kind regards,
Joost

Hello @qurdis

Thank you for reaching out to us, we are here to help.

I have just tested the situation you described:
– created a product bundle with 4 different products included.
– Added different amounts of products in the bundle.
– Sold a single bundle.
– Verified that the individual product count in WooCommerce decreased when the bundle was sold.
– Verified that the individual product count in Zettle decreased as a result of the changes in WooCommerce.

So, everything seems to be working as expected for me on my test environment. I have set the product bundle to not have any inventory count and don’t see (or expect to see) the bundle synchronized to Zettle (since this product type is not possible to synchronize).

Is there anything here that doesn’t work for you in the same way? Am I missing any detail of the problem you are facing? Please provide more details. If you don’t feel comfortable sharing those details on a public forum, please open a ticket with our service desk. You can find the instruction for this here: https://zettle.inpsyde.com/docs/request-support/
(please add the URL of this thread in the ticket as well).

Kind regards,
Joost

Hello @daver56

since we are currently working via the private engagement, we will mark this thread as resolved.
We did find out that the JPG image you are using is causing the issue and if we compress it differently, the image does get synced. The strange this we saw is that the image does work via the sync, but not via the manual upload via the Zettle interface. I checked with Zettle, but did not get much back from them on why this was occurring, so advised you to do the same via the Zettle Support option.

If you hear any other option/solution back from Zettle that could help resolve this issue, please share here, so the community will be able to find this information. From our side, the plugin is functioning as expected, so this is why we are marking the thread as resolved.

Kind regards,
Joost

Hello,

Since we did not receive any response or follow-up questions from you, we will assume you got this working to your requirements. If you still have any more questions for us, please open a new thread, because we will mark this one as resolved.

If this issue was not yet resolved, you might want to open a private engagement, so you can share the system report and logs easier and more securely with us.

Kind regards,
Joost

Hello,

Since we did not receive any response or follow-up questions from you, we will assume you got this working to your requirements. If you still have any more questions for us, please open a new thread, because we will mark this one as resolved.

Kind regards,
Joost

Hello @michaelk85 and @toineenzo

I have had some chats with the team about this, because this is really not something I have seen before. My expectation was confirmed, The documents on?woo.com?are incorrect. Mollie was one of the first payment gateways to support the block checkout, so the Mollie plugin 100% supports the block checkout. If it doesn’t work for you, you need to troubleshoot your setup and environment as advised before.

If this doesn’t help you find any cause for the issue you are experiencing, you can still reach out to our 2nd level support here, so they can have a look at the environment, system report and logs.

Kind regards,
Joost