Tagged: Woo Commerce Storefront
- May 23, 2017 at 10:42 am #11188
I have installed the My Style plugin with the Woo Commerce Storefront theme and the site crashes.
Tech support from the host is telling me the plugin is not compatible with the Storefront theme.
Is this a known issue?
Are there are fixes?
Wordpress is at ver 4.7.5 if that helps.May 23, 2017 at 10:43 am #11189
In addition I currently have the developer Alpha licence set up.May 23, 2017 at 12:39 pm #11190
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?May 23, 2017 at 3:12 pm #11193
Thanks for the quick response:
Error code is as follows. I got this from setting up a test site and activating the plugin. The following errors appear immediately and disappear when I deactivate the plugin. If I log out of the admin the site becomes inaccessible.
Warning: Declaration of MyStyle_SessionManager::persist(MyStyle_Session $session) should be compatible with MyStyle_EntityManager::persist(MyStyle_Entity $entity) in /homepages/8/d668142796/htdocs/app683191009/wp-content/plugins/mystyle-custom-product-designer/includes/entities/class-mystyle-sessionmanager.php on line 0
Warning: Cannot modify header information – headers already sent by (output started at /homepages/8/d668142796/htdocs/app683191009/wp-content/plugins/mystyle-custom-product-designer/includes/entities/class-mystyle-sessionmanager.php:0) in /homepages/8/d668142796/htdocs/app683191009/wp-includes/option.php on line 828
Warning: Cannot modify header information – headers already sent by (output started at /homepages/8/d668142796/htdocs/app683191009/wp-content/plugins/mystyle-custom-product-designer/includes/entities/class-mystyle-sessionmanager.php:0) in /homepages/8/d668142796/htdocs/app683191009/wp-includes/option.php on line 829
Host is 1and1.co.uk
Website URL is http://www.racketwraps.co.uk
Woo Commerce Ver 3.0.7
Woo Commerce System Status is as follows. I have some recommendations for WP Memory Limit and MySQL version but these don’t appear to have caused me any problems so far with the site.
Log directory writable:
WP memory limit:
40 MB – We recommend setting memory to at least 64MB. See: Increasing memory allocated to PHP
WP debug mode:
PHP post max size:
PHP time limit:
PHP max input vars:
5.5.54 – We recommend a minimum MySQL version of 5.6. See: WordPress requirements
Max upload size:
Default timezone is UTC:
WC database version:
Secure connection (HTTPS):
Hide errors from visitors
Active plugins (18)
Advanced Woo Search
by ILLID – 1.17
Contact Form 7
by Takayuki Miyoshi – 4.8-dev
Google Analytics for WordPress by MonsterInsights
by MonsterInsights – 6.1.10
Jetpack by WordPress.com
by Automattic – 4.9
Really Simple CAPTCHA
by Takayuki Miyoshi – 1.9
SiteOrigin Block Animations
by SiteOrigin – 1.0
Page Builder by SiteOrigin
by SiteOrigin – 2.5.3
Huge IT Slider
by Huge-IT – 4.0.3
SiteOrigin Widgets Bundle
by SiteOrigin – 1.8.6
Storefront Footer Text
by Wooassist – 1.0.1
Title Toggle for Storefront Theme
by Wooassist – 1.2.3
by WooThemes – 1.5.4
by Netbaseteam – 1.6.2
WooCommerce PayPal Express Checkout Gateway
by WooCommerce – 1.2.1
WooCommerce Stripe Gateway
by WooCommerce – 3.1.8
by Automattic – 3.0.7
by WooCommerce – 1.7.2 – Network enabled
by Team Yoast – 4.8
Number of decimals
Taxonomies: Product types
external (external), grouped (grouped), simple (simple), variable (variable)
Taxonomies: Product visibility
exclude-from-catalog (exclude-from-catalog), exclude-from-search (exclude-from-search), featured (featured), outofstock (outofstock), rated-1 (rated-1), rated-2 (rated-2), rated-3 (rated-3), rated-4 (rated-4), rated-5 (rated-5)
#11 – /shop
#12 – /basket
#13 – /checkout
#14 – /my-account
– If you’re modifying WooCommerce on a parent theme you didn’t build personally, then we recommend using a child theme. See: How to create a child theme
I hope the above helps.
Gordon McCombeMay 23, 2017 at 3:14 pm #11194
### WordPress Environment ### Home URL: https://racketwraps.co.uk Site URL: https://racketwraps.co.uk WC Version: 3.0.7 Log Directory Writable: ✔ WP Version: 4.7.5 WP Multisite: – WP Memory Limit: ❌ 40 MB - We recommend setting memory to at least 64MB. See: Increasing memory allocated to PHP WP Debug Mode: – WP Cron: ✔ Language: en_GB ### Server Environment ### Server Info: Apache PHP Version: 7.0.15 PHP Post Max Size: 6 MB PHP Time Limit: 30 PHP Max Input Vars: 1000 cURL Version: 7.38.0 OpenSSL/1.0.1t SUHOSIN Installed: – MySQL Version: ❌ 5.5.54 - We recommend a minimum MySQL version of 5.6. See: WordPress requirements Max Upload Size: 64 MB Default Timezone is UTC: ✔ fsockopen/cURL: ✔ SoapClient: ✔ DOMDocument: ✔ GZip: ✔ Multibyte String: ✔ Remote Post: ✔ Remote Get: ✔ ### Database ### WC Database Version: 3.0.7 WC Database Prefix: k6bm8djqtr woocommerce_sessions: ✔ woocommerce_api_keys: ✔ woocommerce_attribute_taxonomies: ✔ woocommerce_downloadable_product_permissions: ✔ woocommerce_order_items: ✔ woocommerce_order_itemmeta: ✔ woocommerce_tax_rates: ✔ woocommerce_tax_rate_locations: ✔ woocommerce_shipping_zones: ✔ woocommerce_shipping_zone_locations: ✔ woocommerce_shipping_zone_methods: ✔ woocommerce_payment_tokens: ✔ woocommerce_payment_tokenmeta: ✔ ### Security ### Secure connection (HTTPS): ✔ Hide errors from visitors: ✔ ### Active Plugins (18) ### Advanced Woo Search: by ILLID – 1.17 Contact Form 7: by Takayuki Miyoshi – 4.8-dev Google Analytics for WordPress by MonsterInsights: by MonsterInsights – 6.1.10 Jetpack by WordPress.com: by Automattic – 4.9 Really Simple CAPTCHA: by Takayuki Miyoshi – 1.9 SiteOrigin Block Animations: by SiteOrigin – 1.0 Page Builder by SiteOrigin: by SiteOrigin – 2.5.3 Huge IT Slider: by Huge-IT – 4.0.3 SiteOrigin Widgets Bundle: by SiteOrigin – 1.8.6 Storefront Footer Text: by Wooassist – 1.0.1 Title Toggle for Storefront Theme: by Wooassist – 1.2.3 Testimonials: by WooThemes – 1.5.4 Nbdesigner: by Netbaseteam – 1.6.2 WooCommerce PayPal Express Checkout Gateway: by WooCommerce – 1.2.1 WooCommerce Stripe Gateway: by WooCommerce – 3.1.8 WooCommerce: by Automattic – 3.0.7 WooCommerce Helper: by WooCommerce – 1.7.2 – Network enabled Yoast SEO: by Team Yoast – 4.8 ### Settings ### API Enabled: ✔ Force SSL: ✔ Currency: GBP (£) Currency Position: left Thousand Separator: , Decimal Separator: . Number of Decimals: 2 Taxonomies: Product Types: external (external) grouped (grouped) simple (simple) variable (variable) Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog) exclude-from-search (exclude-from-search) featured (featured) outofstock (outofstock) rated-1 (rated-1) rated-2 (rated-2) rated-3 (rated-3) rated-4 (rated-4) rated-5 (rated-5) ### WC Pages ### Shop base: #11 - /shop Basket: #12 - /basket Checkout: #13 - /checkout My account: #14 - /my-account ### Theme ### Name: Storefront Version: 2.2.2 Author URL: https://woocommerce.com/ Child Theme: ❌ – If you're modifying WooCommerce on a parent theme you didn't build personally then we recommend using a child theme. See: How to create a child theme WooCommerce Support: ✔ ### Templates ### Overrides: –May 23, 2017 at 3:27 pm #11195
BTW, I have seen reported issues with SSL certificates which my main site has but I get the same problem on a test site which doesn’t have an SSL certificate.May 23, 2017 at 7:29 pm #11196
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.
– SeanMay 24, 2017 at 5:00 pm #11202
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.May 25, 2017 at 2:05 pm #11208
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.
– SeanMay 25, 2017 at 3:36 pm #11211
Thanks for the update.May 26, 2017 at 5:33 pm #11223
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.
– SeanMay 30, 2017 at 2:27 pm #11237
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.
- The topic ‘Plugin Crashes Woocommerce Storefront Theme’ is closed to new replies.