Rob Goodwin

Yes, when I have “Force SSL on Checkout” checked, I get browser warnings that not all of my resources are secure (widget images are being pulled through http, etc). And yes, this error “empty string for ‘card'” happened when “Force SSL on Checkout” was checked.

Of course turning that OFF completely shuts off the Stripe payment plugin anyway, so there’s no way it could have been off.

That “Force SSL” also causes other problems. For one customers can’t ever get back to the HTTP version as all of the links have been converted to HTTPS. I installed WordPress HTTPS to combat that problem. (which gives me a “Sorry, session expired” error on checkout)

Thoughts?

Yeah. It kind-of sucks. But I use custom navigation and the site is fairly small, so it works. It would be great to get that problem fixed though – I agree.

[Solved – for me]
By the way… I put the pages (“checkout” and other pages that weren’t working) back into the root page directory and clicked “save” on the Jigoshop settings page. Everything started working again.

Apparently you just can’t adjust the page structure for some reason.

Yeah, this exact thing happened to me. Everything worked fine until I restructured all the pages to be sub-pages under the SHOP page. Now I can’t get to the checkout or cart pages.

Product pages and “add to cart” page work fine.

Anybody have any thoughts?

Good point.

The very best solution would be for the creator of the plug-in could incorporate functionality like this into the actual plug-in code rather than needing to resort to “hacks” like this.

Although I do like the newsletter plug-in in general, I was surprised that this feature wasn’t included in the first place.

What about this… changing the first line:
require(‘../wp-blog-header.php’);
to
require_once(‘./admin.php’);

… will not allow anyone to access the page unless they are logged in as an admin.

Does that solve the problem? or not really?