danreylop

Yes, that could be the problem. What’s the theme you’re using? If it’s publicly available, I can install it in my testing site so I can try to reproduce the error.

In the meantime, please try using the mystile theme instead of a child theme to confirm that the problem is caused by the child theme.

If changing to a different theme doesn’t solve the issue, please open a WooCommerce support ticket with a link to this thread (then respond here with the Ticket Number so I can get notified and take a look at it). You can attach there a Ssystem Status Report, which is basic information about your store, like all your installed plugins versions and some general basic configuration. Here is a link to do so: https://woocommerce.com/my-account/create-a-ticket/

Thanks for keeping trying to solve this instead of giving up on the plugin! These kind of incompatibilities are expected the first weeks/months a plugin is released to the public, because nobody can test all the plugins, themes, or hosting configurations in the world 🙂

• This reply was modified 7 years ago by danreylop.

Hi @painterofthreads,

You should find the option to disable mod_security (maybe called ModSecurity) in the Security section of cPanel. But I don’t know how SiteGround is configured so maybe they don’t even allow to disable it.

Disabling it entirely is not advisable, but it’s the first step to solve your issue: checking that it’s actually caused by mod_security.

Roughly speaking, mod_security is a firewall that can be configured to “block” certain types of “suspicious” requests to your server. It can be configured with a set of “rules” to determine if a request should or shouldn’t be blocked. Under the most used set of rules (OWASP rules), some of our plugin’s requests were being detected as “suspicious” and thus were blocked. We fixed that, but there’s no way of telling what can happen under a completely different set of rules.

It would help to know which mod_security rules SiteGround uses (in their documentation they only say that “they update them every week”), so we can try to make our plugin be considered “safe” under those rules too.

Regards,

Hi,

Just to make sure we are in the same page, let’s recap.

You said that the crucifix has a weight of 0.02kg, but you didn’t mention its size. It should be small enough so that multiple crucifixes fit in a single envelope. Naturally, if that’s not the case, our program will calculate that you need one envelope for each crucifix. You’ll need to add the dimensions in the Product screen, just where you added the weight: here.

Then, you’ll need to go to WooCommerce -> Settings -> Shipping -> Packages, and you’ll see this screen. You’ll need to manually add there the envelopes and boxes you have available to put items inside. In your case, if I understood correctly, that would be an envelope of 24cm x 10cm x 2cm. Maybe make it a little taller than 2cm to make sure the crucifixes can fit inside.

Did you configure everything that way, and you are still having that problem? Please let us know, we’ll figure this out soon 🙂

Hi,

We’re sorry you’re experiencing those troubles setting up the plugin.

During the past week we’ve been fixing some problems with our Canada Post integration, could you please try again? Even if it doesn’t work, at least the exact error will be reported so we can fix it.

Hi Willie,

All the USPS shipping labels are in 4in x 6in size. The only change we can do to them is how are they arranged in a sheet of paper. What kind of paper do you want to print labels in? Is it letter-size paper with 2 halves, like this one? Or do you have a printer with 8.5 x 5.5 sheets of paper?

Hi Aaron,

This looks like a problem on your environment, but we would need more details to figure out where the problem is. What browser and OS are you using? Also, what version of PHP are you running on your store?

In the meantime, please try using Google Chrome, you can easily print an already purchased label in the same “Edit Order” screen: here’s how

We’re sorry for that inconvenience, we’ll fix it as soon as we figure out what’s happening.

Hi Michael,

We’re sorry your first experience with our plugin was a bad one.

We got the error recorded on our server. It’s related with the address validation performed by USPS before a shipping label can be purchased. Unfortunately, for privacy reasons, we don’t record the origin and destination addresses that caused the error. If you could give us (by private message if you prefer) the Origin and Destination addresses (screenshots would be fine too) that you used, we can work on fixing that bug.

Thanks in advance, and we hope you give this another chance soon 🙂