Edit bar conflict with theme off canvas menu
Permalink
Hi
I seem to have a problem with my custom theme, which uses a cutom off-canvas menu.
When in edit mode, the edit bar is being pushed down and I loose some of it's functionality.
How can I make sure, that my off-canvas menu doesn't conflict with the functionality of the core? I there any best practices?
I seem to have a problem with my custom theme, which uses a cutom off-canvas menu.
When in edit mode, the edit bar is being pushed down and I loose some of it's functionality.
How can I make sure, that my off-canvas menu doesn't conflict with the functionality of the core? I there any best practices?
Hi
Thank you for your reply.
Unfortunately - I've already checked my divs - and it's not what is causing the problem.
Any other suggestions?
Thank you for your reply.
Unfortunately - I've already checked my divs - and it's not what is causing the problem.
Any other suggestions?
Well, I just tried to reconstruct yesterday's issue by removing some div's at the end of the theme. In my case, the down-shift of the toolbar and thus the unaccessibility of the dashboard icons were caused by missing div's.
Sorry, no further ideas ... :/
Sorry, no further ideas ... :/
does this thread help at all?
https://www.concrete5.org/community/forums/themes/top-toolbar-issue/...
https://www.concrete5.org/community/forums/themes/top-toolbar-issue/...
This is what my theme's end looks like. If I remove the last two div's, I get the same issue as in your attachment.
..... your theme's code ....
</footer>
<!-- footer end -->
</div>
</div>
<!-- JavaScript files placed at the end of the document -->
<!-- Jquery and Bootstap core js files -->
<!-- Concrete5 Core Start -->
<?php Loader::element('footer_required')?>
<!-- Concrete5 Core End -->
</body>
</html>
..... your theme's code ....
</footer>
<!-- footer end -->
</div>
</div>
<!-- JavaScript files placed at the end of the document -->
<!-- Jquery and Bootstap core js files -->
<!-- Concrete5 Core Start -->
<?php Loader::element('footer_required')?>
<!-- Concrete5 Core End -->
</body>
</html>
Yes - it did.
Thanks a lot - it was the position of the closing page-wrapper div, that I had wrong.
Thanks again
Thanks a lot - it was the position of the closing page-wrapper div, that I had wrong.
Thanks again
:D
You should probably give "pixeljunkie" the benefit of marking the answer "Best Answer"
Just a thought!
Just a thought!
I ran into the same issue just yesterday, trying to adopt a javascript-packed theme.
Have you checked your div's? After running my theme (with a lot of hardcoded sections) throughhttp://www.tomus.com 's div-checker, I discovere that an end-div was missing (which probably got lost in the course of concretizing the code).
Everthing works just fine now, regardless of some slow-down issues probably due to the javascript-overload.