Karmalakas Veteran
@Karmalakas · Joined 6 years ago · 1180 posts · 28 topics · 216 reputation
Badges
Recent posts
-
Grav CMS Tutorials
· 4 years ago
I almost daily see someone new coming with questions here or on Discord. So I would say community is even growing
-
Override JQuery in Grav
· 4 years ago
:man_facepalming: Once again I fail... Forgot about the promise to search whole project.. Did the search after I just couldn't figure out what was happening (apparently I didn't notice I was redirecte
-
Override JQuery in Grav
· 4 years ago
Frontpage site - https://test-grav.local Didn't even bother to create account on Admin 🙂 Both All four cases tested only on frontpage
-
Override JQuery in Grav
· 4 years ago
Just tried the simplest way Install fresh Grav No changes - jQuery loads Delete {% do assets.addJs('jquery', 101) %} in line 30 of Quarks base template - jQuery is gone Install fresh Grav + Admin
-
Override JQuery in Grav
· 4 years ago
@pamtbaau: Please show that after the steps I’ve shown jQuery is still being loading. How can I show it, if I'm not using Quark? When I get to my IDE later I'll do a search on a whole project to see
-
Override JQuery in Grav
· 4 years ago
@pamtbaau: Try the following: Fresh install of Grav 1.7.33 Remove line 30 containing {% do assets.addJs('jquery', 101) from /user/themes/quark/templates/partials/base.html.twig I use my custom them
-
Override JQuery in Grav
· 4 years ago
Submitted an issue https://github.com/getgrav/grav-plugin-admin/issues/2273
-
Override JQuery in Grav
· 4 years ago
@hughbris: It does not mean <...> your page is loading it But that's exactly what it means :) If it's there, page loads it, even if not used by theme
-
Override JQuery in Grav
· 4 years ago
Yup.. Nothing in Admin works that's on AJAX Will you file an issue on Admin repo? Or I could do that maybe tomorrow P. S. What was the original string? 😃 I need to put it back in It seems I can't eve
-
Override JQuery in Grav
· 4 years ago
I'm using only my custom theme (the only one theme installed) and can confirm the behavior. Although just deleting the string inside second input helped