dklemmt / contao_dk_mmenu Goto Github PK

Hello Dirk,

it would be great to use your extension with 4.4.x Contao version. Could you update the dependencies, please? Thank you.

Best wishes, Jan

Super wäre wenn die AddOns auch verwendet werden könnten ;)
http://mmenu.frebsite.nl/documentation/addons/fixed-elements.html
Eventuell eine Checkbox im Backend und ein Textfeld um die Klassen einzutragen.

Ok. Du hast die AddOns mit gegeben 👍
Zwar die alte Version. Aber klappt alles.

I need to add some small flag images inside this menu. How can I create in contao?

Hallo, habe heute die extension bei einer größeren Seite eingebaut und nach einem Lighthouse/web.dev Test ging der score fast in jedem Bereich runter.

Links to cross-origin destinations are unsafe
Im nav-Template fehlt <?= $item['rel'] ?> aus dem Standard-Contao-Template, somit wird den target="_blank" Seiten kein rel="noopener" übergeben.

Links are not crawlable
Das erste Element oben im Menü mit dem Namen "Menü" ist ein Link ohne funktion, hier meckert der Test. Hier könnte man bei diesem ersten Element den <a class="mm-navbar__title"></a> Tag entfernen und einfach <span>Menü</span> lassen. Leider kann ich das in keinem Template finden/ändern. Hier geht z. B. der score nur wegen diesen einen "Fehler" von 100 auf 92.

Eliminate render-blocking resources
Besteht die Möglichkeit, das die scripte in den Body-Tag per default kommen, ohne es manuell umschreiben zu müssen?

Ich habe auf meiner Seite das mmenu eingebaut. Immer wenn ich eine neue Unterseite aufrufe blinkt das mmenu kurz auf.
Kann man hier etwas dagegen machen? Z.b. per inline css etwas direkt ins Dokument schreiben?

Beim laden tritt das mmenu Kurz in Erscheinung (ohne Stylesheets), bevor das Stylesheet greift.

Meine Lösung war es, den Stylesheet inline in den Head zu schreiben:

<style>#menu-mobile:not(.mm-menu) {
    display: none;
}
</style>

Kann man das nicht auch automatisch machen, da das scheinbar immer (unabhängig von den Einstellungen) auftritt?

Es gibt auch hierzu ähnliche Issues: https://github.com/FrDH/mmenu-js/issues/51

Read more here: contao-bootstrap/layout#12

Im Template mod_mmenuHtml.html5 und mod_mmenuCustom.html5 hat sich ein Fehler eingeschlichen.

müsste

lauten.

Ich habe die aktuelle Erweiterung 3.1.0 in eine Contao 4.8.7

Hier tritt evtl ein Fehler auf.
Wird eine Seite mit Unterseiten zur aktiven Seite verschwindet der Hinweis auf die Untermenüs.
Ist diese dann aktiv, gibt es keine Verlinkung mehr zur Unterseite.

MfG
Mark

Sorry--- Anwenderfehler

Version 1.5.1 build 7 on Contao 3.5.6 throws Error in firebug console

TabSources.prototype._fetchSourceMap threw an exception: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data
Stack: SourceMapConsumer@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/sourcemap/source-map.js:1281:20
TabSources.prototype._fetchSourceMap/fetching<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/utils/TabSources.js:435:19
Handler.prototype.process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:934:23
this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:813:7
this.PromiseWalker.scheduleWalkerLoop/<@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:747:1
EventLoop.prototype.enter@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/script.js:347:5
ThreadActor.prototype.unsafeSynchronize@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/script.js:1085:7
ThreadActor.prototype._addSource@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/script.js:1945:1
ThreadActor.prototype.onNewScript@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/script.js:1892:5
DynamicSourceCollector.prototype.onNewScript@chrome://firebug/content/debugger/script/sourceTool.js:407:1
Line: 1281, column: 20
resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/DevToolsUtils.js
Line 62

Ahoi :)

Das Original-Plugin spricht noch statt als aktiven Menüpunkt an.

Hammer.js SourceMap is not available.
GET http://website.de/assets/js/hammer.min.map 404 (Not Found)
I suggest to remove the last line in assets/js/hammer.min.js

Bei Verwendung mit Contao 4 wird im Sliding-off-canvas-Menü der aktuelle Hauptmenüpunkt nicht generiert, wenn es gleichzeitig der aktive Menüpunkt ist.
Zuoberst wird vom Script zwar ein li.mm-subtitle mit einem darin enthaltenen a.mm-subclose generiert, dieses Element bleibt aber leer.
Offenbar mag das Script nicht die neuen strong-Elemente in Contaos nav_default-Template. Ersetzt man die strong-Elemente im Template durch span-Elemente (wie in älteren Contao-Versionen), wird das das Sliding-Menü korrekt erzeugt.
Lösungsmöglichkeit 1: Die Erweiterung müsste ein eigenes nav-Template mitliefern.
Lösungsmöglichkeit 2: Das Script müsste so erweitert werden, dass es auch den Inhalt der strong-Elemente erkennt.

Hallöchen,

ich habe eine Contao 3.2-Installation auf 3.5 hoch gezogen und dabei auch das dk_mmenu von der legacy-Version auf die aktuelle Composer-Version upgedatet.

Im Frontend gibts jetzt aber immer den Fehler:

Warning: filemtime(): stat failed for /www/htdocs/.../websites/layerbylayer.de/system/modules/dk_mmenu/assets/vendor/mmenu/extensions/jquery.mmenu.fullscreen.css in system/modules/core/library/Contao/Controller.php on line 799

und

Fatal error: Uncaught exception Exception with message File system/modules/dk_mmenu/assets/vendor/mmenu/extensions/jquery.mmenu.fullscreen.css does not exist thrown in system/modules/core/library/Contao/Combiner.php on line 134

Die Datei jquery.mmenu.fullscreen.css ist im Modul vorhanden, allerdings im Unterordner "fullscreen". Wenn ich sie dort raus kopiere und direkt unter "extensions" lege, ist der Fehler zwar weg, aber schön ist das ja nicht. :-D

Liegt ein Fehler in der Erweiterung vor oder ist das ein Überbleibsel vom Update? Habe aber sämtliche Caches und auch die beiden Modul-Ordner selbst (in system und in composer) gelöscht und durch den Composer neu runterladen lassen.

LG
Nicole

Does not work on Contao 3.3.5

I'm trying to get on work On-Canvas Option for Contao 4.4 mmenu-Plugin. Unfortunately it not works with

<script type="text/javascript">
  $(document).ready(function() {
      $("#mmenu").mmenu({
          offCanvas: true;
      });
  });
</script>

Do have any idea how to solve this?

Is that right that if there are a bit more list-items in level_2 list, there is no option to swipe up in mobile view to see the whole level_2 menu-items? How can I fix it? Swiping level_2 menu is not working.

Hi,

ist eine Version für Contao 4.x in naher Zukunft geplant?

In den Einstellungen bewirkt die Einstellung "Art des Menüs" nichts. Egal ob vertikal oder horizontal gewählt wurde, fliegen die Submenüpunkte immer von rechts hinein.

Getestet auf Contao 4.4.16

Ist eine Umstellung auf die neue Version mmenu.js ohne JQuery in Planung?
https://mmenujs.com/whats-new.html

Hallo Fritz,

mir ist noch aufgefallen, dass das Einblenden der Navigation dazu führt, dass die Scrollbar ausgeblendet wird und die Seiten daher ein wenig "springen", wenn Sie bereits eine Scrollbar haben.

Konkret hängt das vermutlich mit folgender Anweisung zusammen:

.mm-wrapper_blocking body { overflow: hidden; }

die beim Öffnen des Menüs greift.
Ändert man das auf:

overflow:scroll;

verschwindet das Springen.
Ich hab jetzt aber nicht getestet, ob das irgendwelche anderen Side-Effekte bei Seiten hat, die generell keine Scrollbar haben / brauchen.

Beste Grüße
Sares

Hi,

There is a conflict with the patch (dk_mmenu.css) and the "front" position.

We need to keep the value of 0 for the margin.

A solution is to add :

html.mm-front.mm-opening .mm-page
    {
        margin: 0 !important;
    }

in dk_mmenu.css or make a test and does not include the css file if the "front" position is used...

Hi,
I have navigation with anchors (one-page), and until responsive version, everything working normally. But the problem are mmenu items.
I use followed way for anchor menu:
-create a Contao page with external redirection to the main page and anchor link ({{link_url::2}}#anchor)
-create an anchor for each item (#anchor)
Usually this wan working normal, but now I have a problem with death links. Each anchor link not working anymore.
I tried also with full path, without tags (example: https://github.com/#anchor), but in this case, anchor links working, but main links not working.
Anybody any suggestion?
Thank you

Ich wollte fragen ob es generell möglich ist in das Menü-Template die "navbars" zu integrieren, da ich einen Header und Footer in dem Menü benötige.

"navbars": [ { "position": "top" }, { "position": "bottom", "content": [ "<a class='fa fa-envelope' href='#/'></a>", "<a class='fa fa-twitter' href='#/'></a>", "<a class='fa fa-facebook' href='#/'></a>" ] } ] });

Viele Grüße,
operatorone

Hi,
I wrote yesterday about this problem and meant that the problem was Contao core. But today, I have the same problem with another website.
I created external link's for some pages, and for this external link's added anchor links. ({{link_url::2}}#anchor) This is my usual way for internal anchor menu items.
All this normally working on desktop navigation, but with mmenu some links not working. For example, when I want open anchor link from another web page (contact, impressum, etc.), anchor link not working. Everything's OK on the main web page, where is anchor link, bot the problem is only when I try open anchor from another page.
Usually, I don't have this problem with mmenu, but for last a few projects (Contao 4.9.1 - PHP 7.4 - mmenu 3.1.2).

Hi, How we can translate this extension?

When I use your extension for my anchor navigation the click does not close the menu. I think this is an error. Can you fix it, please, or write me how I can fix it by myself. Thank you.

Here is the website where I use it. http://dev.akupunkturpunkt.com/

Hello,

the extension occurs following error in Contao Manager

Using version ^3.1 for dklemmt/contao_dk_mmenu
/homepages/45/d4295156004/htdocs/siex-transporte-contao/composer.json has been updated

# Process terminated with exit code 0
# Result: OK


> Resolving dependencies using Composer Cloud v2.4.3

# Job ID J7P1x8LduUNXuf5NS7Nzk8qZceZlT5EJX3jY6W7q9VZv14zSXmr1YeOyPU5948aohBn5LI0baaSTte5ZxZjuvYpLoBSb8Nw0v77PQy2 completed in 36 seconds
# Memory usage: 468.59MB (peak: 2328.18MB), time: 35.59s.

$ /usr/bin/php7.4 -q /homepages/45/d4295156004/htdocs/siex-transporte-contao/web/contao-manager.phar.php composer install --prefer-dist --no-dev --no-progress --no-suggest --no-ansi --no-interaction --optimize-autoloader

Loading composer repositories with package information
Installing dependencies from lock file
Nothing to install or update
Package phpunit/php-token-stream is abandoned, you should avoid using it. No replacement was suggested.
Generating optimized autoload files
Deprecation Notice: Class League\Uri\Schemes\AbstractUri located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v2.0. in phar:///homepages/45/d4295156004/htdocs/siex-transporte-contao/web/contao-manager.phar.php/vendor/composer/composer/src/Composer/Autoload/ClassMapGenerator.php:201
Deprecation Notice: Class League\Uri\Schemes\Data located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v2.0. in phar:///homepages/45/d4295156004/htdocs/siex-transporte-contao/web/contao-manager.phar.php/vendor/composer/composer/src/Composer/Autoload/ClassMapGenerator.php:201
Deprecation Notice: Class League\Uri\Schemes\File located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v2.0. in phar:///homepages/45/d4295156004/htdocs/siex-transporte-contao/web/contao-manager.phar.php/vendor/composer/composer/src/Composer/Autoload/ClassMapGenerator.php:201
Deprecation Notice: Class League\Uri\Schemes\Ftp located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v2.0. in phar:///homepages/45/d4295156004/htdocs/siex-transporte-contao/web/contao-manager.phar.php/vendor/composer/composer/src/Composer/Autoload/ClassMapGenerator.php:201
Deprecation Notice: Class League\Uri\Schemes\Http located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v2.0. in phar:///homepages/45/d4295156004/htdocs/siex-transporte-contao/web/contao-manager.phar.php/vendor/composer/composer/src/Composer/Autoload/ClassMapGenerator.php:201
Deprecation Notice: Class League\Uri\Schemes\Uri located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v2.0. in phar:///homepages/45/d4295156004/htdocs/siex-transporte-contao/web/contao-manager.phar.php/vendor/composer/composer/src/Composer/Autoload/ClassMapGenerator.php:201
Deprecation Notice: Class League\Uri\Schemes\UriException located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v2.0. in phar:///homepages/45/d4295156004/htdocs/siex-transporte-contao/web/contao-manager.phar.php/vendor/composer/composer/src/Composer/Autoload/ClassMapGenerator.php:201
Deprecation Notice: Class League\Uri\Schemes\Ws located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v2.0. in phar:///homepages/45/d4295156004/htdocs/siex-transporte-contao/web/contao-manager.phar.php/vendor/composer/composer/src/Composer/Autoload/ClassMapGenerator.php:201
InvalidArgumentException: Config file "/homepages/45/d4295156004/htdocs/siex-transporte-contao/contao-manager/composer-install.set.json" does not exist. in phar:///homepages/45/d4295156004/htdocs/siex-transporte-contao/web/contao-manager.phar.php/api/Process/AbstractProcess.php:56
Stack trace:
#0 phar:///homepages/45/d4295156004/htdocs/siex-transporte-contao/web/contao-manager.phar.php/api/Process/ProcessRunner.php(185): Contao\ManagerApi\Process\AbstractProcess::readConfig('/homepages/45/d...')
#1 phar:///homepages/45/d4295156004/htdocs/siex-transporte-contao/web/contao-manager.phar.php/api/Process/ProcessRunner.php(116): Contao\ManagerApi\Process\ProcessRunner->loadConfig()
#2 phar:///homepages/45/d4295156004/htdocs/siex-transporte-contao/web/contao-manager.phar.php/api/Process/ProcessRunner.php(61): Contao\ManagerApi\Process\ProcessRunner->wait(1)
#3 phar:///homepages/45/d4295156004/htdocs/siex-transporte-contao/web/contao-manager.phar.php/api/Command/ProcessRunnerCommand.php(46): Contao\ManagerApi\Process\ProcessRunner->run()
#4 phar:///homepages/45/d4295156004/htdocs/siex-transporte-contao/web/contao-manager.phar.php/vendor/symfony/console/Command/Command.php(255): Contao\ManagerApi\Command\ProcessRunnerCommand->execute(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#5 phar:///homepages/45/d4295156004/htdocs/siex-transporte-contao/web/contao-manager.phar.php/vendor/symfony/console/Application.php(1018): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#6 phar:///homepages/45/d4295156004/htdocs/siex-transporte-contao/web/contao-manager.phar.php/vendor/symfony/console/Application.php(271): Symfony\Component\Console\Application->doRunCommand(Object(Contao\ManagerApi\Command\ProcessRunnerCommand), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#7 phar:///homepages/45/d4295156004/htdocs/siex-transporte-contao/web/contao-manager.phar.php/api/ApiApplication.php(70): Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#8 phar:///homepages/45/d4295156004/htdocs/siex-transporte-contao/web/contao-manager.phar.php/vendor/symfony/console/Application.php(147): Contao\ManagerApi\ApiApplication->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#9 phar:///homepages/45/d4295156004/htdocs/siex-transporte-contao/web/contao-manager.phar.php/api/console(86): Symfony\Component\Console\Application->run(Object(Symfony\Component\Console\Input\ArgvInput))
#10 /homepages/45/d4295156004/htdocs/siex-transporte-contao/web/contao-manager.phar.php(57): require('phar:///homepag...')
#11 {main}
# Process terminated with exit code 143
# Result: Termination (request to terminate) [SIGTERM]


---

### Der Hintergrundprozess wurde unerwartet beendet ###

It happens with Contao 4.9.5 and PHP 7.4.9, Hosting United Domains

[6.9MiB/0.24s] Loading composer repositories with package information [54.7MiB/1.56s] Updating dependencies [1100.4MiB/7.60s] Your requirements could not be resolved to an installable set of packages. [1100.4MiB/7.61s] Problem 1 - dklemmt/contao_dk_mmenu[3.2.0, ..., 3.2.2] require symfony/dependency-injection ^3.4 || ^4.0 -> satisfiable by symfony/dependency-injection[v3.4.0, ..., v3.4.47, v4.0.0, ..., v4.4.19]. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.4.19. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.4.18. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.4.17. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.4.16. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.4.15. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.4.14. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.4.13. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.4.12. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.4.11. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.4.10. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.4.9. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.4.8. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.4.7. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.4.6. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.4.5. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.4.4. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.4.3. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.4.2. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.4.1. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.4.0. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.3.11. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.3.10. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.3.9. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.3.8. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.3.7. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.3.6. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.3.5. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.3.4. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.3.3. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.3.2. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.3.1. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.3.0. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.2.12. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.2.11. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.2.10. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.2.9. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.2.8. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.2.7. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.2.6. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.2.5. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.2.4. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.2.3. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.2.2. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.2.1. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.2.0. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.1.12. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.1.11. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.1.10. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.1.9. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.1.8. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.1.7. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.1.6. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.1.5. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.1.4. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.1.3. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.1.2. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.1.1. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.1.0. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.0.15. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.0.14. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.0.13. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.0.12. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.0.11. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.0.10. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.0.9. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.0.8. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.0.7. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.0.6. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.0.5. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.0.4. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.0.3. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.0.2. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.0.1. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v4.0.0. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.47. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.46. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.45. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.44. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.43. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.42. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.41. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.40. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.39. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.38. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.37. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.36. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.35. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.34. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.33. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.32. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.31. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.30. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.29. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.28. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.27. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.26. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.25. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.24. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.23. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.22. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.21. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.20. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.19. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.18. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.17. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.16. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.15. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.14. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.13. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.12. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.11. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.10. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.9. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.8. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.7. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.6. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.5. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.4. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.3. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.2. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.1. - symfony/web-profiler-bundle v5.2.3 conflicts with symfony/dependency-injection v3.4.0. - contao/manager-bundle 4.11.0 requires symfony/web-profiler-bundle 4.4.* || 5.2.* -> satisfiable by symfony/web-profiler-bundle[v5.2.3]. - contao/manager-bundle is locked to version 4.11.0 and an update of this package was not requested. - Root composer.json requires dklemmt/contao_dk_mmenu ^3.2 -> satisfiable by dklemmt/contao_dk_mmenu[3.2.0, 3.2.1, 3.2.2]. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions. [1100.5MiB/7.61s] <warning>Running update with --no-dev does not mean require-dev is ignored, it just means the packages will not be installed. If dev requirements are blocking the update you have to resolve those problems.</warning> [44.2MiB/8.60s] Memory usage: 44.19MB (peak: 1101.4MB), time: 8.61s.

Hi,
I'm using mmenu in my many Contao projects, but with last versions have some problems.
The problem is with web site loading. When we open web site just for one sec we can see all mmenu items list on the left side. This list pushes all web site down and after one or two-second everything is OK. I supposed that the problem can be some conflict with Rocksolid slider plugin. On the websites where I don't have Rosckolid slider, the problematic delay is shorter.
This is not a problem with version 2.1.1, but every after it.

Hi,

habe eine kleine Seite, nur noch Cookiebar und RS-Slider drinn...

wenn ich das das mmenue im Layout aktiviere, wird der Inhalt als Schleife so lange geladen bis die Exec-Time erreicht ist...

Im mmenue sind alles "Standardeinstellungen"

Update to latest release of jQuery.mmenu >= 4.3.6

I have a script Error when i usw the mmenu.js with version 3.0.1 or 3.0.2

The console shows:
SCRIPT1002: Syntaxfehler
Datei: mmenu.js, Zeile: 1, Spalte: 2278

The menu is not functional with IE 11. No Problems with Firefox or Chrome.

When i use Verison 2.1.1 everything ist O.K.

Problem:
Wird das Suchfeld aktiviert, erscheint dieses, es werden allerdings keine Menü-Einträge gefunden.

Ursache
Das Problem liegt wohl am Aufbau des Menü-Templates. Sobald im nav_mmenu.html5 alle Span-Tags entfernt werden, dann funktioniert die Suche nach den einzelnen Menüelementen.

Funktioniert nicht

<li class="mm-listitem mm-hidden" aria-hidden="true">
<a href="erweiterungen.html" title="Erweiterungen" itemprop="url" class="mm-listitem__text">
<span itemprop="name">Erweiterungen</span>
</a>
</li>

Funktioniert

<li class="mm-listitem mm-hidden" aria-hidden="true">
<a href="erweiterungen.html" title="Erweiterungen" itemprop="url" class="mm-listitem__text">
Erweiterungen
</a>
</li>

Hi,
I have update to the last version but some css class missing in HTML.
Contao : 4.9.1
Thx

Ich setze vielmals das mmenu - article ein, da ich jeweils noch andere Contents/Links ins Flyout nehme. Passt auch perfekt für einen Seitenbaum.
Jedoch bei mehreren Seitenbäumen tritt das Problem auf, dass ich jeweils den Artikel den ich anziehen will, nur aus dem 1. resp. obersten Seitenbaum auswählen kann.
Das heisst habe ich zwei oder mehrere Bäume, müsste ich die Artikel im ersten Seitenbaum platzieren, ist da aber ein wenig unglücklich, da es sich ja um zwei Eigenständige Bäume handelt... dasselbe bei mehrsprachigen Webseiten.

Beispiel eines Inhaltelementes mit Zugriff auf alle Seitenbäume:
Artikel (Include Elemente) > Bezogener Artikel
(Bei der Auswahl kann man Artikel aus allen Seitenbäumen auswählen)

Hallo,

es kann ja im Modultyp ein mmenu - article eingestellt und ausgewählt werden.
Wenn man jetzt Beispielsweise in der Seitenstrucktur einen Stamm für die Desktop Webseite hat und einen für die Mobile anlegt, greift immer nur die Desktopversion.

Ist das beabsichtigt?

Hi together,

while working on a project, where we had an error in our HTML markup, we found an error via w3validator in mmenu extension templates.

The template nav_mmenu.html includes an itemprop attribute. The outer templates don't define an itemscope.

https://validator.w3.org/ and Sistrix mark this as an Error.

On these lines, there should be added the itemscope:

itemscope itemtype="http://schema.org/SiteNavigationElement"

Best regards
Uwe

P.S.: contao core bundle navigation defines it in mod_navigation.html5

Hi, would be nice if someone can do an update to version 5.6+ https://github.com/FrDH/jQuery.mmenu/tree/v5.6.0.

I tried to overwrite some resources in /assets with new ones from 5.6.0 and it seems to work with smooth opening and closing again.

assets\css\jquery.mmenu.css
assets\css\jquery.mmenu.oncanvas.css

assets\css\addons\jquery.mmenu.counters.css
assets\css\addons\jquery.mmenu.dragopen.css
assets\css\addons\jquery.mmenu.offcanvas.css
assets\css\addons\jquery.mmenu.searchfield.css
assets\css\addons\jquery.mmenu.toggles.css

assets\css\extensions\jquery.mmenu.effects.css
assets\css\extensions\jquery.mmenu.fullscreen.css
assets\css\extensions\jquery.mmenu.iconbar.css
assets\css\extensions\jquery.mmenu.positioning.css
assets\css\extensions\jquery.mmenu.themes.css
assets\css\extensions\jquery.mmenu.widescreen.css

assets\js\jquery.mmenu.min.js
assets\js\jquery.mmenu.oncanvas.min.js

assets\js\addons\jquery.mmenu.counters.min.js
assets\js\addons\jquery.mmenu.dragopen.min.js
assets\js\addons\jquery.mmenu.fixedelements.min.js
assets\js\addons\jquery.mmenu.offcanvas.min.js
assets\js\addons\jquery.mmenu.searchfield.min.js
assets\js\addons\jquery.mmenu.toggles.min.js

Dear all,
I just updated from Contao 3.5 to 4.9. Now I got two problms with the site:

1. The contents moves, when using the menu. The cause might me the vanishing scroll bars when clicking the menu.
   They came back, wheren closing the menu. Sothe content is moving about halb the width of the scrollbar. I treid overflow:scroll in the body and wrapper class. Nothing happend,

2. The first entry in the menu ha s a smaller height, than the rest. I tried li.active first {height:30px;"} and span.active first{height:35px;}
   without success. To see any effekt, I tried a simple color:red to the classes. Nothing happend.So there must be an extra css file beeing loaded. When analysing the source with chrome I saw an entry like 400px x 20px, Where is this defined?

How can I fix this. Thanx 4 hints
tsunami

Hallo Fritz,

ich habe heute testweise die neue Version 3 installiert und dabei ist mir aufgefallen,
dass das Menü nach dem Klicken nicht mehr angezeigt wird. Der Grund dafür war auch schnell
gefunden, denn im Template mod_mmenu.html5 findet sich im nav-Container eine invisible CSS-Klasse, die dazu führt, dass das Menü nicht angezeigt wird und die IMHO entfernt werden kann.

Beste Grüße
Sares

Hab die 3.0.0-RC1 unter Contao 4.4 getestet - funktioniert alles wie gewünscht. Einen Vorschlag/Erweiterung zur Konfiguration hätte ich noch...

Den Titel (Standard: Menu) könnte man konfigurierbar und somit (mit Inserttags) mehrsprachig machen. Die Überschrift hat ja hier keinen Sinn, eventuell könnte man dieses Feld nutzen?!

Ich habe versucht Composer in meine Contao-Installation einzubauen. Direkt nachdem ich Composer installiert habe (+ Migration aller Plugins) habe ich diese Fehlermeldung erhalten:

[01-Dec-2015 10:08:16 Europe/Berlin] 
PHP Warning: filemtime(): stat failed for C:\xampp\htdocs\yyy/system/modules/dk_mmenu/assets/css/themes/.css in C:\xampp\htdocs\yyy\system\modules\core\library\Contao\Controller.php on line 793
#0 [internal function]: __error(2, 'filemtime(): st...', 'C:\\xampp\\htdocs...', 793, Array)
#1 C:\xampp\htdocs\yyy\system\modules\core\library\Contao\Controller.php(793): filemtime('C:\\xampp\\htdocs...')
#2 C:\xampp\htdocs\yyy\system\modules\core\classes\FrontendTemplate.php(102): Contao\Controller::replaceDynamicScriptTags('<!DOCTYPE html>...')
#3 C:\xampp\htdocs\yyy\system\modules\core\pages\PageRegular.php(190): Contao\FrontendTemplate->output(true)
#4 C:\xampp\htdocs\yyy\system\modules\core\controllers\FrontendIndex.php(267): Contao\PageRegular->generate(Object(Contao\PageModel), true)
#5 C:\xampp\htdocs\yyy\index.php(20): Contao\FrontendIndex->run()
#6 {main}

Die Datei ".css" existiert nicht indem Ordner Assets. Wenn ich diese Datei anlege verschwindet diese Fehlermeldung.

Contao 3.5.4
dk_menu 1.5.1.9007

I'm testing the new Version. But i can't figure out why I get the Error: SyntaxError: '#' is not a valid selector.
I have testet it in Contao 4.4.40 with and without other JS active.
The error is in line 1 of the code (but there is all Code, so i don't think it is usefull).

Any clue why this could happen?

Kind regards

Hi,
is there any possibility to make a close button into mmenu (such as in the screenshot),

I tried with mmenu mburger (https://mmenujs.com/mburger/tutorial-css.html) but not working.
Maybe can be useful to make an update of Contao mmenu plugin with an implemented field for adding a close button.
Thank you

Hi,

I will make a pull request if it's ok for you ?

There are "only" 4 colors : default, mm-light, mm-black and mm-white. The others were apparently removed. We remove them too?

Ich würde mir eine Option wünschen um das Menü nicht bei :hover sondern onClick öffnet bzw. schließt.

Ich habe ein Menü mit teilweise hoher Anzahl an Unterpunkten. Dort muss dann auf mobilen Geräten gescrollt werden.
Verwende ich die vertikale Version des Menüs, kann ich fast gar nicht vertikal scrollen – das Menü “friert ein". Bei der horizontalen Version ist dies nicht seltener zu beobachten, kommt aber auch vor. Es scheint damit zusammenzuhängen, wo genau man mit dem Finger anfängt zu schieben.

Hier ein Beispiel: https://www.zkp-online.de/seminare (Untermenü "Die Seminare").

Die Konsole meldet Uncaught DOMException: Failed to execute 'querySelector' on 'Document': '#' is not a valid selector.
Und im Code findet sich auch die Ursache:
<script> document.addEventListener( "DOMContentLoaded", () => { new Mmenu('#', null, null); }, ); </script>
Dennoch ist die generelle Funktionalität vorhanden.

Was könnte ich falsch gemacht haben?
Ich verwende die Version 3.1.0 mit Contao 4.4.45

Contao 4.4.26: Wenn meine Navigation aus internen Weiterleitungen auf einen Anker bestehen, erzeugt die Extension im Frontend nur den Anker, somit funktioniert die Navigation nicht mehr.