Accordion and Tabs Compatibility Issues with VisualComposer

Hello,

For the testing, please try to switch to any default theme like twenty-twenty and check if it is working well or facing the same issue.

And let us know what version of the theme and Ocean extra plugin are you using?

I switched to Twenty-Twenty theme and Visual Comoposer starter theme and the accordions and tabs worked fine with them.

I have the OceanWP Theme v3.07 and the latest updated Ocean Extra plugin.

• This reply was modified 3 years, 4 months ago by mezpow.
• This reply was modified 3 years, 4 months ago by mezpow.

Hello any update on next steps in being able to resolve this issue?

Hello,

Sorry but I’m unable to replicate the issue. I would request you to kindly open a ticket at the helpdesk with the details of the staging site.
And I will pass the issue to the dev team.
https://docs.oceanwp.org/article/762-how-can-i-get-support

Thanks, how do I open a helpdesk ticket? I am using the free theme but I assume this is something that needs to be fixed as the issue with accordian tabs only occurs on this theme.

Got your ticket and reverted on that.

Team,

We can reproduce the issue. When using OceanWP in addition to WPVC, if you change the name of the anchor tags on the accordion sections, it breaks the accordion – and though the viewport moves to the location of the anchor tag, it doesn’t appear in the address bar, nor does it expand the section.

See here in this staging area: https://staging.elkrapids.org/wp56/_test-accordion-page/#beautification-commission

Adding the anchor tag manually will reload the page with the section expanded.

@mezpow Please do not permit anyone to access your site such as with any login.

@oceanwp If your support staff is sending users from here to your site to bypass the prohibition on logging into a user’s site then plugins and themes on this site may be closed.

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.