Skip Navigation

[Resolved] Mega menu JupiterX not show into custom post type

This support ticket is created 4 years, 6 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 -
- 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 -

Supporter timezone: Europe/London (GMT+00:00)

This topic contains 19 replies, has 2 voices.

Last updated by Nigel 4 years, 2 months ago.

Assisted by: Nigel.

Author
Posts
#1639579

Hi,
i created mega menu but this not show into my custom post type created with toolset.
How can i fix?
Regards

#1639673

The problem show only with set custom model template.
If not set the model i show the mega menu.
Regards

#1639959

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Could I take a look at your site and see how the mega menu is set up?

I have the Jupiter theme but I think it may be different with the Jupiter X theme.

Let me set up a private reply to get site credentials from you.

Please provide whatever details I need to see the issue with the menu.

#1640027

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

standard posts.png
associato post.png

When I visit standard blog posts and the custom posts on the front-end I can see that with the standard posts the header includes various "mega" widgets but with the associato posts that have a content template assigned those are not included.

That is odd, because the Toolset content templates only affect the content part of the page and have nothing to do with the header.

It only happens when the content template is assigned to the post type, not otherwise.

I'm taking a copy of your site to intall locally where I can debug this.

It make take a little time so please bear with me, I'll let you know when I have found something.

#1640047

Thanks! 🙂

#1642969

Hi Nigel,
do you have good news?

#1643795

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

I've completed some extensive testing and am now passing my findings on to the compatibility team for them to pursue further.

They should be able to determine whether it is something we can fix ourselves, or whether we need to collaborate with JetPlugins to produce a fix.

I don't have a workaround, I'm afraid.

I'll let you know when I have some feedback from my colleagues to share.

#1644133

Ok, thanks for all!

#1651299

Hi Nigel,
do you have good news?

#1651359

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Well, I can see from the internal tickets that the compatibility team have identified somewhere within our code where we may be able to fix the issue, and that has been passed on to the relevant developer. It is still in progress, but is included in the current development board which means that a fix can hopefully be included by the time of the next release of Views/Blocks.

I don't have an ETA for that, though, I'm afraid.

#1666359

Hi, i see Toolset Layouts and Types update.
Do you fix the problem?

#1666481

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

No, the affected product is Blocks (or Views), yesterday's updates are not related.

The internal ticket is still on the board for the current dev cycle although it is not fixed yet. I've left a comment reminding them that you are awaiting a fix.

#1669817

Thanks. Also because I should publish the site.
If you can give me an ETA it would be fantastic.
Regards

#1672007

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Unfortunately I don't have one, but looking at the notes from the tester in the compatibility team they proposed a minor change in our code to resolve the problem.

It needs to go through the developers to confirm the solution is suitable, and I'm not sure when they will do that.

But in the meantime I've prepared a patched version of the affected file, which you can download a zip of here: hidden link

You'll need to use FTP to overwrite the existing file at wp-content/plugins/wp-views/application/controller/compatibility/elementor.php

But please note this hasn't been tested, so I can't say for sure that it won't have any side-effects.

So only update the file once you have a current backup, and then do some general testing of pages where Toolset and Elementor may overlap to see they still function okay.

Let me know how you get on.

#1672197

Hi Nigel,
super!

The file works 😉