uiSub menu Mobile on click

Hi I have supplied the login details to the email provided. I was wondering if you have managed to debug this issue.

If you could let me know.

Thanks

• This reply was modified 5 years ago by davidchapman1.

Hi thanks for getting back.

I did send an email with the login details on the 20th Feb. The email title is “uiSub menu Mobile on click”.

If you could check again or your junk that would be great. I have also send it agin today.

Thanks

Hi David,

In the following javascript file, which is part of your website’s theme.

https://new-staging.proinsight.org/wp-content/themes/xclean/js/main-script.js?ver=5.3.2

There are the following codes which will act on mobile menu link.

/*=============================================
= Mobile menu accordion =
=============================================*/

if( $( window ).width() < 767 ) {
$( ‘.menu-item-has-children>a’ ).click( function( e ) {
e.preventDefault();
if ( $( this ).parent( ‘li’ ).hasClass( ‘active’ ) ) {
$( this ).parent( ‘li’).removeClass( ‘active’ );
$( this ).parent( ‘li’ ).children( ‘ul’ ).slideUp( ‘normal’ );
} else {
$( this ).parent( ‘li’ ).addClass( ‘active’ );
$( this ).parent( ‘li’ ).children( ‘ul’ ).slideDown( ‘normal’ );
}
} );
}
/*===== End of Mobile menu accordion ======*/

The code will apply to a “menu item that has children”.

The e.preventDefault code is to stop the link from going to it’s destination.

This is why in mobile, this user is not able to activate the top menu link when there are sub menu links within it.

Removing this block of code should fix the issue.

Follow by clearing any cache plugin or server cache as well as browser history, so as to allow the changes to show up on website.

If the problem is not fixed after removing the above mention block of codes, we request you to do a plugin or theme conflict check.

To do this, try disabling all the plugins at once and then enable them one by one by checking which one is causing the conflict. If this doesn’t resolves the problem, try switching to a wordpress theme on your website to check if the theme is causing the conflict or not.

Kind regards,
Kriti

Hi

Thanks for taking a look into this. I know form the result this is not an issue you needed to debug, as its not an issue with your plugin.

This has worked. I should have found this myself.

Thanks again

I am glad that you are now satisfied.

Regards,
Kriti

@expresstechsupport I have archived your reply and temporarily flagged your account for moderation. That means your posts and replies will need to be approved before anyone else can see them. @ notifications from your account will not work.

While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.

If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.

Thankfully are other ways to get information you need:

• Ask the user to install the Health Check plugin and get the data that way.
• Ask for a link to the https://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
• Ask the user to create and post a link to their phpinfo(); output.
• Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
• Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site vistors).
• Ask the user for the step-by-step directions on how they can reproduce the problem.

You get the idea.

We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.

When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.