rtddev

@javib6 thanks.

We’ve decided to re-write the PaySimple plugin, and have already resolved the Internal Server error issue.

The problem with PayPal & Stripe, is their “simple” pricing is quite a bit more expensive than the current PaySimple pricing my colleagues are paying.

At higher volumes of payment processing, there’s a big difference between high 2% (and low 2% processing fees.

We’ve done some initial fully-loaded pricing comparisons, and even with the $45 monthly cost, it does look like the cost is less to use PaySimple. We’re looking deeper into the reports to confirm that is indeed the case.

We may be able to negotiate better pricing with Stripe of PayPal, but that will be our back-up plan.

At the moment, we have our PaySimple for WooCommerce plugin working in a v1.0 state, but we are quickly adding features to fully leverage the PaySimple API and have a more comprehensive feature set.

@javib6 – So, if you haven’t heard back from them, did you ever find a way to correct the Internal Server error using their PaySimple plugin?

If not, did you find an alternate PaySimple WooCommerce plugin?

If not, did you go a different direction with your credit card processing provider?

2-3 weeks is a long time to not hear back from a business, and we just don’t have that long to figure out the problem.

For clarity, we had no issues testing on Sandbox — everything worked fine, and our test orders processed without any problems.

Once we enabled the credentials for Production, we got the Internal Server error.

I checked the PaySimple end points in the plugin itself, and they did not match the current API information from the PaySimple website. So, I did try changing the endpoints in the code, but that didn’t resolve the issue either.

We’re seeing the following error in our WooCommerce fatal errors log:
CRITICAL Uncaught Error: Call to a member function deepAll()
related to > woo-paysimple.php, line 513

I’ve opened a support ticket on the company’s website in hopes that someone will get back to us quickly.

If that doesn’t happen, I may have to ask another plugin developer to see if they can help us debug the issue.

@designguy @javib6 Did you get any resolution of this issue from @dots?

We’re having the same issue.

Ok, thanks Praveen.

Appreciate you getting back to me.

Ok, thanks Takayuki.

Hey Nick,

I figured out the problem.

It was a plugin conflict with Ultimate Addons for Visual Composer.

It was related to WooCommerce 3.0 that had been addressed & fixed in Version 3.16.10 of the plugin.

I upgraded to the latest version of that plugin and it fixed the issues I reported in my last post.

Hope the information helps anyone else experiencing the same problem!

Hey Nick,

We recently updated to 3.0.5.

We’re having the same issue as you, related to the empty Product modal.

But in addition to that, our Add Order > Customer field dropdown is empty — meaning we can’t look-up customers when adding an order.

Can you share a bit more about where the kad_adminscripts.js is, and how you resolved the conflict?

Did you put the kad_adminscript.js of the working theme into the non-working theme’s folder, or are you saying that kad_adminscript.js wasn’t needed?

Everything on the front-end website seems to be working fine, but we’re running into a few various issues inside of WordPress/WooCommerce admin.

Thanks in advance for any insight/help you could provide.

• This reply was modified 7 years, 6 months ago by rtddev. Reason: Checked "notify me"

Agreed, seems easier to export your product & variant information and send them to a company to create barcode labels for you.

I just learned that the dymo 4xl thermal printer software can create barcodes as well as do a mailmerge type function from a file of data (CSV). This might be another option.

To easily export SKU & Variant level data, there may be free WC data export plugins available. Our PickingPal Extension for WooCommerce does this too, so if you need some help, for a small fee we could possibly install PickingPal temporarily to your shop, export the data needed for the barcodes labels to CSV, then uninstall.

We do have a relationship that allows us to get barcode labels printed rather inexpensively, so if you’d like, visit pickingpal.com and contact us for more information about that.

Might be easier to export your product information and send them to a company to create barcode labels for you.

The other way, is to generate your barcodes with an online barcode generator tool and use Avery labels with your inkjet, laser, or thermal printer.

I’ve tested this plugin and the barcode layout is not optimal, though it is easy to create barcode images for multiple products.

We do have a relationship that allows us to get barcode labels printed rather inexpensively, so if you’d like, visit pickingpal.com and contact us for more information about that.

Hello @dwd – Sorry for the inconvenience. We have not updated our Free/LITE version of this plugin to work with WooCommerce 2.2.

There is a new version coming out soon that should address any functionality issues.

If you need an immediate resolution, the paid version of the plugin/extension is fully compatible with WC2.2.

Thanks for understanding!

Excellent.

I saw your comment about cachify and was going to recommend you disable and test. Was also going to recommend Quick Cache as an alternative.

Glad you got it figured out before I had the chance to reply!

Hi,

Off hand, not exactly sure why our plugin would not work with your theme’s internal ad spots, but it appears to behaving the same way as if our plugin was not installed.

Will submit to our dev for review and see if we can determine what might be the conflict with your theme.

Ok. Thanks!

ok. thanks!

Sorry toby04, but WordPress didn’t send an email letting us know about your support question.

Is this issue still occurring??