Marcus Karlos

Hi Gal Baras, its done))

+ new JS issues in WP Dashbord

TypeError: t.tablePrepareColumnItems is not a function
at ReportReAuth-d9fc4de3.min.js:1:38727
at c.pD as _l
at c.kt (ReportReAuth-d9fc4de3.min.js:1:38594)
at RD.e._render (vendor-b19955ae.min.js:5:22157)
at c.n (vendor-b19955ae.min.js:5:32204)
at e.get (vendor-b19955ae.min.js:5:28396)
at e.run (vendor-b19955ae.min.js:5:29133)
at Mk (vendor-b19955ae.min.js:5:34414)
at Array. (vendor-b19955ae.min.js:5:25959)
at uM (vendor-b19955ae.min.js:5:25371)
kq @ vendor-b19955ae.min.js:5

+ that when

Play.

1. Click “Screen Options”
2. Try disabling MonsterInsights
3. Error in console

vendor-b19955ae.min.js:262 Error: <path> attribute d: Expected number, "M e -16 6 A -6 -6 …".vendor-b19955ae.min.js:262 Error: <path> attribute d: Expected number, "M e -16 6 A -6 -6 …".vendor-b19955ae.min.js:262 Error: <path> attribute d: Expected number, "M e -16 6 A -6 -6 …".

The problem disappears only when we switch the widget to smaller mode. In full screen mode, the widget logs this error! I think the error is that the function that the script is looking for is missing in full mode.

Yes, but you need to make these changes in the update so that I don’t have to manually edit your code every time, otherwise I will refuse to use the plugin.

Okay i will do

I hope u help that, i fix your script and my issues is resolved

In new update 9.2.2 – is not fixed( lol…

This is own fix i do for 2min

/**
 * Update script tag.
* The vue code needs type=module.
*/
public function script_loader_tag( $tag, $handle, $src ) {

    if ( ! in_array( $handle, $this->own_handles ) ) {
        return $tag;
    }

    // Check if the 'monsterinsights-vue-frontend' script is the target
    if ( 'monsterinsights-vue-frontend' === $handle ) {
    // Remove any existing type attribute
    $tag = str_replace( 'text/javascript', 'module', $tag );
    }

    // Change the script tag by adding type="module" and return it.
    $html = str_replace( '></script>', ' type="module"></script>', $tag );

    $domain = monsterinsights_is_pro_version() ? 'ga-premium' : 'ga-premium';
    $html   = monsterinsights_get_printable_translations( $domain ) . $html;

    return $html;
} 

+ New bug in Dashboard WordPress

Error: attribute d: Expected number, "M e -16 6 A -6 -6 …".
TypeError: t.tablePrepareColumnItems is not a function
at ReportReAuth

Bug Report: Conflict in Script Tag Type Modification for Module Scripts

Description:

During independent testing, a bug was identified involving the function public function script_loader_tag( $tag, $handle, $src ) located in admin-assets.php. This function is intended to set specific scripts as modules by modifying the <script> tag. However, an issue was observed, where despite modifications from the filter, the <script> tag’s type remains as text/javascript instead of module.

Log results indicate that the filter correctly applies changes to the <script> tag. Nevertheless, the script type is not updated to module because an existing type="text/javascript" attribute is likely predefined, either within the plugin code or influenced by browser behavior. Consequently, for the file js/frontend.min.js, the script type remains incorrect, causing the module-based script not to load as intended.

Proposed Solution:

To address this issue temporarily, I suggest modifying the function in admin-assets.php under the path /wp-content/plugins/google-analytics-for-wordpress/includes/admin as follows:

/**
 * Update script tag.
 * The vue code needs type=module.
 */
public function script_loader_tag( $tag, $handle, $src ) {

    if ( ! in_array( $handle, $this->own_handles ) ) {
        return $tag;
    }

    // Check if the 'monsterinsights-vue-frontend' script is the target
    if ( 'monsterinsights-vue-frontend' === $handle ) {
        // Remove any existing type attribute
        $tag = preg_replace( '/\stype="[^"]+"/', '', $tag );
    }

    // Change the script tag by adding type="module" and return it.
    $tag = str_replace( '></script>', ' type="module"></script>', $tag );

    $domain = monsterinsights_is_pro_version() ? 'ga-premium' : 'ga-premium';
    $tag    = monsterinsights_get_printable_translations( $domain ) . $tag;

    return $tag;
}

This modification removes the type="text/javascript" attribute and correctly sets type="module". It temporarily resolves the console errors and ensures proper functionality of the plugin. We hope the development team can review and implement a permanent fix to detect and set the correct module type without conflict.

Impact:

This issue affects both the Pro and Lite versions of the plugin, preventing the script and its dependencies from executing correctly.

Results After the Fix:

1. Pro Version: <script src="DEMOSITE/wp-content/plugins/google-analytics-premium/pro/assets/vue/js/frontend.min.js?ver=9.2.1" id="monsterinsights-vue-frontend-js" type="module"></script>
2. Lite Version: <script src="DEMOSITE/wp-content/plugins/google-analytics-for-wordpress/lite/assets/vue/js/frontend.min.js?ver=9.2.1" id="monsterinsights-vue-frontend-js" type="module"></script>

The monsterinsights-vue-frontend script is set with the type text/javascript, likely due to the following reasons:

1. Lack of initial check for type in the script_loader_tag function: The MonsterInsights plugin might explicitly set text/javascript for all scripts if the type was not previously modified. The script_loader_tag function may trigger after the type has already been set.
2. Conflicts with wp_enqueue_script(): If the script is registered with the standard WordPress function wp_enqueue_script() or a similar method without the type="module" attribute, WordPress will automatically apply the text/javascript type.

the monsterinsights-vue-frontend script is registered in google-analytics-premium/includes/frontend/frontend.php using the wp_register_script() and wp_enqueue_script() functions:

wp_register_script( 'monsterinsights-vue-frontend', $frontend_js_url, array( 'wp-i18n' ),  monsterinsights_get_asset_version(), true );
 wp_enqueue_script( 'monsterinsights-vue-frontend' );

It’s important to note that the wp_register_script() and wp_enqueue_script() functions do not set the type attribute, so by default, WordPress adds type="text/javascript".

This second solution:

* Update script tag.
* The vue code needs type=module.
*/
public function script_loader_tag( $tag, $handle, $src ) {

    if ( ! in_array( $handle, $this->own_handles ) ) {
        return $tag;
    }

    // Check if the 'monsterinsights-vue-frontend' script is the target
    if ( 'monsterinsights-vue-frontend' === $handle ) {
    // Remove any existing type attribute
    $tag = str_replace( 'text/javascript', 'module', $tag );
    }

    // Change the script tag by adding type="module" and return it.
    $html = str_replace( '></script>', ' type="module"></script>', $tag );

    $domain = monsterinsights_is_pro_version() ? 'ga-premium' : 'ga-premium';
    $html   = monsterinsights_get_printable_translations( $domain ) . $html;

    return $html;
} 

I hope this helps the development team address this critical issue. Thank you!

Hello. I have too error on Frontend side with this “Import Module”

The error “Uncaught SyntaxError: Cannot use import statement outside a module” occurs when a JavaScript file with import statements is loaded in a context that doesn’t support ES6 module syntax (also known as ECMAScript 2015). This can happen with files like frontend.min.js if they are loaded without specifying the module type.

Subject: JavaScript Module Loading Issue: Uncaught SyntaxError: Cannot use import statement outside a module

Description: I’m encountering an error in frontend.min.js in the plugin directory (/wp-content/plugins/google-analytics-premium/pro/assets/vue). When attempting to load this file, I receive the following error in the console:

javascript

Copy code

Uncaught SyntaxError: Cannot use import statement outside a module (at frontend.min.js?ver=9.2.1:1:1)

Steps to Reproduce:

1. Load the page where frontend.min.js is used.
2. Observe the console error.

Expected Behavior: The JavaScript file should load without errors, and all module imports should be properly handled.

Observed Behavior: The import statements in frontend.min.js are throwing an error because the file is not recognized as a module.

Details: This issue typically occurs when JavaScript files with import statements are loaded without the necessary type="module" attribute, which is required for ES6 modules. Here is a relevant configuration snippet from manifest.json:

You must add script how <script type=”module” but you add him how <script type=”text/javascript”..

When a client downloads files, for example, products for download from WooCommerce, and the file is remote on Google Drive, the browser does not receive the download size. This means that the client is downloading the file with a question mark until the file is fully downloaded and does not see the final file size until the download is complete. This issue occurs because the Content-Length is not passed to the browser, so it does not know the size of the file being downloaded. Is it possible to add a feature that first retrieves the file size from Google Drive and then includes it in the headers during the download? This happens only when the download works directly without redirecting to Google Drive.

Okay

Will try find solution for this

In firefox latest

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://googleads.g.doubleclick.net/pagead/viewthroughconversion/962985656/?backend=innertube&cname=56&cver=20240902&foc_id=aS-igVSTyhIQopJHsWJN_A&label=followon_view&ptype=no_rmkt&random=143700614&cv_attributed=0. (Reason: CORS request did not succeed). Status code: (null).

In opera latest after tap play buttn YouTube

https://ibb.co/Jqd5qr0

This is issues on any website where is YouTube video added via block YouTube Embed Block..

https://heavyocity.com/2-hour-cues-episode-9-writing-a-supervillain-theme/

Installed: PHP 8.3.11 + NGINX + APACHE

WordPress 6.6.1 and Browser Opera 113.0.5230.55

Please add to to filter

// This Allow Lang Tag from XSL
$allowedposttags['html'] = array(
   'lang' => array(),
); 

    <html xmlns="https://www.w3.org/1999/xhtml" lang="en">
        <head>
            <title>XML Sitemap</title>
             <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
              <meta name="description" content="This file was dynamically generated using the WordPress content management system and XML Sitemap Generator for Google by Auctollo." />

This will be resolved BING

WARNING : Meta Language tag missing

What is the issue about?

The page is missing meta language information. The Meta Language information is used as a hint to help us understand the intended language and country/region the page content applies to. This can help if your site is not hosted in the country/region. Use the “content-language” meta tag to embed the culture code in the <head> section of your page. For example, <meta http-equiv=’content-language’ content=’en-gb’> indicates that the page is in English and intended for the the United Kingdom. Alternatively, you can use <html lang=’en-gb’> or <title lang=’en-gb’ />.

THIS IS FIXED VERSION WITH ALL FIXES: XSL + Core.php

Download 4.1.21 Fixed: https://www.transfernow.net/dl/20240807XoPXNMYs

VirusTotal: https://www.virustotal.com/gui/file/b3e298962ffd5db0aad4c05368f63ccf352ba6c8b6de7547784026378a6b0f19?nocache=1

Changes

        $allowedposttags['meta'] = array(
            'name' => array(),
            'content' => array(),
            'http-equiv' => array(),
        );
        $allowedposttags['html'] = array(
            'lang' => array(),
        );

XSL

<html xmlns="https://www.w3.org/1999/xhtml" lang="en"> and <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

                  <meta name="description" content="This file was dynamically generated using the WordPress content management system and XML Sitemap Generator for Google by Auctollo." /><html xmlns="https://www.w3.org/1999/xhtml" lang="en"> and