lennilg

I ended up buying PW WooCommerce Bulk Edit. I couldn’t wait for an update, it might not be more powerfull but it’s very simple to use, and works really well.

https://drive.google.com/file/d/1VnrddC9zBID44ndEMY3mHn9c7ir-mWw4/view?usp=sharing

That makes sense, I’d expect a checkbox that will state, leave blank, once checked, the input field is grey and the plugin ignores the localized string and defaults to blank instead.

I see, it still seems like the “Are you over %s years of age?” string is the only one that does not default to the pot file if it is unset, or set. If I remove the text at Yes or No fields in the messages tab, the plugin pulls it from the POT file and if I change language on my website, it translates into supported languages such as Italian, German and any other language that users have previous translated and uploaded to WordPress.com

In general, it’s best practice to rely on the POT files as fallback, rendering webmasters capable of removing the manually typed strings, and translating the plugin in to any and all language.

I did notice, that the line numbers in the POT file, does not match those of class-age-gate-activator.php

There’s nothing in the debug file, and no errors in dev console. I’ll try and record a video tomorrow but is will just illustrate that the upsells don’t copy over from the checked source product. If many are selected, it will remove all current upsells, and copy only 1 from the parent, no other.

Strange, it won’t pull the translation from the pot file, if I remove the string under the messages tab, the modal has no text, only yes / no.

Can’t right now, but I did notice the following 404 errors in the Developer Console.

DevTools failed to load SourceMap: Could not load content for https://www.example.com/wp-content/plugins/woo-bulk-editor/assets/js/easy-autocomplete/easy-autocomplete.min.css.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load SourceMap: Could not load content for https://www.example.com/wp-content/plugins/woo-bulk-editor/assets/js/easy-autocomplete/easy-autocomplete.themes.min.css.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

• This reply was modified 4 years ago by lennilg.

Thanks @aahulsebos

That did the trick. Still, having the min-width by default, wider than most mobilephones, seems .. untested. Now resolved by using the suggestion you provided.

I’ve noticed that same error and it does indeed slow down page load, we do however use Geolocation and thereby cannot disable it. If you don’t need it, or don’t want it running – simply do the following:

Go to WooCommerce -> General settings, Set the option “Default customer location” to “No Location by default. This will effectively disable it.

Okay, I’m totally clueless. I installed WordPress Health Check, and enabled Troubleshooting. Disabled the theme and plugins, enabled the theme and then one by one I enabled the plugins eventually all plugins were enabled, including child-theme and latest version of the Swatches plugin – and now, for the life of me.. I don’t understand why, but Swatches is working once again, and is now fully respecting Default Variations and supplied ?attribute_pa_option=

Could it be due to transience, cache or session salt? Beats me, but I’m glad it’s working!

It selects the variation, as seen in the video provided above. If possible varations are 3mg, 6mg, 9mg, etc. and I type in ?attribute_pa_option=3mg and press Enter, then the Dropdown selects 3mg as seen in the video. However, when Swatches is enabled. The urls attribute_pa_option is fully ignored.

My guess is, that Swatches chooses the variation Default Attribute, over the supplied attribute_pa_option provided by URL, Direct Linking.

So far, I’ve had to downgrade to version 1.0.60 and now everything is working again.

@pluginswoo any update on my issue?

We’ve been thinking about downgrading the version of this plugin, if this won’t affect potential security patches. So far, we’ve been dialing up customers to verify that the chosen products in their order, is indeed what was expected by the customers – and while it’s not a major issue; confusion does occur.

Yes, 100%

Sure thing, here’s a recording.

So far, I’ve been able to gather that disabling the plugin solves the issue at hand, while re-enabling it causes the same issue.

https://www.dampcig.dk/product/100ml-nicotine-base-0mg/?attribute_pa_option=pg50-vg50

https://www.dampcig.dk/product/1500mah-rpm-40-2ml-pod-kit/?attribute_pa_option=white