• Resolved BackuPs

    (@neo2k23)


    I am getting a error in the js console after closing the Elementor One Message

    Uncaught TypeError: $(…).pointer is not a function

    I had to edit the file editor-one-pointer.php and remove the script to get rid of the error message. Using WP 7.0 Beta


    I remove this code from the file mentioned.

        <script>
            jQuery( document ).ready( function( $ ) {
                setTimeout( function () {
                    function markIntroductionAsViewed( redirectUrl ) {
                        elementorCommon.ajax.addRequest( 'introduction_viewed', {
                            data: {
                                introductionKey: '<?php echo esc_attr( self::CURRENT_POINTER_SLUG ); ?>',
                            },
                            success: function() {
                                if ( redirectUrl ) {
                                    window.location.href = redirectUrl;
                                }
                            }
                        } );
                    }
    
                    $( '<?php echo esc_js( $pointer_element_selector ); ?>' ).pointer( {
                        content: <?php echo wp_json_encode( $pointer_content ); ?>,
                        position: {
                            edge: 'top',
                            align: 'left',
                            at: 'left+20 bottom',
                            my: 'left top'
                        },
                        close: function() {
                            markIntroductionAsViewed();
                        }
                    } ).pointer( 'open' );
    
                    $( document ).on( 'click', '.elementor-editor-one-pointer-got-it', function( e ) {
                        e.preventDefault();
                        markIntroductionAsViewed( '<?php echo esc_url( $got_it_url ); ?>' );
                    } );
                }, 10 );
            } );
        </script>



    Please fix. Thank you

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Support Milos

    (@miloss84)

    Hi,

    Thank you for you great feedback,

    Since you are an Elementor One user, you can open a support ticket at my.elementor.com ref: https://elementor.com/help/how-to-submit-a-support-ticket/ I’d also suggest you check out Elementor Community Group on Facebook.

    We have created it to connect Elementor users together and share knowledge, Global Elementor Community.

    WordPress.org rules state that commercial products are not supported here.

    Thread Starter BackuPs

    (@neo2k23)

    I am sorry but i am not a elementor one user. I dont even have any idea what elementor ONE means. I am using elementor free and got a message in the top of my admin area about the elementor menu which has been moved. I closed the message and now i get this js error. Anyway i will try and see how i get this in your support forum. Have a good day

    This problem exists in the free version of Elementor and I found it on my sites as well. Please fix this error, do not redirect me to other support or forums, thanks.

    Thread Starter BackuPs

    (@neo2k23)

    @deepwaterpixel. I did not take any further action by contacting them. It happens in 3 websites using the elementor free plugin & wp 7.0 beta or wp 6.9.4. If if i setup a clean new wp website. It starts after closing a popup message about elementor one in the admin area. For now i adjust the file as mentioned before to get rid of the js error. I guess more users with this issue will start reporting this.

    Good, you should not have gone anywhere else — they have an obligation to provide support here in the plugin repository for their free plugin, based on the very policy they so glibly referenced when stating (erroneously and hilariously confidently) that you were an Elementor One user. If they do not wish to provide that support here by incorrectly routing to their support system, well, as taken from the Developer Expectations section of the policy linked above: “Auto-replies and emails that route to a support system are not permitted as they historically prevent humans from addressing emails in a timely fashion.”

    Applicable remedies as detailed by that policy are:

    • disable or remove any plugin from the directory, even for reasons not explicitly covered by the guidelines.
    • remove developer access to a plugin in lieu of a new, active, developer.
    • make changes to a plugin, without developer consent, in the interest of public safety.

    So, WordPress can fix this for us by removing the plugin, removing Elementor’s developer access, or amending the plugin themselves to remove this error.

    Elementor is allowed to promote their paid features, but critically, they are not allowed to degrade the free experience while doing said promotion. The squeaky wheel gets the grease so I made sure to +1 on this and confirm this is a free plugin problem.

    What irritates me the most about this is the immediate assumption that because it was their promotional section causing this issue, that you must be a paid user, based on essentially zero work on their end to make that determination. It’s very concerning and smacks of “just touch the ticket” quantity over quality. I will wax poetic about this every time I see it because it’s a symptom of a much worse state of affairs and that is to monetize to no end.

    Every company can’t have every dollar. If they want to use the plugin repo as a means to get people using the product for free so they’re willing to pay for Pro, then they need to follow the rules like everyone else.

    Thread Starter BackuPs

    (@neo2k23)

    @deepwaterpixel if you have access to your sql database. In the meta data there is a variable called ‘elementor_introduction’ change its value from f.e.

    a:1:{s:27:”ai-get-started-announcement”;b:1;}

    to

    a:2:{s:27:”ai-get-started-announcement”;b:1;s:27:”e-editor-one-notice-pointer”;b:1;}

    Some how the s:27:”e-editor-one-notice-pointer”;b:1; is not added when you click away the message. This way you do not need to edit the file anymore on every elementor update.

    Make sure to increase a1: to a2: or a5: to a6: and add s:27:”e-editor-one-notice-pointer”;b:1; at the end just before the last closing bracket }

    F.e. change

    a:5:{s:27:”ai-get-started-announcement”;b:1;s:7:”exit_to”;b:1;s:34:”ai_promotion_introduction_textarea”;b:1;s:20:”globals_introduction”;b:1;s:28:”yoast-introduction-editor-v2″;b:1;}

    to

    a:6:{s:27:”ai-get-started-announcement”;b:1;s:7:”exit_to”;b:1;s:34:”ai_promotion_introduction_textarea”;b:1;s:20:”globals_introduction”;b:1;s:28:”yoast-introduction-editor-v2″;b:1;s:27:”e-editor-one-notice-pointer”;b:1;}

    Plugin Support Milos

    (@miloss84)

    Hi there,

    Thank you for contact us again.

    If you would like assistance with these kinds of issues, I advise you to visit our GitHub page on http://www.github.com/elementor and submit this query to our developers as they will be able to assist in the best possible way and/or give you advice on how this can be handled.

    Kind regards,

    Thread Starter BackuPs

    (@neo2k23)

    @miloss84 I am sorry but after 5 weeks you reply to us to post the issue on github? Why close the issue in the first place by assuming that one is using elementor one or using the commercial version? (which is not the case). This happens often when replies here are given by you. Stating that people are using the commercial version of your product and closing the issue. I can not appreciate such. Let me confirm again: I do NOT use elementor PRO! I have this issue in a clean wp install with elementor free and clicking away a message about elementor one that pops up above the elementor settings in the admin area.

    What is the use of the elementor support here on wordpress?

    Note: I already fixed my issues by editing the database and get rid of the $pointer fatal js error. I applied the same fix already in many other websites for people asking how to fix this. So to me this has no priority anymore. Reporting the issue was to point out to elementor that there is a issue which others also will experience. It is up to you to pick it up and deal with it.

    (re)Creating the issue has been described in the reporting here. I will refrain from reporting any future issues i run upon with the free plugin as i am very dissatisfied on how things are handled. here

    Have a great day and thank you for the support.

    @miloss84 I am sorry, but that is an unacceptable response. We are not obligated to submit issues to your GitHub, it is you who is obligated to provide support for issues in your free plugins, right here.

    This query is submitted in the correct location, the problem has been well-defined and the solution has basically been handed to you. Ignoring this is very discouraging to the spirit of community engagement here in the support forums, as you are being given this information for free to improve your product. As stated by @neo2k23 , it is unlikely they will report any further issues they find to you here, as clearly outlined by policy.

    While this does not seem important to Elementor, it constitutes a violation of the WordPress Plugin Repository Policy, and I have reported this plugin for violating it and have referenced this thread in my report.

    Thread Starter BackuPs

    (@neo2k23)

    @deepwaterpixel Thank you for your reply,

    i wrote a small php code to fix the issue.

    if ( is_user_logged_in() ){
        if ( current_user_can( 'manage_options' ) ) {
            $elementor_introduction = get_user_meta(get_current_user_id(), 'elementor_introduction', true);
    
            if ( is_array ( $elementor_introduction)) {
                if ( !isset($elementor_introduction['e-editor-one-notice-pointer'] ) ) {
                    $elementor_introduction['e-editor-one-notice-pointer'] = true;
                     update_user_meta( get_current_user_id(), 'elementor_introduction', $elementor_introduction );
                } 
            } else {
                $elementor_introduction = array();
                $elementor_introduction['e-editor-one-notice-pointer'] = true;
                update_user_meta( get_current_user_id(), 'elementor_introduction', $elementor_introduction );
            }
        }
    }

    Make sure you are logged in and add the code above to the theme functions.php. Reload the admin area page or frontpage or the website . It sets the propper value in elementor_introduction variable in the wp user meta data and the error will go away. After refreshing the admin area just once or loading the frontpage the code in the functions.php can be removed.

    You don’t need phpmyadmin and edit hardcoded the field in the database.

    Note you need to do this per logged in user as the error popsup on a user base! So if another user logs in the error is back. You need to run the code for that user also. Or just leave the code in the functions.php for a while.

    If you dont want to login as each user, login as a admin and run the script below. It will walk through all users and set the variable in elementor_introduction for the admin users and thus removing the js fatal message. After you reload the admin area or the front page just once the script has ran and you can remove the code snippet as all related usermeta are adjusted so the error stays away. Btw the error only appears on admin users.


    if ( is_user_logged_in() ){
        if ( current_user_can( 'manage_options' ) ) {
            $users = get_users();
            foreach ( $users as $user ) {
    
                if ( user_can($user, 'manage_options') ) {
                    $elementor_introduction = get_user_meta($user->ID, 'elementor_introduction', true);
                    if ( is_array ( $elementor_introduction)) {
                        if ( !isset($elementor_introduction['e-editor-one-notice-pointer'] ) ) {
                            $elementor_introduction['e-editor-one-notice-pointer'] = true;
                             update_user_meta( $user->ID, 'elementor_introduction', $elementor_introduction );
                        } 
                    } else {
                        $elementor_introduction = array();
                        $elementor_introduction['e-editor-one-notice-pointer'] = true;
                        update_user_meta( $user->ID, 'elementor_introduction', $elementor_introduction );
                    }
    
                }   
            }
        }
    }


    Plugin Support Milos

    (@miloss84)

    Hi,

    Thank you for your detailed response and for taking the time to clarify everything so thoroughly.

    First, I want to sincerely apologize for the overall experience you’ve had here. I completely understand how frustrating this situation must have been, especially given the delay in our reply and how the previous response came across.

    I’m also sorry for the confusion regarding Elementor One. I understand why that assumption felt incorrect and frustrating in your case, particularly since you clearly mentioned this was happening on a clean WordPress installation using Elementor Free. Thank you for pointing that out and clarifying it again.

    Additionally, I want to apologize for the time it took to respond. Receiving a reply after several weeks that doesn’t fully address the original report is understandably disappointing, and I’m sorry for that experience.

    I really appreciate you taking the time not only to report the issue, but also to investigate it on your side and share your findings. The details you provided about the $pointer fatal JS error, along with the workaround you applied across multiple sites, are very valuable even if the issue is no longer affecting you directly.

    I’ve shared your report and findings with our senior team so they can take a closer and more detailed look at this behavior, particularly the Elementor One notice and how it interacts with the admin area. Your input helps us better understand potential edge cases that may affect other users as well.

    I’m also truly sorry to hear that this experience has left you feeling discouraged from reporting issues in the future. That’s definitely not the experience we aim to provide, and your feedback here is important for us to improve both our response time and the way we handle similar cases.

    Thank you again for bringing this to our attention and for the effort you put into documenting and resolving it.

    Kind regards,

Viewing 11 replies - 1 through 11 (of 11 total)

You must be logged in to reply to this topic.