silvadiego705

Hello @misulicus,

thank you for the reply. That was very helpful. I’ll try changing the Stripe integration method and see how that works with Apple/Google pay.

The missing phone number field is definitely connected to the /public/js/mollieIn3.min.js file, the file is loaded regardless if the In3 method is enabled or not. That is easy to test: deactivate the In3 payment method and then check on the frontend if the mollieIn3.min.js file is loaded or not. And according to the enqueueFrontendScripts() function in the /src/Assets/AssetsModule.php the mollieIn3.min.js file should load only when the In3 payment is activated.

The phone number isn’t always removed. Only by repeatedly refreshing the page sometimes the phone number is removed.

The phone number is removed upon the JS “updated_checkout payment_method_selected” trigger. The JS code attempts in fact to replace the phone number code with some other HTML code, but that happens only depending on the value of the input[name=”payment_method”] field. I assume that field’s value is also changed sometime after the page load and, depending if the “payment_method_selected” happens before or after this change, it replaces the phone number field with “NULL” or with desired HTML code. (It is hard deciphering the minified mollieIn.min.js file).

Anyway, would you please make sure to load the mollieIn3.min.js file only when the In3 payment method is activated. That would solve a lot of headaches for most of us.

And please don’t remove posts from this discussion. This is definitely counterproductive.

Hello @niklasinpsyde,

there were 8 people discussing about the missing phone number field. There was plenty of useful information related to the missing phone number. Would you bring back that discussion? Hiding it doesn’t really help.

Actually I need to create a “mouseover” event over an image, but that doesn’t work because the original image is replaced with a clone. By default the cloned objects don’t copy the event handlers (see jQuery clone()), so the “mouseover” event disappears.

Then I found the “jetpack-lazy-loaded-image” trigger that theoretically could’ve helped me. But that line turns out to be just dead code.

Howdy –

I’m talking about a JavaScript trigger, not a WordPress PHP action hook. Please open the “/jetpack/modules/lazy-images/js/lazy-images.js” file and look for the following line:

// Fire an event so that third-party code can perform actions after an image is loaded.
theClone.trigger( 'jetpack-lazy-loaded-image' );

I want to write a “third-party code that performs actions after an image is loaded”, as mentioned in the comment.

Another question, unrelated to the topic:

The public/js/woocommerce-product-gallery-slider-public.js file is enqueued even if the code inside does absolutely nothing. Am I missing something?

Yes, it does work with the “WooCommerce 3.0+ Fix” enabled”.

Is there any reason why the fix isn’t applied automatically when WooCommerce 3.0+ is enabled? You can check the WooCommerce version with the following code:

if ( class_exists('woocommerce') && version_compare( WC_VERSION, '3.0', '>') ) {
    \\ enqueue prettyPhoto CSS and JS
}

Same problem here: the download button is missing if only one theme is present.

//

• This reply was modified 7 years, 7 months ago by silvadiego705.