Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Greetings,
I would be interested in using this theme but I do not use panolopy, I build my panels sites from the ground up. Would you consider removing the panolopy dependency? thanks.
Comments
Comment #1
areynolds commentedTechnically there is no "dependency" per-say; there's just a prominent warning. Perhaps we could either limit the warning to users with a Panels administrative permission or have it only appear after install instead of all the time; otherwise, I'd suggest either limiting your error reporting to other users or hacking the warning so you can play around a bit and we'll adjust the reporting.
Comment #2
pirog commentedwe could scale back the "dependency" but in order to get kalatheme to function without a shit ton of errors you definitely need a couple important modules. on our end it was much easier to just say "rely on panopoly" then spell out the minimal "requirements."
that said if you were to do this you would probably want to verify the user has at least the following
1. libraries module
2. jquery update module and jquery version set to 1.7
3. panels/panelizer and dependencies
@talengix what are your thoughts?
Comment #3
pirog commentedComment #4
pirog commentedComment #5
pyxio commentedhi pirog,
i use all of those modules extensively. not a problem. i want to use kalatheme but i don't want to use panopoly (or any heavy distro for that matter including commerce kickstart) as i prefer to install the modules i want and build sites my way rather than install a heavy distro and remove everything and rebuild it. panolopy is fine... it's just that my approach to site building suites me better and it is unfortunate to not be able to use this potentially awesome theme because of my approach to site building.
so should i be waiting for a build that turns these errors off? or try the current version? thanks for your help. cheers kevin
Comment #6
pirog commentedcurrent version still "requires" panopoly.
i think that we might do going forward is change the "dependency" to hook_requirement and change the actually programmatic checking to
1. libraries module 2.1
2. jquery update module and jquery version set to 1.7
3. panels/panelizer and dependencies
however i think we will keep the marketing and instructions focused on installing panopoly as the best way to get this thing running. this way we maintain the "ease" of getting starting while still affording people who dont want to use panopoly more flexibility.
sound good?
Comment #7
pyxio commentedthanks pirog,
sounds fine to me. as long as advanced site builders are at liberty to build up a panels site from scratch. that is all that i am concerned about. panolopy is a good distro and i understand why you like it. i just think a little more flexibility should be built into theme. cheers kevin
Comment #8
pirog commentedyup, youve convinced me.
the impetus for panopoly was that its easier for a lot of people to just download the distro and install kalatheme vs settings everything up from scratch... but you are right we shouldnt just ignore the more advanced market segment on this point.
ill ping this thread when we push up the change!
Comment #9
pyxio commentedsuper and thanks. again nothing against panolopy. those guys rock. fyi, i am a drupal commerce site builder and also don't use kickstart... not because it isn't awesome.. i just like to build stuff from the ground up ;o) cheers
Comment #10
pirog commented@talengix,
ive pushed this up to the latest dev. instead of checking for panopoly we are now checking for
* Libraries 2.1+
* Panels 3.x
* JQuery Update 2.x (with JQuery version set to 1.7+)
* A bootstrap library (read below in Installing Bootstrap)
going to mark this as fixed but if you could provide some additional testing that would be awesome.