larsvonhierblau

Getting something similar and in the logs for wc-ppcp is written: Error Error creating PayPal order. Msg:Request is not well-formed, syntactically incorrect, or violates schema. Params: Array . That seems to be the case since the latest Woocommerce 7.5.0. Here are digital files (pictures) sold so no address or country code is needed.

Some more Info on it:

[0] => Array
                        (
                            [field] => /payer/address/country_code
                            [value] => undefined
                            [location] => body
                            [issue] => INVALID_PARAMETER_SYNTAX
                            [description] => The value of a field does not conform to the expected format.
                        )

                    [1] => Array
                        (
                            [field] => /payer/address/country_code
                            [value] => undefined
                            [location] => body
                            [issue] => INVALID_STRING_LENGTH
                            [description] => The value of a field is either too short or too long.
                        )

                )

            [links] => Array
                (
                    [0] => Array
                        (
                            [href] => https://developer.paypal.com/docs/api/orders/v2/#error-INVALID_PARAMETER_SYNTAX
                            [rel] => information_link
                            [encType] => application/json
                        )

                    [1] => Array
                        (
                            [href] => https://developer.paypal.com/docs/api/orders/v2/#error-INVALID_STRING_LENGTH
                            [rel] => information_link
                            [encType] => application/json
                        )

• This reply was modified 1 year, 8 months ago by larsvonhierblau.

Hi, this issue could be caused by several things. One would be, you are using a specific plugin which generates a custom url for the users dashboard. Another could be that you are forcing the url to be cached. You could exclude this specific URL in the cache settings and make it to either private cached or not cached. If this doesn’t help I’d recommend to open a support ticket.

Hi Eduard, you guys are really fast. Big compliment. I can confirm the Beta fixes it. How are they outputting the Qty. selector now ?

Hi, just to follow up since the latest beta i got from your support the refund error is gone however now I have the major amount of customers complaining that the PayPal options doesn’t work at all. I posted above the error. It’s again country related. I am using woocommerce checkout field editor the official plug-in from woocommerce

• This reply was modified 2 years, 5 months ago by larsvonhierblau.

Hi, thanks for the reply. I have tested it and it seems to work for now.

Thanks for your reply and the solution. I grab the country via GEO IP for currency changes, however it shouldn’t be necessary to put a country hence this might be not necessary for digital products. I hope this could be fixed soon.

The exact error is: An error occurred while attempting to create the refund using the payment gateway API.

Log shows: Refund failed: No country given for address. –> I am using woocommerce Checkout field editor hence for digital products (images) i would need no address.

• This reply was modified 2 years, 5 months ago by larsvonhierblau.

Is there a way to still enable it? Or what’s the hard limit for file sizes?

Hi @davidanderson thank you very much! I before didn’t add the define (..) on the top. It turns out it really works great. Just one more question, is this just a temporary solution or will this change, and if so would it be announced? Btw. thanks for the amazing support! Really rocks

Hi, @davidanderson the issues seems to be related to /tmp space of ubunutu. Updraft seems to fill it up during the upload to S3 and not getting rid of the already uploaded chunks. This seems to accumulate until the /tmp is running out of space. This happens on all chunk settings (used several). I created a temporary new sized /tmp and the backup went through without issues. But this method isn’t sustainable hence it causes the ram to fill up. Is there a way to use /tmp directory within wordpress which can be defined via wp-config?

• This reply was modified 2 years, 8 months ago by larsvonhierblau.

Hi, I tried but it didn’t help. The Upload and execution works now but seems to stuck at following error:
Amazon S3: upload: all chunks uploaded; will now instruct S3 to re-assemble
4324.114 (6) Amazon S3: re-assembly error (others0): Error executing “CompleteMultipartUpload”

I made a new bucket already. I checked my cron jobs and i also added the litespeed noabart tag. However the error seems to persist. I also decreased the split file size. The issues didn’t accuse with significantly older versions.

• This reply was modified 2 years, 8 months ago by larsvonhierblau.

Ah also one of my clients who’s purchased your theme, thats why i am writing here, has the Blocksy Theme running with wishlist enabled on a litespeed server. He asked me for help and i figured if litespeed uses ESI for the woocommerce cart it somewhat interferes with you wishlist. It causes strong behaviors such as you can not remove the items anymore or all but the last one etc.

Wow you guys are really fast and amazing!!!!!!!! Thank you so much for the help. Really I am speechless how fast you guys are.

@beyondaries use ftp and put – this in front of the folder name of woocommerce and the email customized to rename it. With this it’ll be deactivated. Login to you page and rename the folders back to normal. You can use wp rollback to go to a earlier version of woocommerce.

I can reach your site. It’s just slow