[Sean P]

Hello,

We have a patch for this issue, which is caused by the updates from WooCommerce 3.x+ and/or PHP 7+.

Please press “update” on your MyStyle Plugin and make sure you are on version 2.0.0, as this version starts supporting WooCommerce 3.x+

Thanks,

– Sean

[Sean P]

Hi Gordon,

Just an update that we’re working on the remaining SSL support items and then will be releasing our main plugin with 2.0.1 or higher later this week.

Until then you should be able to test if you can turn off SSL on your dev site.

Thanks,

– Sean

[Sean P]

Hi Gordon,

Judging by your other ticket for SSL support I’m going to assume this is closed!

WooCommerce 3.X and PHP 7.0.6 are both now supported in version 2.0.1 and up (releasing in the WP marketplace this week).

We will also be releasing SSL support for the HTML5 app with the updates later this week.

Thanks,

– Sean

[Sean P]

Hi Philicia,

The fastest workaround for this is to use the raster print file from the Flash customizer, since that’s the only version that support patterns right now.

2nd fastest is most likely inserting the pattern file, which I can email you in a moment.

The Renderer is still a BETA product so it doesn’t support Patterns or FX currently, but we are working on that for an upcoming release. I am looking into an early release of pattern support now.

[Sean P]

Hi Gordon,

Yeah I can see you’re using SSL on your /customize/ page. That’s most likely the issue.

Our next plugin release next week will have SSL support for HTML5 as well, but right now your pre-release is writing the iframe URL with https://.

Until then- temporary solutions:

1) Can you exclude that page from SSL so it’s regular https:// instead of https:// ?

I think there are some plugins that let you manage SSL on some pages and not others if you’re not able to do it via PHP or .htaccess yourself

2) Edit some php… (hacky)
If you are able to change the line that writes the iframe URL and replace https:// with https:// it would work.

3) Turn off full-site SSL and just use SSL for checkout (woocommerce setting)

[Sean P]

Hi Gordon,

Different browsers handle both Flash and SSL slightly differently, but if you have the HTML5-Only checkbox ticked in your settings, you can at least be sure the Flash handling is not the cross-browser inconsitency that you’re seeing.

The HTML5 app is not just a different UI, it’s also responsive and mobile compatible for all devices. The other UI runs on the Flash plugin, which is largely blocked by most browsers now that Chrome changed their default settings to block it in March (it can be turned on in settings but that’s not realistic for most users).

If the HTML5 app has everything you want, you may want to go with that only to be more consistent with all users.

Also, the html5 version is now SSL compatible as of yesterday!

Have you tried temporarily disabling all plugins except mystyle to test? That will tell you if it’s another plugin that is causing a conflict. By process of elimination you can find which plugin causes it and we could try to investigate it.

[Sean P]

Hi Gordon,

We have a pre-release version of our plugin that is compatible with your environment – WooCommerce 3.X with PHP 7.X

We also have pre-release versions of all of our add-ons, but there is still a lot of backwards compatibility for us to do before we can release it to the public. Because of this, I can send you the new versions just for your use as a ZIP file via email, and when we release it to the public you’ll be able to just press “update” on your plugin from your admin. Until then, it will think it’s on the current version, even though you’re a version ahead. Your version won’t have legacy support for our add-ons that don’t support WC 3.X, that we will be releasing in the next couple weeks, so for now just use our main plugin and our design manager, no other add-ons for another week or two.

Thanks!

– Sean

[Sean P]

Hi Gordon,

We are able to run our unit tests with our current DEV build for WooCommerce 3.X now (unreleased, coming out today or tomorrow) but we just noticed you’re running PHP 7.0.16… We’re suspecting this may be related to that PHP version. We’re working on building and testing a VM today with PHP 7.0.X and see if we can reproduce your exact error that way.

Next update later today or tomorrow.

Thanks,

– Sean

[Sean P]

Hi Gordon,

We’re in development on some patches for the issue. This is a WC 3.X issue only. If it’s convenient any 2.X WC build should be able to function properly just for your dev purposes so you’re not held up waiting for our next release with this patch.

In fact, if you use a lot of plugins I would caution updating above WooCommerce 2.X because they have deprecated magic getters and other major hooks that lots of plugins besides ours use, and there has been a huge amount of WP plugin bugs with lots of plugins that are still catching up (also notice woocommerce has put out 7 bug fix revisions already since they released 3.0 not that long ago). They’re still patching things themselves and stabilizing their new major version update.

Note I’m only referring to WooCommerce 2.X, not WordPress, which should be fine at the current 4.X version.

I will update again when we have the patches for this WC 3.X issue.

[Sean P]

Perfect, thanks.

We have a ticket open for our top senior wordpress plugin developer to look into this bug at their next availability, which should be tomorrow during PST business hours. We will update this thread with any info that we find, or with an update that we’ve shipped a fix.

Thanks,

– Sean

[Sean P]

Hi Tia,

We’re going to assume by no response that your issue was resolved and close the ticket. Please get in touch if you have any more issues we can help you with!

Thanks!

[Sean P]

Hi Gordon,

I see your active license account here and I can help you sort this out.

Can you please paste the server error that is occurring? We can easily debug it with that information on our end.

We have used MyStyle with storefront plenty of times, no issues. There are currently Storefront site themes using it that haven’t reported any problems yet, but that doesn’t mean there aren’t any.

For example, what version of Woo Commerce are you using? I know that WooCommerce 3.0 was shipped by WP with LOTS of bugs, and, they changed magic getters which broke lots of plugins on the web, but our latest update for MyStyle is compatible with those changes.

Can you paste your full WooCommerce diagnostic for us to check? That will have all of your exact plugins and versions numbers to see if there is any clues as to what’s messing up your system.

Which host do you use?

What’s your website URL?

[Sean P]

Hi Tia,

Just following up to see if you were able to resolve your issue.

You may want to verify that your versions are up to date with our most current releases. For the design manager, download it again from our site here under your account’s downloads. Remove yours and install the current version. This should eliminate any bugs as far as we know.

Thanks,

– Sean

[Sean P]

Hi Tia,

Can you send me a link to an example design on your site that is having the issue so I can reproduce it?

Thanks,

– Sean

PS: Here are some guidelines for bug reports to be investigated and diagnosed much faster:

General Bug Report Format

[Sean P]

Hi Chris,

Just following up one more time to see if you got this working OK with the “All Products” setting.

Thanks,

– Sean

[Author]

Posts