Feature Request: Always show customtop position

[prophoto]

I use Phoca Top Menu since I hate hate hate the left menu (hate it just as much in Wordpress) but I can fix it with Phoca Top Menu. Can you stop hiding the 'customtop' module position in the admin template? This just started recently.

Akeeba Component screen vs Fabrik. Akeeba doesn't hide customtop.

 

[lori19]

Hi there!

At a quick glance: I think that has more to do with the configuration of the custom menu then with Fabrik. Did you check, if the module customTop is set to "show on all pages"?
I don't think Fabrik is actively hiding some features of Joomla or any other developer makes no sense at all.

Kindly,
Lorenz

 

[prophoto]

Hi there!

At a quick glance: I think that has more to do with the configuration of the custom menu then with Fabrik. Did you check, if the module customTop is set to "show on all pages"?
I don't think Fabrik is actively hiding some features of Joomla or any other developer makes no sense at all.

Kindly,
Lorenz

Where would I find that option? I've never seen a Menu Assignment tab in an administrator module. It shows on all other components. Here's another example.

 

[prophoto]

from /media/com_fabrik/css/fabrik.css line 7.

.collapse:not(.show) {
    display: none !important;
    }

 

[prophoto]

Fixed - Fabrik 4.5 new css hides Cassiopeia menu

Hi, in /media/com_fabrik/css/fabrik.css there are some new lines starting at line 7: .collapse:not(.show) { display: none !important; } The default Cassiopeia menu module, set to "Collapsible dropdown" has a class "collapse" and so it is hidden on pages where a Fabrik list, form or module...

fabrikar.com

 

[elmarra]

Fixed - Fabrik 4.5 new css hides Cassiopeia menu

Hi, in /media/com_fabrik/css/fabrik.css there are some new lines starting at line 7: .collapse:not(.show) { display: none !important; } The default Cassiopeia menu module, set to "Collapsible dropdown" has a class "collapse" and so it is hidden on pages where a Fabrik list, form or module...

fabrikar.com

As I mentioned in the last post.
I fixed and isolated the issue.
And this was available in the next release.
(alternatively in the meantime you can update via Git).
So either do a full update.
Or update this.

Bitbucket

bitbucket.org

And you will see that "your problem" will be solved