@odak71 – Just took a look, and I think there is some type of mistake here. That file is one line and the only thing it does is change the Admin menu item color for our “Extend” page to green: !function(n){“use strict”;window.PUM_Admin=window.PUM_Admin||{},n(document).ready(function(){n(‘a[href=”edit.php?post_type=popup&page=pum-extensions”]’).css({color:”#a0d468″})})}(jQuery);
Moreover, we don’t use .type() anywhere in our code with respect to jQuery.
We do use .type from the raw JavaScript language, but that simply accesses the HTML input elements type=”checkbox” attribute for example. Not gonna be part of the jQuery update or be deprecated unless they change HTML form elements as well, which at this point would break most of the internet.
I’m thinking you have something else going on here, likely an issue coming from another plugin/theme but triggered when we call jQuery in that script.
My suggestion is follow our guide on debugging JS errors, and click the little black arrow to see what JS scripts were run leading up to that error. You may find your theme for example has a script listed there which would be highly indicative that it were involved.
https://docs.wppopupmaker.com/article/373-checking-javascript-errors
Let me know, but as of now I’ve tested with WP 5.7 and have found 0 errors or warnings. We updated for WP 5.7’s jQuery changes before WP 5.5 was released, mainly because at that time they released the entire plan for the change over 3 versions. They also released a utility to test each set of changes, which we did. WP 5.5, 5.6, 5.7 were each a small stage in the migration to a newer version of jQuery. So in regards to jQuery changes coming, we tested all of them over a year ago and have seen 0 issues on our end so far for each update.
I will now point out also that there were ~100 users reporting issues with their popups when WP 5.5 & WP 5.6 each released. In 100% of those cases though the issue was traced back to a theme or another plugin that had not updated their code for the changes as needed. Since our plugin won’t work if your site is full of JS errors, they only noticed anything was actually wrong because our plugin stopped working.
Even in those cases, we helped them track it down every time which is how I know none of them were from our end, fortunately.
Hope that helps.
