Hi,
Glad we were able to help, if you have any further questions please create a new thread and we will gladly try to help you. Thank you for using Enfold.

Best regards,
Mike

Hi,
Sorry, guess I misunderstood.

Best regards,
Mike

Hi,
Sorry for the confusion, I removed the WPCode snippet and enabled the child theme function again.
This is the working solution:

function tab_though_menu_skipping_sub_menu_items_unless_down_or_up_arrow_keys_are_used() { ?>
 <script>
document.addEventListener('DOMContentLoaded', function () {
   const menuItems = document.querySelectorAll('.menu-item-has-children'); // Adjust this selector to match your menu structure

   // Initially set tabIndex to -1 for all sub-menu items to skip them in tab navigation
   menuItems.forEach(item => {
       let subMenuItems = item.querySelectorAll('.sub-menu a'); // Adjust this selector for your sub-menus
       subMenuItems.forEach(subMenuItem => {
           subMenuItem.tabIndex = -1;
       });

       item.addEventListener('keydown', function (e) {
           // Only proceed if the event target is a menu item that contains a sub-menu
           let subMenu;
           if (e.target.classList.contains('menu-item-has-children')) {
               subMenu = e.target.querySelector('.sub-menu'); // Adjust this selector for your sub-menus
           } else {
               // This ensures we get the sub-menu even if a child of the menu item was focused
               subMenu = e.target.closest('.menu-item-has-children').querySelector('.sub-menu');
           }

           let subMenuItems = subMenu.querySelectorAll('a'); // Assumes sub-menu items are anchor tags
           let focusedElement = document.activeElement;
           let currentIndex = Array.from(subMenuItems).indexOf(focusedElement);

           switch(e.key) {
               case 'ArrowDown':
                   // Move focus to the next sub-menu item
                   if (currentIndex < subMenuItems.length - 1) {
                       subMenuItems[currentIndex + 1].tabIndex = 0;
                       subMenuItems[currentIndex + 1].focus();
                       e.preventDefault(); // Prevent scrolling the page
                   } else {
                       // Optionally wrap around to the first item
                       subMenuItems[0].tabIndex = 0;
                       subMenuItems[0].focus();
                       e.preventDefault(); // Prevent scrolling the page
                   }
                   break;
               case 'ArrowUp':
                   // Move focus to the previous sub-menu item
                   if (currentIndex > 0) {
                       subMenuItems[currentIndex - 1].tabIndex = 0;
                       subMenuItems[currentIndex - 1].focus();
                       e.preventDefault(); // Prevent scrolling the page
                   } else {
                       // Optionally wrap around to the last item
                       subMenuItems[subMenuItems.length - 1].tabIndex = 0;
                       subMenuItems[subMenuItems.length - 1].focus();
                       e.preventDefault(); // Prevent scrolling the page
                   }
                   break;
           }

           // Reset tabIndex to -1 for items not focused to ensure they're skipped during tab navigation
           subMenuItems.forEach(subMenuItem => {
               if (subMenuItem !== document.activeElement) {
                   subMenuItem.tabIndex = -1;
               }
           });
       });
   });
});
</script>
 <?php
}
add_action( 'wp_footer', 'tab_though_menu_skipping_sub_menu_items_unless_down_or_up_arrow_keys_are_used', 99 );

Best regards,
Mike

Hi,
Glad Ismael could help, if you have any further questions please create a new thread and we will gladly try to help you. Thank you for using Enfold.

Best regards,
Mike

Hi,
If you want the circles to be larger on mobile try changing the height & width from 15px to 30px like this:

@media only screen and (max-width: 767px) { 
.color-circle::before {
    content: '';
    display: inline-block;
    width: 30px;
    height: 30px;
    border-radius: 50%;
    margin-right: 2px;
    margin-left: 3px;
    margin-bottom: -1px;
    position: relative;
}
}

Or adjust somewhere in the middle to suit your needs.

Best regards,
Mike

Hi,
Glad that this helped, in some cases Autoptimize works ok, if your client is not having trouble then go ahead and use it, but if you notice trouble in the future try disabling Autoptimize first.
Unless there is anything else we can assist with on this issue, shall we close this thread then?

Best regards,
Mike

Hi,
Glad we were able to help, if you have any further questions please create a new thread and we will gladly try to help you. Thank you for using Enfold.

Best regards,
Mike

Hi,
Glad Ismael could help, if you have any further questions please create a new thread and we will gladly try to help you. Thank you for using Enfold.

Best regards,
Mike

Hi,
Oh, I misunderstood, I thought that you were saying that the plugin was causing the admin-ajax.php 403 (Forbidden) error. Perhaps disabling it along with your other plugins would be a good test. I note in your log above there are a few errors for the gravityforms plugin as it has exhausted the memory size
It also looks like you downgraded your PHP to v7.3.33, I thought before you were using v7.4?
Perhaps your plugins require v8, have you tried that?

Best regards,
Mike

Hi,
Glad to hear that you have sorted this out, I don’t see anything specific that stands out in the log the you posted.
What is the name of the custom login plugin that you were using?

Best regards,
Mike

Hi,
We still are not allowed

Best regards,
Mike

Hi,
If you are still getting the admin-ajax.php 403 (Forbidden) then try the common fixes, and if that doesn’t help then check with your webhost if they can see a cause in your error logs.
I see now your custom login url is a 404 as well as the standard WP login url, and it makes me think that perhaps this customization is breaking how the backend admin-ajax.php is being called or loaded. Try disabling this customization. Perhaps the key is in what is different with this install and the others that don’t have an issue, are that all on the same server, same plugins and customization, etc. There is probably something small and different that is causing this.

Best regards,
Mike

Hi,
Thanks for the login, but unfortunately we get a “forbidden” error so we can not login.
I see on your page that you have some random “P” tags and “br” between the elements, did you also edit or open the page with a difference editor such as the Block Editor?
Please note that when you create a page with the Advanced Layout Builder you should not edit it with any other editor.
So now you could try Enabling the Avia Layout Builder Debugger and try to remove the random “P” tags and “br” between the elements. If you have trouble with this then try to allow us to login to your site, otherwise you may need to create a new page and only use the Advanced Layout Builder to edit it.

Best regards,
Mike

Hi,
I’m not seeing a top margin for the first .flex_column_table, only after the first one. Are you hiding the first one with some custom css? Please link to your page so we can examine, perhaps you have a different issue.
The latest version is now v5.6.10

Best regards,
Mike

Hi,
Thank you for your patience and the link to your site, I notice in your WordPress ▸ Dashboard ▸ Tools ▸ Site Health ▸ Info ▸ Server that your PHP max input variables is set to 4000, please try changing to 10000
Also try setting your Max input time to 120 and your PHP memory limit to 768M
Perhaps uping your WordPress Constants WP_MEMORY_LIMIT to 64M and changing your Database Max connections from 300 to 1000 will also help. These are the settings that I see are different between your site and my test site.
When I checked your homepage I saw the error: admin-ajax.php 403 (Forbidden) this can be caused by many issues, such as if mod_security is enabled on the server, try asking your webhost if it is, and to disable it as a test. It could also be caused by incorrect file permissions or a Corrupt .htaccess file. Please see this article for common fixes.

Best regards,
Mike