mbdNnse
Forum Replies Created
-
Forum: Plugins
In reply to: [WooCommerce] Hidden custom field in product variation editing pageFor anyone looking for the solution:
All you have to do is
1. add the CSS class “variation-needs-update” to the div with “woocommerce_variation” and “wc-metabox” classes.
2. Activate the “save” button just by removing “disabled” attribute from it.<div class="woocommerce_variation wc-metabox">
to
<div class="woocommerce_variation variation-needs-update wc-metabox">and then
<button type="button" class="button-primary save-variation-changes" disabled="disabled">Save changes</button>
to
<button type="button" class="button-primary save-variation-changes">Save changes</button>You can do it with JS and onchange eventListener listening your hidden input field. I did it this way.
Forum: Plugins
In reply to: [Album Gallery] Album GalleryHello @labtomarket,
jQuery is loaded too late so lightbox is not working. Are you using some kind of plugin that was installed to speedup your website? Something delays loading of jQuery and that’t the problem.Forum: Plugins
In reply to: [WooCommerce] Fatal error: Uncaught IntlException: Constructor@hiphopservers
I have the same issue and it’s probably caused by intl and UCI extension enabled in PHP. Try to disable it and then update woocommerce. That’s sad but I have the same issue and Woocommerce support just ignores me on the forum.Forum: Plugins
In reply to: [WooCommerce] Website won’t get up after update to 4.6.1Hey @3sonsdevelopment!
Will I get any more reply here?- This reply was modified 5 years, 6 months ago by mbdNnse.
Forum: Plugins
In reply to: [WooCommerce] Website won’t get up after update to 4.6.1Thanks for reply @3sonsdevelopment!
I tried to run it with woocommerce as the only active plugin and Storefront as active theme (I use child theme, storefront based). Sadly it didn’t work.
I have also uploaded 2 versions of woocommerce: 4.5.2 and 4.6.1. I have renamed it to woocommerce_new and woocommerce_old to be able to fast switch between versions (simply renaming one of these to “woocommerce”). 4.5.2 works fine and 4.6.1 is not working.
I have no idea what can be the reason of that issue…
Is there some way to prevent stack trace from being cutted?
What can be blocking rest api?
I was using it before in my custom plugins and it worked all the time.- This reply was modified 5 years, 6 months ago by mbdNnse.