Zakra Pro (Developer Lifetime) support halted?
-
I’ve submitted the same bug (mobile submenu opening issue) twice in the past week using the Pro support channel. No acknowledgement or response of any kinda has been seen. Is support no longer available to Pro owners?
Anyone else struggling with the same problem? After troubleshooting this with Claude, I had it write the following summary of the bug report, to try to codify the information succinctly.Bug Report: Mobile Nav — Clicking SERVICES Text Opens ABOUT US Submenu
Site URL: https://wolff-staging.qgs58musbz-ypj68nne96l2.p.temp-site.link/
Theme: Zakra Pro
Active Plugins: Zakra Pro only (all others disabled to isolate issue)
Device: Mobile (reproduced on iOS and/or Android browsers and desktop Firefox in Mobile form factor)Description
In the mobile hamburger navigation, the SERVICES top-level menu item behaves incorrectly when its text label is tapped:
- Tapping the down-caret (▾) icon next to SERVICES → correctly expands the SERVICES submenu ✓
- Tapping the SERVICES text label → incorrectly expands the ABOUT US submenu ✗
- Tapping the ABOUT US text label → correctly expands the ABOUT US submenu ✓
In other words, tapping the text of the first
menu-item-has-childrenitem (SERVICES) triggers the submenu of the secondmenu-item-has-childrenitem (ABOUT US), suggesting an off-by-one index error in the click handler that maps anchor elements to their corresponding submenu containers.Steps to Reproduce
- Open https://wolff-staging.qgs58musbz-ypj68nne96l2.p.temp-site.link/ on a mobile device (or narrow desktop browser to mobile breakpoint)
- Tap the hamburger menu icon to open the nav
- Tap the word “SERVICES” (not the caret icon)
- Observe: the ABOUT US submenu expands instead of the SERVICES submenu
Expected Behavior
Tapping the SERVICES text label should expand the SERVICES submenu, consistent with the behavior of the caret icon.
Suspected Cause
The mobile nav click handler attached to
menu-item-has-children > aelements appears to use an index-based lookup to find the target submenu container, rather than traversing the DOM relative to the clicked element (e.g., via.closest()or.parentNode). Because Zakra renders the menu twice in the DOM (desktop + mobile), the index of SERVICES in the mobile menu is offset from its index in the full NodeList, causing it to resolve to the wrong submenu.The page I need help with: [log in to see the link]
-
I did some troubleshooting with Claude, because this was outside of my wheelhouse (having not hacked around in Zakra’s menu system myself). It felt it identified an issue (see Suspected Cause) and some trial and error debugging led to a code snippet which I have temporarily installed to try to avert the issue while waiting for Zakra support to respond. Hopefully it may help some others.
The broken version is still on the staging site (link in original post) so Zakra support can look at it if/when they get around to it. I can’t seem to get the code to paste here, so here’s a link to it
https://pastebin.com/zfK0wqH6Hi @xenonofarcticus,
Please note that this forum is dedicated only to the free version of the Zakra theme. We’re unable to assist with Zakra Pro or license-related concerns here, as this falls outside the ww.wp.xz.cn support forum guidelines.
To receive proper assistance, we kindly recommend reaching out to our official Zakra support team through our website. You can use the live chat option there, which is the fastest way to get help with Pro-related queries.
Support Page: https://zakratheme.com/support/
When contacting the team, please include the link to your forum thread so they can review your concern with full context: https://ww.wp.xz.cn/support/topic/zakra-pro-developer-lifetime-support-halted/
Best Regards!
You must be logged in to reply to this topic.
