Forum Replies Created

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter mollyyjane

    (@mollyyjane)

    really appreciate the instruction and the image you provided – they were incredibly helpful.

    I have to admit, I initially overlooked the custom link option within the mobile menu settings, so your guidance was spot-on.

    Thanks to your clear explanation, I’ve been able to successfully add the aria-label to the logo in the Nav Menu widget.

    Thread Starter mollyyjane

    (@mollyyjane)

    Thanks a ton for your help!

    We stumbled across the same issue on our mobile accessibility score (https://pagespeed.web.dev/analysis/https-velvetfiles-com-services/ru91egenmg). Turns out the ‘Jkit-nav-logo’ (div.jkit-menu-wrapper > div.jkit-nav-identity-panel > div.jkit-nav-site-title > a.jkit-nav-logo) element on mobile screens is having the same “Links do not have a discernible name” issue. Looks like it may be missing that aria-label attribute too.

    Any chance you could point me in the right direction for adding the code to this element? I would like to assign an aria-label on the ‘Jkit-nav-logo’, like you did with the Off-Canvas widget.

    It’d be awesome to have both the Off-Canvas and Nav-Logo elements working with accessibility to help maintain our score.

    Thanks again, we really appreciate all your help.

    Thread Starter mollyyjane

    (@mollyyjane)

    Hello,

    I wanted to let you know that I’ve successfully implemented the changes you suggested by replacing the file as instructed. This has resolved the accessibility error and improved my Google Page Speed Insights score as I was hoping.

    I appreciate your commitment to including this change in the next update of Jeg Elementor Kit. It’s great to know that these changes won’t be overwritten next update.

    Thank you for your reply and for providing a solution that worked!

    • This reply was modified 3 months, 2 weeks ago by mollyyjane.
    Thread Starter mollyyjane

    (@mollyyjane)

    Switching to the defualt theme didn’t solve the issue. I’m considering deleting the plug-in and then deleting all data in the phpMyAdmin File Directory and starting over with a fresh install to see if this solves it?

    It’s been difficult to find any support and it seems everyones default solution is always to install defualt theme and remove plug-ins, however I think there is something else going on here. The form’s were submitting correctly on the dev site, but when reassigning the domain to the live site, the functionaility broke somewhere.

    @perryb Not sure why or what could be causing this but I will report back if I do my phpMyAdmin / File Directory method, and let you know if this works.

    Thread Starter mollyyjane

    (@mollyyjane)

    We are currently using BeTheme and only have a couple plugins installed (Contact Form 7, Jetpack, UpdraftPlus – Backup/Restore, and YoastSEO).

    @andybrezz,

    Did you ever figure out a solution? I’m facing the same exact issue and have not been able to figure it out.

    _____________________________________________________________

    Update…. I figured it out, for anyone in the future

    This can be set at the Woocommerce settings page.

    Admin -> Woocommerce -> Settings -> Products -> Inventory

    Its a bit hidden but its there.

    Thread Starter mollyyjane

    (@mollyyjane)

    Correct, we’re still having the same problems even after rolling back to the previous version.

    Thread Starter mollyyjane

    (@mollyyjane)

    @xue28 thanks for your response!

    Are you aware of any other instance it could be outside of the shortcode?

    I would be happy to test the shortcode or WooCommerce Cart/Checkout blocks, however we designed our website using the Elementor Pro Builder on the Hello Elementor theme. We referenced these support articles when designing those pages.

    WooCommerce Checkout Widget
    WooCommerce Cart Widget

    When using the WooCommerce shortcode or Cart/Checkout blocks we are unable to customize the fields and design of these pages to match the brand on the rest of our site.

    The problem when testing the shortcode, is we can’t duplicate the issue (as it doesn’t happen in every instance) and we don’t want to keep the shortcode onsite for an exteneded period and risk these pages staying off brand.

    Do you have any other recommendations to test?

    Below are the fatal error logs we are seeing:

    fatal-errors-2023-01-17-43b8c715530bbc334a49061e95be833a.log 
    2023-01-17T22:21:12+00:00 CRITICAL Uncaught Error: Call to undefined function ElementorPro\Modules\Woocommerce\Widgets\wc_print_notices() in /home1/mollyest/public_html/wp-content/plugins/elementor-pro/modules/woocommerce/widgets/products.php:336
    Stack trace:
    #0 /home1/mollyest/public_html/wp-content/plugins/elementor/includes/base/controls-stack.php(2268): ElementorPro\Modules\Woocommerce\Widgets\Products->render()
    #1 /home1/mollyest/public_html/wp-content/plugins/elementor/includes/base/widget-base.php(609): Elementor\Controls_Stack->render_by_mode()
    #2 /home1/mollyest/public_html/wp-content/plugins/elementor/includes/base/widget-base.php(750): Elementor\Widget_Base->render_content()
    #3 /home1/mollyest/public_html/wp-content/plugins/elementor/includes/base/element-base.php(449): Elementor\Widget_Base->print_content()
    #4 /home1/mollyest/public_html/wp-content/plugins/elementor/includes/base/element-base.php(1354): Elementor\Element_Base->print_element()
    #5 /home1/mollyest/public_html/wp-content/plugins/elementor/includes/base/element-base.php(449): Elementor\Element_Base->print_content()
    #6 /home1/mollyest/public_html/wp-content/plugins/elementor/includes/base/element-base.php(1354): Elementor\Element_Base->print_element()
    #7 /home1/mollyest/public_html/wp-content/plugins/elementor/includes/base/element-base.php(449): Elementor\Element_Base->print_content()
    #8 /home1/mollyest/public_html/wp-content/plugins/elementor/core/base/document.php(1669): Elementor\Element_Base->print_element()
    #9 /home1/mollyest/public_html/wp-content/plugins/elementor/core/base/document.php(1095): Elementor\Core\Base\Document->print_elements(Array)
    #10 /home1/mollyest/public_html/wp-content/plugins/elementor/includes/frontend.php(1153): Elementor\Core\Base\Document->print_elements_with_wrapper(Array)
    #11 /home1/mollyest/public_html/wp-content/plugins/elementor/includes/frontend.php(1048): Elementor\Frontend->get_builder_content(7729)
    #12 /home1/mollyest/public_html/wp-includes/class-wp-hook.php(308): Elementor\Frontend->apply_builder_in_content('<a href="https:...')
    #13 /home1/mollyest/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters('<a href="https:...', Array)
    #14 /home1/mollyest/public_html/wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php(1857): apply_filters('the_content', '<a href="https:...')
    #15 /home1/mollyest/public_html/wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php(384): WP_REST_Posts_Controller->prepare_item_for_response(Object(WP_Post), Object(WP_REST_Request))
    #16 /home1/mollyest/public_html/wp-includes/rest-api/class-wp-rest-server.php(1171): WP_REST_Posts_Controller->get_items(Object(WP_REST_Request))
    #17 /home1/mollyest/public_html/wp-includes/rest-api/class-wp-rest-server.php(1018): WP_REST_Server->respond_to_request(Object(WP_REST_Request), '/wp/v2/pages', Array, NULL)
    #18 /home1/mollyest/public_html/wp-includes/rest-api/class-wp-rest-server.php(442): WP_REST_Server->dispatch(Object(WP_REST_Request))
    #19 /home1/mollyest/public_html/wp-includes/rest-api.php(410): WP_REST_Server->serve_request('/wp/v2/pages')
    #20 /home1/mollyest/public_html/wp-includes/class-wp-hook.php(308): rest_api_loaded(Object(WP))
    #21 /home1/mollyest/public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)
    #22 /home1/mollyest/public_html/wp-includes/plugin.php(565): WP_Hook->do_action(Array)
    #23 /home1/mollyest/public_html/wp-includes/class-wp.php(399): do_action_ref_array('parse_request', Array)
    #24 /home1/mollyest/public_html/wp-includes/class-wp.php(780): WP->parse_request('')
    #25 /home1/mollyest/public_html/wp-includes/functions.php(1332): WP->main('')
    #26 /home1/mollyest/public_html/wp-blog-header.php(16): wp()
    #27 /home1/mollyest/public_html/index.php(17): require('/home1/mollyest...')
    #28 {main}
      thrown in /home1/mollyest/public_html/wp-content/plugins/elementor-pro/modules/woocommerce/widgets/products.php on line 336
    
    log-2023-01-22-ffbf58d53ede722f81f1230ce71312be.log 
    2023-01-22T20:20:33+00:00 CONVERSIOS PRODUCT SYNC LOG  Start auto sync with last_sync_product_id=0
    2023-01-22T20:20:34+00:00 CONVERSIOS PRODUCT SYNC LOG  Auto before product sync API Call for 161 products
    2023-01-22T20:20:37+00:00 CONVERSIOS PRODUCT SYNC LOG  after product sync API Call
    2023-01-22T20:20:37+00:00 CONVERSIOS PRODUCT SYNC LOG  Done and update ee_auto_product_sync_check
    2023-01-22T20:20:37+00:00 CONVERSIOS PRODUCT SYNC LOG  Start auto sync with last_sync_product_id=14
    
    mailchimp_woocommerce-2023-01-06-6cd346b722d0a505ae2bd0c92832d1b8.log
    2023-01-06T17:59:31+00:00 NOTICE action_scheduler.queue_job :: MailChimp_WooCommerce_User_Submit queued :: obj_id 322
    2023-01-06T18:00:40+00:00 NOTICE member.sync :: [email protected] is Pending Double OptIn
    2023-01-06T18:03:29+00:00 NOTICE profile :: user_update_subscribe_status :: Array
    (
        [subscribed] => 
        [user_id] => 322
        [gdpr_fields] => 
    )
    
    2023-01-06T18:03:29+00:00 NOTICE action_scheduler.queue_job :: MailChimp_WooCommerce_User_Submit queued :: obj_id 322
    2023-01-06T18:04:32+00:00 NOTICE member.sync :: Updated Member [email protected] :: Array
    (
        [previous_status] => transactional
        [status] => 
        [language] => 
        [merge_fields] => Array
            (
                [FNAME] => Jess
                [LNAME] => Stephens
            )
    
        [gdpr_fields] => 
    )

    Thanks for your help!

    • This reply was modified 1 year, 9 months ago by mollyyjane.

    Hi there!
    I’m having the exact same issue! I noticed the last time I had a shipping order was Oct. 14, looked into when the Plug-in was updated and it was October 14th at 7:40pm. It has to be on their end! I’ve tried sending in 3 support forums to get help, and NO ONE has responded to me! Any lucky with anything to fix this? I see you said you designed a ‘fallback’ rate? Maybe I should try that for that for now?

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