avong

Any updates from internal ticket?

Sorry, I think you’re still not understanding the issue.

What I’m referring to is anything in the exclusion list should not be manipulated by WP Optimize. Therefore, when a theme or a plugin enqueue’s a JS or CSS file via standard WP function, the SRC (JS) or HREF (CSS) should not be modified in any form or any string being stripped out.

Can you please take a bit more time to understand the issue raised and perhaps refer this to someone more technical/senior in the team to understand/resolve the issue?

• https://developer.www.ads-software.com/reference/functions/wp_enqueue_style/
• https://developer.www.ads-software.com/reference/functions/wp_enqueue_script/
  

That’s right. The minified scripts and css is fine, but scripts and css files on WP Optimize Exclusion list isn’t.

So any JS and CSS on WP Optimize exclusion lists should be left as is and (?ver=1.0.0) should be kept as is and not being removed . This is very important and hope your developers can resolve this asap.

Disregard the minified and un-minified references.

The issue is related to the scripts being excluded are removing the version attribute as defined in “wp_register_script” or “wp_enqueue_script” and “wp_register_style” or “wp_enqueue_style” WP functions.

Example:

wp_enqueue_script( 'some_js', '/path/to/foo.js',array(), '1.0.0');

This should output the HTML (without WP-Optimize minify enabled)

<script type="text/javascript" src="https:/example.com/wp-content/themes/example-theme/js/foo.js?ver=1.0.0" id="some_js"></script>

But when ‘wp-content/themes/’ is set as one of exclusion paths under WP-Optimize Minify, the “?ver=1.0.0” at the end is removed:

<script type="text/javascript" src="https:/example.com/wp-content/themes/example-theme/js/foo.js" id="some_js"></script>

Hi @benfterpay,

As per my original post, when Afterpay plugin is activated, it disabled my theme using standard WP function ‘wp_enqueue_scripts’ to include a custom JQUERY library . Please refer to the original for the detailed issue. This is happening without WP Optimize plugin active.

Prior to the Afterpay plugin update, there wasn’t any issues so I believe there’s some QA issue.

For simplicity and help you guys replicate, in our theme we ‘wp_deregister_script(“jquery”);’ and then ‘wp_enqueue_script( “jquery”, “//cdnjs.cloudflare.com/ajax/libs/jquery/3.2.1/jquery.min.js”, [], null, true );’. All subsequent JS files in our theme and other plugins (eg. WooCommerce) not longer gets enqueued if Afterpay plugin is activated, it’s fine when deactivated.

Otherwise can you please advise how to complete their external Afterpay support form that ask all those questions like (Merchant ID, etc) which we do not have.

@benfterpay The form request information that we don’t have.

Please resolve the plugin issue here without trying to send people to your internal system so that other WordPress plugin users can follow the issue that happened with your updates

It’s also affecting our website.

https://i.ibb.co/Nx50QLm/Screenshot-2023-11-01-at-2-15-30-pm.png

We’re having the same issue have the plugin updated to 2.1.9.

This is breaking our our WordPress theme’s front-end AJAX calls. Running WP 5.9.8

That worked. Will this get patched in the next update? Otherwise I will have to revert back to 4.2.

Yes. We’re using the older version of the plugin that only supports “Direct Post”

Field types such as “image_advanced”, “select” and “select_advance” bug still exists in Meta Box version 4.9.5 & WP 4.6.1.

Still creates unnecessary database row with value “a:0:{}”even though nothing is selected.